You can configure a child case type with a set of dependencies that control whether the case type is instantiated. By allowing your application to manage run-time dependencies, you can reduce the workload for case workers.
In the Explorer panel, click Cases, and then click the case type that you want to open.
Caution: Ensure that you open the correct version of your case type if it has multiple parent case types. The instantiation details for a child case type are unique to each parent case type.
On the Settings tab, click Instantiation.
Select the Automatically by system when check box.
Click [Any or all] of the below conditions are met.
Click + Add condition to define a dependency.
In the Case field, press the Down Arrow key and select a case type on which your current case type depends.
This list is populated by case types that share your topmost case type and excludes: specialized case types, descendant case types, and case types with more than one parent.
In the Condition list, select the criteria for creating a child case.
If you select the has work status condition, select a case status in the list that is displayed.
Tip: When using work status as dependency condition, ensure that your process has at least one shape, such as an assignment or utility, that sets the status of a case to the expected value.
If you select the has completed condition, click any or all to indicate how many cases must be resolved before a child case is created.
Click OK.
Optional: Further refine the conditions that control whether a case is created by pressing the Down Arrow key in the Allow only when field and selecting the name of a when condition.
Click Save.
At run time, a child case is created if one does not already exist, your dependency conditions are met, and the when condition that you provide returns a true value. The limitation of one child case prevents duplication when a dependency, such as a parent case type reaching a specific stage, is fulfilled more than once.