Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-9916

Do checkbox conversion in LookupInputField only when specified through attribute definition

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-10121Attribute Definition: Conversion Script
      KULRICE-10120Attribute Definition: Conversion Guide
      KULRICE-11549Conversion Script- When tranforming MaintainableFieldDefinition, the name attribute is the only one being transformed.
      KULRICE-6721Document search does not work properly with KNS Attribute Definitions
      KULRICE-7415BO Notes do not save through notes tag
      KULRICE-6860Add support for specifying multiple default values for an attribute definition or field
      KULRICE-9489Determine best way to determine whether KRAD criteria fields treat wildcards and operators as literals
      KULRICE-7643DTOConverter#convertWorkflowAttributeDefinition only looks for a definition by name now
      KULRICE-1374EDocLite does not properly handle multi-value checkboxes in the case of rendering as read-only
      KULRICE-10055Text for radio buttons do not change to correct color when disabled until hovered (IE only issue)
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      Lookup
    • Application Requirement:
      Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      For LookupInputField convert the checkboxes only when it comes from the attribute definition.

      Jerry's request/observation:

      It seems we only do the textarea control conversion if it comes from the attribute definition, but we convert checkboxes in all cases. Is there a reason for the difference? It makes sense to me that we only convert controls if it comes from the AttributeDefinition. If they set the control explicitly on the field, we should probably just allow it.

      Jerry also suggest the following improvement:

      For converting from the checkbox to the radio group. We inject the radio group for one case, and build it using the component factory in another case. I would just build a bean for the radio group with a set id, then if it is determined you need to convert the control call the component factory to get that bean by id. That way it is configured in the XML, but we only get it if needed.

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Claus Niesen
              Reporter:
              Claus Niesen
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel