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

Use message for readonly values of Input and DataField to allow processing of rich message content (if they contain any)

    Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.2.0-m4
    • Fix Version/s: Backlog
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-8287Allow for use of rich messages in a header component
      KULRICE-7869Enhance Rich Message parsing to allow for ' (single quote) in content of property values easily
      KULRICE-8741Rich message support for tooltip text
      KULRICE-9722Error using spring expressions inside rich messaging components
      KULRICE-6677UI Framework - Rich Message Content / Architecture
      KULRICE-12548Rich messages not getting processed for image cutline text
      KULRICE-8253For attribute for MessageField, ActionField, ImageField, readOnly InputField, and DataField are incorrect
      KULRICE-8086Smoke tests for Rich Messages
      KULRICE-8216Document Rich Messages Functionality
      KULRICE-5987Improvements for components/html elements in message content (links and etc)
    • Epic Link:
    • Rice Module:
      KRAD
    • Application Requirement:
      Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Change display to use message template instead of just outputting the string to allow rich message content to be displayed if the string is formatted with that type of content.

      This may need a toggle to turn off and on to prevent conflicting issues with the data they want to show and the rich message parse (maybe default off, flag to turn on for when they need it?)

        Activity

        Hide
        Jessica Coltrin (Inactive) added a comment -

        moving non-blocker and non-critical m4 Jiras to 2.2-backlog

        Show
        Jessica Coltrin (Inactive) added a comment - moving non-blocker and non-critical m4 Jiras to 2.2-backlog

          People

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

            Dates

            • Created:
              Updated:

              Structure Helper Panel