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

Can't lock the record of a data table using Obj-Open



The applicaiont implements a data table in Data class keyed on the operator id. During the routing process this information is used and updated to enhance routing decisions. In the routing activity a lock is requested in the Obj-Open. Ocasionally when multiple operators route work to the same user, then some don't obtain a lock.

Error Messages


Steps to Reproduce

In a routing activity perform an Obj-Open with "Lock" checked for a record related to the operator that the work will be assigned to.

Root Cause

The root cause is due to a lack of providing user feedback and allowing retry when lock can't be obtained.


Customer decided to implement own enhancement to their application.
When multiple users attempt to lock a work object only one should obtain a lock. This is the expected behavior. The local change involved adding checking for the lock, done in a transition step. Then appropriate action is taken (delay and retry, or show message to user, etc) based on business requirements.


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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