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

Option to override the default dirty form info message

        Details

        • Type: Improvement Improvement
        • Status: Closed Closed
        • Priority: Major Major
        • Resolution: Fixed
        • Affects Version/s: 2.2
        • Fix Version/s: 2.3
        • Component/s: Development, User Experience (UX)
        • Security Level: Public (Public: Anyone can view)
        • Labels:
          None
        • Similar issues:
          KULRICE-8450Issues with overriding datatables options for columns
          KULRICE-12904Info messages missing at page level
          KULRICE-13011Implement custom dirty data warning dialog when user tries to leaves page before saving changed data
          KULRICE-8001Checks not correctly cleared for dirty fields
          KULRICE-8407Messagemap Message values(info,error,warning) are not displayed
          KULRICE-7851Dirty field indicator not working on Collections
          KULRICE-9816New collection rows are not set to dirty
          KULRICE-1516Allow for overridding of default OJB.properties
          KULRICE-11602Create extension points to override ExpressionEvaluator
          KULRICE-9466THe [link] tag in messages in KRAD use target="_blank" by default and don't give an option to specify the target (or no target at all, for that matter)
        • Rice Module:
          KRAD
        • Application Requirement:
          KS
        • KAI Review Status:
          Not Required
        • KTI Review Status:
          Not Required

          Description

          Currently, KRAD displays 'Form has unsaved data. Do you want to leave anyway?' on form unload. It would be nice if we have an option to customize this message something like

          "You are leaving a page with unsaved changes.

          Would you like to save your changes before continuing?

          [ Save changes ] [ Discard changes ] Cancel"

            Issue Links

            is related to

            New Feature - A new feature of the product, which has yet to be developed. KULRICE-6676 UI Framework - Central Repository for Message Content

            • Major - Major loss of function.
            • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
            relates to

            Task - A task that needs to be done. KULRICE-7998 Rewrite how Dirty Fields Work

            • Major - Major loss of function.
            • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
            reported by User Feedback issue

            Improvement - An improvement or enhancement to an existing feature or task. KSENROLL-962 Unsaved Changes Dialog Box (Decision 26)

            • Major - Major loss of function.
            • Open - The issue is open and ready for the assignee to start work on it.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Jessica Coltrin (Inactive) added a comment -

              Candace, isn't this already in the plans for 2.2, i.e in the externalized messages item for 2.2.0-m3?

              Show
              Jessica Coltrin (Inactive) added a comment - Candace, isn't this already in the plans for 2.2, i.e in the externalized messages item for 2.2.0-m3?
              Hide
              Permalink
              Jerry Neal (Inactive) added a comment -

              Jessica,

              External messages is for m3, but I think we need a Jira for this as well. The extend of external messages is to allow things that are specified in the XML to be external. However this message and some other are coming from script. So first it needs to be externalized. As part of the external messages we could do the effort to make everything external. I was seeing that as another effort since it would add quite a bit to the task. But it probably makes sense to do them together. Thoughts?

              Jerry

              Show
              Jerry Neal (Inactive) added a comment - Jessica, External messages is for m3, but I think we need a Jira for this as well. The extend of external messages is to allow things that are specified in the XML to be external. However this message and some other are coming from script. So first it needs to be externalized. As part of the external messages we could do the effort to make everything external. I was seeing that as another effort since it would add quite a bit to the task. But it probably makes sense to do them together. Thoughts? Jerry
              Hide
              Permalink
              Candace Soderston (Inactive) added a comment -

              I'll link this with the item in 2.2.0-m3 (https://jira.kuali.org/browse/KULRICE-6676).

              Show
              Candace Soderston (Inactive) added a comment - I'll link this with the item in 2.2.0-m3 ( https://jira.kuali.org/browse/KULRICE-6676 ).
              Hide
              Permalink
              Venkat PremChandran (Inactive) added a comment -

              The current impl uses JS alert. Are we going to change it to use question framework?

              Show
              Venkat PremChandran (Inactive) added a comment - The current impl uses JS alert. Are we going to change it to use question framework?
              Hide
              Permalink
              Jerry Neal (Inactive) added a comment -

              Venkat,

              That is correct. Dialog/question framework will be coming in m2 and we will make use of it for all our alerts.

              Jerry

              Show
              Jerry Neal (Inactive) added a comment - Venkat, That is correct. Dialog/question framework will be coming in m2 and we will make use of it for all our alerts. Jerry
              Hide
              Permalink
              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
              Hide
              Permalink
              Jessica Coltrin (Inactive) added a comment -

              per Jerry's comment, this should be fixed. Please reopen if it's still an issue.

              Show
              Jessica Coltrin (Inactive) added a comment - per Jerry's comment, this should be fixed. Please reopen if it's still an issue.

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel