Summary

Error Messages

Steps to Reproduce

1. Create a hierarchal parent-child case structure.
2. Deselect the 'Lock parent case when child case is locked' checkbox in the Case type settings.
3. Resolve the child case.

Root Cause

Resolution

1. In a child case flow, the lock on the parent case is acquired through the obj-refresh. The lock of the parent case performs an obj-open-by-handle followed by an obj-save (as in the getWorkObjectLock activity). This is because in certain scenarios, the parent case is already locked, and if an obj-refresh-and-lock is performed, the Clipboard page is not updated.
    
2. In the prConfig.xml, set <env name="database/maxlockattempts" value="1"/>
   
   The default value is 3. That is, the value represents the number of times the server attempted to lock a work object before displaying an error. 
   
   Any value higher than 1 causes the system to read the page from the database before checking if the object is lockable. This introduces a Timing window in which another requestor may have updated the page beyond what is read from the database. As a result, a stale page is delivered.
    
3. Write a custom activity as below to set the pxCoveredCountOpen,
   
   In the Method Parameters,
   
   Set the PageName to any page of the code-pega-list. This stores the browse results.
   Set the ObjClass to a class to search to obtain child cases.