Skip to main content


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

Configuring case type locking

Updated on December 3, 2021

For each case type, select whether only one user at a time can edit a case, or whether multiple users can concurrently edit the same case.

Pega Customer Service Implementation Guide

Identifying the most appropriate lock setting for your application and case types is important because it can affect the throughput of work in your application. For example, if a case type allows only one user at a time to edit a case, then other users cannot update the case until the first user unlocks the case or the lock settings expire.

Alternatively, if multiple users can work on a case simultaneously, then each user receives a notification when another user updates the case, and those changes are added to the case.

  1. In the navigation pane of App Studio, click Case types.
  2. Click the case type that you want to modify.
  3. Click the Settings tab.
  4. Under Access strategy to open and work on a case, select the locking strategy:
    • Allow one user - Lock the case when a single user is working in it, and leave it unlocked until that user releases the lock, or the lock times out.
    • Allow multiple users - Do not lock the case when users are working in the case.
  5. In the Time out value field, enter the number of minutes after which to automatically unlock a locked case.
    For child cases, this value should be less than the timeout value for the parent case.
  6. Click Save.

Tags

Pega Customer Service 8.7 Pega Customer Service for Communications 8.7 Pega Customer Service for Financial Services 8.7 Pega Customer Service for Healthcare 8.7 Pega Customer Service for Insurance 8.7

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