Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

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.

How to allow multiple simultaneous updates of covered work objects

Updated on September 13, 2021


Version V4.2SP2 (SmartBuild) makes available a new locking mechanism for cover work objects.

Suggested Approach

In versions before V4.2 SP2 SmartBuild, standard activities lock both a work object and the cover object. The cover work object may contain counts, totals, or other derived information that should change whenever the covered work objects change.

This approach works, but prevents two people from updating two distinct work objects that belong to the same cover at the same time.  

Beginning with V4.2SP2 SmartBuild, standard activities lock the covered work object but not the cover. Then, when the processing gets to a point where locking the cover is required (because it's about to be updated), the system checks whether the cover has changed, refreshes it, and locks it. At that point both the cover and covered items are locked, and can be updated.

Using this feature, you can now begin a transaction on one work object, bring another object or objects into the transaction, and commit the modifications without violating transaction integrity.


Pega Platform 7.1.1 - 8.3.1 System Architect Lead System Architect Business Architect Experience Designer Pega Delivery Leader System/Cloud Ops Administrator Case Management Financial Services Healthcare and Life Sciences Insurance Communications and Media Government Healthcare and Life Sciences Consumer Services

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us