Ability to navigate to harness instead of dirty Unsaved Changes check happening
When a user in our application goes into a case and enters some data without saving, it will throw the dirty warning message letting them know they have unsaved changes that they can save, discard, cancel, etc.
When a user attempts to leave a case with unsaved data by clicking on a navigation item to launch a new harness outside of the case, the dirty warning modal will appear which is good, but it will then stop the user from launching the new harness because the modal window's action stops it from continuing with the navigation item's action. Suggestion is if a user does an action which causes the dirty modal window to load on screen, pressing any of the actions within the modal will not stop the other action from finishing.
Background info:
Created an SR for this issue and it was found to be expected behavior so an enhancement request was suggested to see if anything could be done for this requirement.
Updated: 6 Jan 2023 7:36 EST
Pegasystems Inc.
GB
@MattE522 can you confirm that the SR you are referring to is INC-254727 (Dirty warning causes Left Portal navigation to not occur)?
The engineer's conclusion was that when you open a case assignment in theme cosmos user portal and perform changes to the case and try to navigate to some other harness by clicking on portal left navigation menu, you are OOTB by default shown a modal window warning about unsaved changes. Upon doing any action on this modal you are navigated as per the actions configured on that modal controls within the same case.
Some more info:
We are following the global standards, and this is the expected behaviour, enhanced after the Pega upgrade. Engineering decided to change browser pop up into pega pop up to enable possibility of styling and also after closing this pop up work item should be closed, as this is the action that should take place after displaying this message according to accepted standards.
This message "Unsaved Changes - You are about to discard your unsaved changes." is informing client that his job will not be continued and changes are unsaved. Previously job was still open so this pop up wasn't needed at all. It works the same way as when we are making some changes inside the word document, and when we want to close the window the similar message appears, if we click "ok" work is closed with no changes applied (unsaved changes).
@MattE522 can you confirm that the SR you are referring to is INC-254727 (Dirty warning causes Left Portal navigation to not occur)?
The engineer's conclusion was that when you open a case assignment in theme cosmos user portal and perform changes to the case and try to navigate to some other harness by clicking on portal left navigation menu, you are OOTB by default shown a modal window warning about unsaved changes. Upon doing any action on this modal you are navigated as per the actions configured on that modal controls within the same case.
Some more info:
We are following the global standards, and this is the expected behaviour, enhanced after the Pega upgrade. Engineering decided to change browser pop up into pega pop up to enable possibility of styling and also after closing this pop up work item should be closed, as this is the action that should take place after displaying this message according to accepted standards.
This message "Unsaved Changes - You are about to discard your unsaved changes." is informing client that his job will not be continued and changes are unsaved. Previously job was still open so this pop up wasn't needed at all. It works the same way as when we are making some changes inside the word document, and when we want to close the window the similar message appears, if we click "ok" work is closed with no changes applied (unsaved changes).
The solution to avoid this confusion is to include the pxDisbleClientDirtyDetection section along with the table and save the changes.
As a local change in the past we would suggest users to switch to native browser popup by adding below script in user workform. pega.u.d.bUseNativeDirtyConfirm = true
This works as expected but when users were trying to switch to local action screen multiple times, in the browser popup it also showed a checkbox "Don't let this page create more messages" or "prevent this page from creating additional dialogs". If user checked this checkbox user was unable to see browser native popup(confirm box) and also unable to perform other actions because in the code we always received false value when browser ignores in-page dialogs and we assumed that form was still dirty and that is why we were unable to navigate away from current screen.
Please find this confirm box behavior explained here: https://developer.mozilla.org/en-US/docs/Web/API/Window/confirm
From Pega side we will not be able to completely control the browser showing ""prevent this page from creating additional dialogs" checkbox. We can suggest to update a browsers to the latest version. In latest Chrome "prevent this page from creating additional dialogs" is not being displayed.
Please note that there is already an existing Enhancement Request for something similar
Cosmos: DirtyCheck warning displaying inconsistent (FDBK-75921)
"If a user begins work on a work-object (by entering text into input fields within the case) and then clicks the Home icon in the left-navigation, they get a dirty-state popup confirming they’d like to discard their unsaved changes. This is in the form of a modal with cancel, discard, and save buttons.
In the same way, when they enter the data the are getting browser alert.
Steps to Reproduce:
- In User Portal, create work object
- Assignment is in screen flow
- Add value for any of the fields in assignment
- Click on Home icon in left panel menu
- Popup window will appear – Unsaved Changes
- Cancel, Discard and Save buttons will appear in pop up window
Current Product Behaviour:
During editing the case details, if client click on My work we are getting dirty check warning in modal format. For the other left panel menu items like Dashboard, Pulse etc.--> we are getting the browser alerts.
Client Expectations:
During editing the case details, if client click on My work or Pulse,, spaces etc. they should be get browser alert in the all scenarios."
@SrinivasKakani can you verify if the above request is the same as FDBK-75921?
Carrollton Enterprise Services
US
@MarijeSchillern Hello Marije, Yes that is the SR that was linked to this request. When you say the work object is closed when the action in the dirty modal is selected, do you mean the assignment is closed so it displays Review harness or that it will completely close the case from the screen and show a different harness? I can check if someone has customized those buttons on our project and see if adding a Close action to close the case will resolve the issue. For the solution mentioned above (include the pxDisbleClientDirtyDetection section along with the table and save the changes), will this make it so dirty detection does not happen at all? We still want the detection to happen, just I guess would need the case to close out only if they select an action other than Cancel. Matt English
Pegasystems Inc.
GB
@MattE522 I found some further updates that were worked on for other use cases.
I am adding it here in case it is relevant for your requirement.
There have been further discussions with the engineering team regarding the 'Save' and 'Discard' buttons not working correctly in 8.6 and 8.7 versions.
Essentially the Save does save the changes, but the UX is confusing since Edit Details screen is not where the end user is taken after clicking Save button on pyDirtyCheckConfirm
Launch case manager, New>Process Flow>click Submit>type some text in the description field>click Actions>click Edit Details>click Save button>observe that you are not directed to being on the Edit Details screen (instead you are on the Dashboard- or somewhere else like Recently visited or the beginning of Assignments ) Not the Edit Details screen. Now launch the Screen Flow Case type>click Submit>enter some text>click Actions>Select Edit Details, Observe that you might not navigated anywhere, you just stay on the same screen or that you are taken somewhere else on the UI like Recently opened which is confusing UX.
Conclusion:
DirtyCheck modal Save button doesn't work as expected (BUG-802403)
Target release: Pega 8.7.6