Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.5
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-10159Work with KC on KRAD POC
      KULRICE-11087KC POC: Expand/collapse all buttons
      KULRICE-11084KC POC: Document Info section classes
      KULRICE-11086KC POC: Tabs - migrate jQuery to Bootstrap
      KULRICE-11082KC POC: View Header DOM
      KULRICE-1542PoC Portlet for getAllGroupNames()
      KULRICE-4358improved validation error messages.
      KULRICE-11988Validation messages add 4th level of messaging - success
      KULRICE-10983Reduce validation message divs
      KULRICE-4201Create a POC using JAXB
    • Epic Link:
    • Rice Module:
      KRAD
    • Application Requirement:
      KC, UXI
    • Sprint:
      2.5.0-m1 Sprint 1
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      The technical POC currently displays a validation message upon initially saving a proposal:

      "Document was successfully saved."

      Can we make this message dismissable by showing a close icon to the right of the message? Validation messaging is provided in the Bootstrap framework - perhaps we can leverage this?

      Also, can we make the message more specific to the user's current taskflow, such as:

      "Proposal #23533 has been initiated."

      Helpful links

      Prototype validation message sample:
      http://ux.kuali.org/prototypes/kc/p2-prototype-b1/prop.basics.details.php?msg=1

      Bootstrap aletrs:
      http://getbootstrap.com/javascript/#alerts

        Issue Links

          Activity

          Hide
          Brian Smith (Inactive) added a comment -

          The second suggestion is application specific and can be done by overriding performWorkflowAction and using a different message key and passing in the appropriate parameters for the message.

          Show
          Brian Smith (Inactive) added a comment - The second suggestion is application specific and can be done by overriding performWorkflowAction and using a different message key and passing in the appropriate parameters for the message.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 days
                2d
                Remaining:
                Time Spent - 6 hours Remaining Estimate - 1 day, 2 hours
                1d 2h
                Logged:
                Time Spent - 6 hours Remaining Estimate - 1 day, 2 hours
                6h

                  Agile

                    Structure Helper Panel