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.
I tried setting up the similar use case to understand your use case and see that there is an error message which comes up when the user A tries to submit the assignment he is working on, when prior to that user B has already committed the changes of the assignment to DB.
Error message states as below -
As the error comes up to user A now, ideally they won't be able to submit the changes to DB since the changes are already committed to DB by user B.
Are you not facing some similar error in this scenario even after having optimistic locking implemented? If so, can you please share the version of prpc where you are facing the issue?
Posted: 5 years ago
Posted: 12 Jun 2017 2:43 EDT
venkata praveen kumar pittala (venkatapraveen)
Lead System Architect