Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-9641Change table components to not go through field templates
      KULRICE-11750Remove field label position option
      KULRICE-12815 Expressions in field labels not carried through for table headers
      KULRICE-5531Field in "Attribute Field Options 2" needs watermark: "No instructions, no label"
      KULRICE-11689Modify label default configuration
      KULRICE-10826Required message label always appears in left when placed inside Table collections
      KULRICE-12551Improvements on handling of template options
      KULRICE-11698Provide option for not displaying messages at page and section levels
      KULRICE-7203Go through KRAD script files and create constants
      KULRICE-4710Support for always visible constraint message
    • Epic Link:
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      UIF Component
    • Sprint:
      2.4.0-m4 KRAD UXI Sprint 2
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Labels for multi-value controls go through the message template each time (for rich messages). Is it possible to only invoke the message template when a rich message is present (similar to how we do in other places)?

      This is a snippet from sping.ftl:

      <label for="$

      {controlId}" onclick="handleRadioLabelClick('${controlId}

      ',event); return false;"><@krad.template component=option.message/></label>

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Brian Smith (Inactive)
            Reporter:
            Jerry Neal (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 4 hours
              4h
              Remaining:
              Time Spent - 2 hours Remaining Estimate - 2 hours
              2h
              Logged:
              Time Spent - 2 hours Remaining Estimate - 2 hours
              2h

                Agile

                  Structure Helper Panel