Skip to main content

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

Locking stand-alone cases

Updated on May 11, 2022

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.
  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Process category, and then click Case Type.
  3. Open a case type that you want to edit.
  4. 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:
    Only one user can access a case
    1. Select Allow one user.
    2. 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
    1. 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.
  5. 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.
  6. Click Save.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us