Question
Debeka
DE
Last activity: 3 Apr 2017 12:06 EDT
Avoid "Confirm close" prompt message when no "real" change to WO has been made
Hi everyone,
in our application on Pega 7.1.7 we have a main case and several subcases that can be started from the main case.
The subcases are listed in a worklist that is accessible through the main case.
For each subcase in the worklist, it is possible to click the expand icon in the worklist to see more information on the subcase:
When you click the expand icon and then try to close the main case, the "Confirm close" prompt message pops up, although NO changes to any of the work items have been made. Only the icon to expand the subcase for more information was clicked. It seems like just clicking this icon triggers the system to assume that changes to the work item have been made. This is irritating our end users a lot and they're requesting this popup to not show in such cases.
Hi everyone,
in our application on Pega 7.1.7 we have a main case and several subcases that can be started from the main case.
The subcases are listed in a worklist that is accessible through the main case.
For each subcase in the worklist, it is possible to click the expand icon in the worklist to see more information on the subcase:
When you click the expand icon and then try to close the main case, the "Confirm close" prompt message pops up, although NO changes to any of the work items have been made. Only the icon to expand the subcase for more information was clicked. It seems like just clicking this icon triggers the system to assume that changes to the work item have been made. This is irritating our end users a lot and they're requesting this popup to not show in such cases.
I sumitted a service request in the PDN Support Portal already and was suggested to post my issue here.
Is there a possibility to change the behavior of this prompt message, so that it only shows when real changes (text edits, check boxes clicked) have been made?
Looking forward to your input on this.
Thanks,
Kerstin
***Updated by Moderator: Marissa to archive post. This thread has been closed to future comments. This thread will not be updated and is available for educational/informational purposes. If you have the same question, please write a new post.***
Pegasystems Inc.
IN
Hi Kerstin, Good Morning!
Could you please double check if any set value action event is applied on property '.pyRecordDirtyCheck'
because the property .pyRecordDirtyCheck triggers the popup. so tracking the value of this property helps.
to solely disable the popup, please include OOTB section rule @baseclass.pxDisableClientDirtyDetection on the harness rule/section configured rule.
Please share your comments/observations, Thank you!
psahukaru
Debeka
DE
Good morning!
There is no set value action event applied on the property you mentioned. It looks like some JavaScript sets the "dirty" flag.
We managed to disable the popup by including the section you mentioned, but the problem now is that the popup is then also disabled when we actually MAKE real changes (like adding text in a comment section, selecting from a dropdown list etc.) in some other part of the UI inside the assignment.
So in an assignment, is there any way to distinguish between real changes (adding text, selecting from a dropdown etc...) and just expanding some information, e.g. in a repeat grid like in my above screenshot? So that the popup ONLY shows when real changes have been made?
Pegasystems Inc.
JP
It is difficult to avoid dirty detection, if you use OOTB "expand row" feature of the repeating grid, which will trigger "Edit Item" event.
However, you can use a button or link to luanch a flowaction which displays the detail of the sub-case in Modal Dialog, that won't trigger "Edit Item" event, hence can escape dirty detection.
Debeka
DE
Hello Chunzhi,
thanks for the suggestion. Unfortunately, a modal dialog is not the behavior that our end users would appreciate. But I will keep it in mind nevertheless!
Pegasystems Inc.
JP
Hi Kerstin,
Recently, I noticed that Pega Pulse "Share" button has the ability to suppress the dirty check dialog and I found that it is running the script "pega.u.d.clearDirtyState" at the end of its action set.
So, if it is OK for you to implement a custom expand button like below example provided in UI Gallery, I think you can run the above script on click of the custom expand button to avoid dirty check.
Chunzhi