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.