Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Unable to resolve case using alternate stage when flow SLA exist

SA-33239

Summary



The user has configured a case type with an alternate stage to Cancel the work and the option would be available through "Other Actions". Case has flow level SLA. System throws error while trying to resolve the case using an alternate stage


Error Messages



Save, Delete or Commit has failed because lock <id> is not held


Steps to Reproduce



Create a case type where there is an alternate stage to cancel work and a flow level SLA is defined.


Root Cause



When we configure SLA for a process in Case Designer, we are setting the internal flow(pzInternalProcessFlow) as companion flow for the process. When a resolution stage ends, we iterate and remove all the flows launched using RemoveFlow RUF. RemoveFlow removes the current flow and its companion flow as well. But the loop is still iterating and trying to access the internal(companion) flow which is removed previously.

Resolution



HFIX-31991

Suggest Edit

Published February 4, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us