GetNext-MoveToWorklist does not honor Optimistic Locking
When using the GetNextWork (GNW) with Optimistic locking to fetch an assignment, the work object is locked and is not released. Additionally, when a different user opens the same assignment and submits it, error occurs.
Assignment is already locked by other user
Lost ability to make change
Steps to Reproduce
- Create a case type with Optimistic Locking.
- Set GetNextWork_MoveAssignmentToWorklist to false in the local ruleset.
- Create some cases and open the first case from work basket.
- Click GetNext. The second case acquires a lock. Hence, users cannot submit the case. Step 5 of MoveToWorklist activity has a precondition which jumps to Step 17 on false. Step 15 and 16 are related to checking Optimistic Locking.
A defect in Pegasystems’ code or rules.
Published January 16, 2020 - 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.