Case type dependency

Case type dependency relationships control automatic case instantiation, or the completion of a workbasket assignments (also referred to as a "mid-process dependency"). The case types must belong to the same top-level case type, and should not have parent/child covering relationships (to help avoid deadlocks).

Instantiation dependency

This relationship exists when a dependent case type automatically instantiates only when one or more other case type instances (under the same top-level case type, and at sibling or cousin-levels) are created, completed, or reach a specified work status.

Top-level case types cannot have instantiation dependencies.

To create this relationship:

1. On the Case Explorer, select the case type for which you want to create an instantiation dependency.
2. Open the Details tab and select the Instantiation Edit link to open the Case Designer: Instantiation pop-up dialog.
3. Select Automatically by system when checkbox.
4. Specify which case type or types it depends on, and the conditions the case must meet in order to instantiate the case.
5. Click OK to save your edits and close the dialog.

Mid-process dependency

A dependent workbasket assignment depends upon another case type instance reaching a specified work status in order to automatically complete and advance the flow. Use a Dependent-type Assignment shape to specify the workbasket that the case is routed to, the case type the assignment is waiting for, the status the case must reach, and the flow action following completion. A Declare Trigger rule is automatically created in the Applies To class of the case type that activates the assignment. See Flow form — Editing with Process Modeler — Editing Assignment shape properties. The case types ( Applies To class) of the flow containing the dependent assignment and the case type that is being waited for must both be under the same top-level case type.

	Case Management, assignment, work item status
	Using the Case Explorer About Case Type rules

Definitions