Lock not released for new Work Objects
SummaryLock is not getting released on Work object (WO) creation even though back-to-back assignment processing is disabled for a flow.
Error MessagesNot Applicable
Steps to Reproduce
- Create a Flow.
- Check the "Creates a new work object?" checkbox.
- Uncheck the "Look for an assignment to perform after create?" checkbox.
- Run the Flow and check for lock on the WO.
Root CauseA defect in Pegasystems’ code or rules.The issue is happening due the logic in the Work-.Add (Pega-ProCom:07-10-25) activity. The eighth step in the activity checks for "param.pyNextAssignment==true" and if false(when back-to-back processing disabled) directly jumps to 12th Step to call Show-Harness without unlocking the Work Object.
Published April 18, 2017 - Updated May 3, 2017