Support Article

Lock not released for new Work Objects



Lock is not getting released on Work object (WO) creation even though back-to-back assignment processing is disabled for a flow.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a Flow.
  2. Check the "Creates a new work object?" checkbox.
  3. Uncheck the "Look for an assignment to perform after create?" checkbox.
  4. Run the Flow and check for lock on the WO.

Root Cause

A 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.


Apply HFix-33917.

Published April 18, 2017 - Updated May 3, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.