Question
IE stating "Are you sure you want to leave this page?"
Hello,
The below issue I am encountering in the CPMHC portal, I am working in Pega 6.3 SP1.
I go to Reference material option in the CPMHC and chose say any field value and then close cross mark on the window I get message window from IE stating "Are you sure you want to leave this page?"
The above message window does not appear when I don't chose any field value in the window.
Any way I can get rid of the IE window to leave the page. Does it require JavaScript change or is it configurable in CPMHC or Pega.
Thanks,
Kapil
***Updated by moderator: Lochan to add Categories***
***Updated by moderator: Marissa to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
'tis but a workaround. We've hit this problem elsewhere in v6, and got the same workaround suggestion from GCS.
Obviously, what's happening here is that the gDirtyOverride is being set to true somewhere. If it's set in a single place by a single method (e.g., setDirty?) we could put a breakpoint in the JS, and see the stacktrace to see what's setting it.
Alternatively, it would be handy to have this function make a UI change to let the user know that the page has been updated (e.g., display a pencil icon somewhere).
Is this still a problem in v7, anyone know?
Let me amend my response. I looked into the SR we had filed. spoke with a colleague, and remembered the actual implementation.
It's not that something is setting gDirtyOverride at all -- that's just the magic override property.
Instead, what's happening is that when doExplorerFormIsDirty is called prior to leaving the form, it's comparing the current values with the initial ones, as set in the defaultValue (defaultChecked, defaultSelected) property. Wher we've run into this is in setting a prompt value ("Select item here") after page loads. So we're looking at ways of addressing this.
Your code is already OOTB in the Section rule @baseclass.pxDisableClientDirtyDetection (heretofore undocumented).
Thanks Susan your trick works the way it was required, thanks a lot for the same .
@Jon thanks for guiding in the right direction and completely agree with your guidance of using the section. Thank You.
If you use some scheme like this, please test to make sure the user is still sufficiently warned if they really are about to throw away unsaved typing that they’d like to know about. /Eric
Yes Eric it is the most imp thing which I am working next. Thanks for the pointer.
Hi Kapil,
I reproduced the issue on my cpmhc system.
You can add the following script in UserWorkForm to get rid of it.
<script>
if(parent && parent.pega && parent.pega.u && parent.pega.u.d){
parent.pega.u.d.gDirtyOverride = false;
}
pega.u.d.gDirtyOverride = false;
</script>
Please give a try and let me know the result.
Thanks,
Susan