Back Forward About Dependencies

The Dependencies setting, on the Details tab of the Case Designer landing page, displays the number of case types this case type is dependent upon in order to automatically instantiate. This does not appear in top-level case types.

A dependency relationship exists when a dependent case type can automatically instantiate only when one or more other case type instances (under the same top-level case type) are created, completed, or reach a specified work status. You use this item to define that relationship.

Using the parent case type's Instantiation setting, you select the Upon Dependency Fulfillment as the automatic instantiation option for the selected subcase.

Select to create one or more dependency definitions for this case type. In the Define Dependencies dialog, complete the following fields.

Field

Description
Enabled Selected by default. Clear the check box to disable the dependency on the case type defined in the adjoining Depends on field.
Depends on Select a case type whose case instance(s) must attain the value defined in the Satisfied When field in order to instantiate this case type.

Enter case types that are siblings or cousins under the same top-level case type.

You cannot define dependencies on:

  • Case types with more than one parent under the same top-level case type.
  • Descendent or ancestor case types.
  • Specialized and base case types. See the Specialized item below.
Dependency Select one of the following:
  • Any Case — The case is instantiated when the first Depends on case type instance reaches the status defined in the Satisfied When field.
  • All Cases — All of the Depends on case type instances must be resolved in order to instantiate the case.
Satisfied When Appears when you select Any Case. In order to instantiate the dependent case type, the Depends on case type instance must attain one of the following conditions (select one):
  • Has Started — The case has been created.
  • Has Completed — The case has been resolved.
  • Has Reached Status — The case has reached a shape on the process that contains the work status value you select in the adjoining field (appears when you select this option). Verify that the status you select here has been defined on the appropriate shape on the process model.

Click () to add a row and specify another dependency relationship. All enabled dependencies must be satisfied in order to instantiate a case.

You can also employ case types to define mid-flow dependencies using workbasket assignments of type Dependency. See Process Modeler — Editing Assignment shape.

Altering case type dependency relationships

Dependency data is stored on Page GrouppyDependents in the top-level case type rule. Be careful when changing the case type hierarchy, which can alter dependency relationships.

Example 1

If you promote a subcase type a top-level, all of its dependent relationships are deleted.

Assume a subcase type named Ship Order has a dependent relationship with its peer Package Order under their parent case type Equipment Request. If Package Order is removed from its parent and made a top-level case type, the Ship Order relationship is also removed. The row in its Define Dependencies dialog, and the dependency data in Equipment Request, are deleted.

Example 2

If you add a top-level case type to a subcase type under another top-level case type, the dependency data for all of the subcase types is copied to the new top level. The data in the original top-level is deleted.

Using the above example, assume you add top-level Equipment Request as a subcase type beneath top-level New Hire. The dependency data for subcase types Package Order and Ship Order is copied from New Equipment to New Hire. The New Equipment data is deleted.

Definitions case management, landing page, subcase,top-level case type, ad hoc work, cover, folder, case, instantiate, case type, Federated Case Management
Related topics About Case Type rules
About the Case Manager and Case Worker portals
Process and Rules category — Case Management Gallery

UpTools — Process and Rules

Help System home pageHelp Home