venkatapraveen Member since 2013 4 posts
Posted: 3 years ago
Last activity: 2 years 3 months ago

Dirty Pop up save is failed and showing confirm harness - Pega(7.2)

Scenario: User opened the parent work object and Modifying the case. Now child WO(Another user) updated the parent WO and got commited successfully as it has optimistic lock. Parent user is clicking on close, Dirty pop up showed and clicked on save, which is calling DoSave and commit is failed on the parent WO due to lock not held since it is already commited by child wo.

Obj-Refresh-And-Lock can't be used since parent user have already entered huge data and cannot afford to enter it once again.
Cannot even copy this stale data work object page and perform commit as the recent commit changes will override.

Trying for the situation where we know if lock is already held by the user prior commiting the WO.

***Updated by moderator: Lochan to add Categories***

**Moderation Team has archived 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.

Case Management
Moderation Team has archived post
Share this page LinkedIn