Commit done during Finish Assignment is commiting stale copy of data
1) We are opening a case from worklist in one portal(as it is optimistic locking for case type, lock is not held), meanwhile through backend activity we are updating some properties in pyWorkPage of that case through backend activity(obj-open + lock + release on commit, changed values of properties in the case which are not referred in the UI when case was first opened in portal)
2) The changed values are reflected in db
3) Now the earlier opened case has been submitted in the portal
Observed that the changed values in the pyWorkPge of case in backed activity have been overrided, and stale values prevalent at the time of opening in portal (but not referenced in UI) have been commited into db
***Edited by Moderator Marissa to update platform capability tags***
We are using pega 7.4
I'm not aware of an issue with optimistic locking on Pega 7.4
Could you please attach the screen shots for configuration.
We are using in pyDefault following configuration
An action taken on case (optimistic)
Hello,
Have you tried Obj-Refresh-And-Lock method for a quick try?
We cannot use Obj-Refresh-And-Lock for following reasons
1) We are using offline mobile and submit needs to work in offline
2) We are using OOTB finish assignment processing
3) Some other data might get changed in UI which might be lost if we do Obj-Refresh-And-Lock, in that case we need to compare the two data and merge them manually
Hi bogga,
After a quick internal discussion, we recommend that you create an SR so that a detailed investigation can be conducted.
Regards,
HI,
Below link might help you.
https://community1.pega.com/community/product-support/question/stale-as…
Hello,
This is a bit surprising. Which version of the product are you running ?