Lock is not checked and data is overriden
Application does not check for the lock while saving a work object. The data is overriden due to this. This issue is reproducible only when the state of the work object is new.
Steps to Reproduce
1. Create a case.
2. Pull the case from work basket, and passivate it without closing the current browser session.
3. Wait till another user pulls the case and Resolve-Completes it.
4. Click Save in the current session. Notice that the application incorporates the changes to the database instead of checking on the lock.
A defect in Pegasystems’ code or rules:
An internal property holds the value whenever data is fetched from the database. No value is set in this property when the case is created for the first time. Hence, it is treated as a new instance. Therefore, the lock is not checked and the changes are incorporated in the database when saved.
Published March 16, 2016 - Updated October 8, 2020
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.