Skip to main content
This content is now archived and is no longer updated. Progress is not calculated. Pega Cloud instances are disabled, and badges are no longer awarded.

Configuring case locking

Configuring case locking

When working with a case type hierarchy, you set locking on the top parent case. The settings cascade down to each child case when it is instantiated. If the child cases are instantiated as part of the parent case, they have the same locking settings as the parent. In the Case Type Explorer, select the parent case type to set locking. Then, in the Case Designer, on the Settings tab, select the Locking option. If you select Allow one user, you can modify the default locking timeout of 30 minutes in the Access time out value is ________ mins field. Consider the business context when setting the timeout duration. For instance, if a case will likely be opened frequently, you may want to shorten the timeout so that users can more quickly access the case.

Case designer settings locking

If you select default locking, you can update the lock timeout for any child cases. If you do not want to lock the parent case if the child case is open, select the Allow access for the parent case when the child case is opened check box.

Case designer child case settings locking

For more information about the locking options, see the Help topic Managing concurrent access to a case.

Locking standalone cases

Child cases may be instantiated independently of a parent case. For example, you may want to create a shipping case as a standalone case that is not a child case of a purchase request parent case. If a child case is instantiated as a standalone case, it does not inherit its lock settings. You can configure case locking for this case type on the Advanced tab of the Case Type rule.

Stand Alone Case Locking Advanced Tab

This Topic is available in the following Module:

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

Pega Academy 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