Managing concurrent access to a case
Set a locking strategy for parent case types to reduce the risk of losing updates to cases that users make simultaneously.
In most configurations, use the default locking strategy to preserve transaction integrity among cases. If you do not use default locking, you can lose work when other users perform such tasks as bulk processing or escalation actions in a service-level agreement.
In the navigation pane of App Studio, click Case types, and then click the case type that you want to open.
On the Settings tab, click Locking.Only parent case types support this option.
Select one of the available locking strategies.
- To allow one user at a time to work on a case, click Allow one
This default strategy locks the case for 30 minutes or until the user submits or closes the case.
Use this approach to enable data updates and to maintain transaction integrity in both parent cases and child cases. For example, the parent case can contain properties that count or total values in the child case. Locking both parent and child cases at the same time helps to keep the counts or totals in sync.
- To allow multiple users at a time to work on a case, click Allow
This strategy preserves the changes that the first concurrent user makes. All other users who are working on the case receive notifications and must review the changes before they can submit their own updates.
Use this approach if multiple users need to open and review cases simultaneously but do not have to update the cases.
- To allow one user at a time to work on a case, click Allow one user.
To change the default timeout value of 30 minutes, in the Access time out value is field, enter a number.
- Overriding the locking strategy of a child case
Override a locking strategy to customize the way that your application manages concurrent updates to child cases. By default, a child case inherits the locking strategy from its parent case.
- Guiding case workers to successful case resolution
- Object locking