Skip to main content


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

Locking entities

Updated on April 12, 2021

Updating the same entities in different processes can lead to data integrity issues. Pega Product Composer for Healthcare provides a locking mechanism that helps you control the data integrity issues that might occur. These issues might occur because you update the same entities and dependent entities by using the SBC mass generation feature or through a different PCS process such Smart Update, or entity creation or update in the straight-flow process.

For example, you select a product that has 10 child plans. Another document generation process is currently using the product. As a result, the system displays 11 errors and the document generation process stops. You have to identify the 10 plan errors that result from the parent product selection, and then delete these plan entities from the configuration, or wait until the other process completes and the system removes the lock.

Pega Product Composer for Healthcare

The locking mechanism in the SBC mass generation feature works as follows:

  • If you select a product and click Submit, the selected product and all child plans, whether or not you selected them, are locked and are not allowed for use or update by another process.
  • If you select a plan and click Submit, the selected plan and parent product, whether or not you selected them, are locked and are not allowed for use or update by another process.

Note: PCS intentionally locks the product and plans even if you did not select them for document generation so that data integrity is maintained among the entities.

Locks for all selected and dependent entities remain in place based on the manager's actions. After the document generation process completes, all locks are released regardless of the status such as Pending errors and Resolved-completed.

The following list describes the manager actions:

Send for rework
The document generation is routed to the user and all locks are released.
Reject
The document generation is rejected and all locks are released.
Withdraw
The document generation is resolved as withdrawn and all locks are released.
Approve
The document generation is submitted for document generation process. Locks are in place.

When the document generation displays any of the following statuses, the entities are not locked:

  • New
  • Pending validate errors
  • Resolved withdrawn
  • Resolved-rejected
  • Pending-rework
  • Pending errors
  • Resolved completed

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us