Ensure data consistency by defining a locking strategy that applies in scenarios when a case type is a stand-alone case, a child case, or a parent case. By configuring multiple locking settings at once, you ensure that your case type meets access and security requirements in every scenario.
For example, in an insurance application, you can define a locking strategy for a Body injury case type to define how locking works when the case type is a stand-alone case or a parent for a Review medical records case type. At the same time, you can configure locking behavior when the Body injury is a child of a Car accident case type. As a result, you save time because you provide configurations for different use cases at once.
You lock stand-alone cases by using a case type rule form
in Dev Studio.
- In the navigation pane of Dev Studio, click Records.
- Expand the Process category, and then click Case Type.
- Open a case type that you want to edit.
-
On the Advanced tab, in the Locking
section, define the locking strategy when this case type is a parent case or a
stand-alone case:
Choices Actions Only one user can access a case - Select Allow one user.
- Optional:
To adjust the time-out value to your needs, in the
Time out value time-out
duration mins. field, enter
how many minutes a lock remains on a case.
The default value is 30.Result: Your application locks the case for a time-out duration or until the user submits or closes the case.
Multiple users can access a case simultaneously -
Select Allow multiple users.
Providing multiple users with access to a case is necessary if you want users to access cases offline.Result: Your application preserves the changes that the first concurrent user makes. All other users who work on the case receive notifications and must review the changes before they can submit any updates.
- Optional:
To leave a parent case unlocked when this case type is a child case, select the
Do not lock the parent case when the child case is being
performed check box.
After resolving a child case, the system automatically locks a parent case for a short period of time to update relevant properties. If you leave a parent case unlocked and another user performs edits in the parent case when the system attempts to automatically acquire the lock, the error occurs. To prevent errors, allow multiple users to access the parent case.
- Click Save.