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

Lock could not be held on the screen error does not occur

KCP-122

Summary

A harness that displays the work object content is present. A button on the harness is supposed to run a screen flow in modal dialog in the same work object context. The out-of-the-box behavior is to acquire a lock on the work object when the flow starts. The lock could not be held on the screen error message does not display when the work object is locked by an operator. However, the error message displays on the Tracer. And also, the error message displays on the second assignment of the screenflow.

 

Error Messages

Not Applicable

 

Steps to Reproduce

  1. Configure a harness that displays details of a workobject instance
  2. Configure a screenflow with multiple assignments
  3. Launch the flow on a modal dialog on click of a button in the previously mentioned harness
  4. Use another operator to launch the flow for the same work object instance to acquire the lock on it
  5. Repeat the previous step with the first operator. The error message does not display 

 

Root Cause

This issue was determined to be a product enhancement request. The case lock error does not display in the first step of the flow in the modal dialog.

 

Resolution

An enhancement request, FDBK-67592, is created for consideration by Pega Product Management.

 

 

Suggest Edit

Published December 2, 2021

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