Browser dirty check now native dirty check after upgrade

User Experience
, , , , , ,
1

In 8.2.7 - The dirtycheck alert is coming from the browser.

In 8.7.4 - The dirtycheck alert is showing native.

The UserWorkForm on both do not have the script setting it to true. Where is the change made? Is one preferred over the other. We are looking for same behavior as original unless we can justify the change.

2

Hi @nelsa

Could you please refer below article

Thanks,

Ashok

3

@Bhumireddy Thank you for the article. I see it is preferred to use Pega native dirty check. That is helpful. I would like to see an explanation for why it is preferred. If I find that answer I will post it.

The remaining issue is I have checked the configs mentioned in the article. We have alike configs on the old and new version and are getting browser dialog on old one and native dialog on the new. Setting the UserWorkForm to true seems to be the way to use browser over native. In both the old and updated platform it is using browser without setting the script.

I will pass on it is preferred to use native.

4

@nelsa it is unknown at this time why we are getting the dirty check without having it configured on the userWorkform. We are keeping the recommended Pega dirty check on the new system.