Question
Tata Consultancy Services
IN
Last activity: 17 May 2022 7:49 EDT
Closing Harness without any dirty warning on unsaved Changes
Hi,
How to close Harness tab without any dirty warning on unsaved changes on click of a button?
It is not read-only harness. The fields inside the section which is called in the harness is saved in clipboard but still I am seeing the dirty warning on tab.
Harness is launched as a new tab from another tab inside Tab group Layout.
Please post here if anyone knows/suitable action to close the tab with commit.
***Edited by Moderator Marije to add Capability tags***
Pegasystems Inc.
GB
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. 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 clik "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.
Also check with the Article below
https://community.pega.com/support/support-articles/dirty-popup-issue-save
As a local change suggested customer to switch to native browser popup by adding below script in user workform. pega.u.d.bUseNativeDirtyConfirm = true
Note if the user is trying to switch to local action screen multiple times, in the browser popup it also shows a checkbox "Don't let this page create more messages" or "prevent this page from creating additional dialogs". If user checks this checkbox user is unable to see browser native popup(confirm box) and also unable to perform other actions because in the code we always receive false value when browser ignores in-page dialogs and we assume that form is still dirty and that is why we are unable to navigate away from current screen.
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. 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 clik "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.
Also check with the Article below
https://community.pega.com/support/support-articles/dirty-popup-issue-save
As a local change suggested customer to switch to native browser popup by adding below script in user workform. pega.u.d.bUseNativeDirtyConfirm = true
Note if the user is trying to switch to local action screen multiple times, in the browser popup it also shows a checkbox "Don't let this page create more messages" or "prevent this page from creating additional dialogs". If user checks this checkbox user is unable to see browser native popup(confirm box) and also unable to perform other actions because in the code we always receive false value when browser ignores in-page dialogs and we assume that form is still dirty and that is why we are 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
Also see this forum question and this forum suggestion
There may be users who have found a way around this - they can comment further below.