Related information
Case type rules enable you to nest cover objects within other cover objects in a parent-child (case-child case) hierarchy. This capability helps centralize flow processing and monitoring among multiple cases in large applications. To use the rule, add it to a cover class and define the work classes you want to cover. You can nest any number of parent and child covers.
The case type rule is especially useful in case management applications. For example, an Auto Insurance Claim application has a top-level case (parent cover) called At-Fault Accident Claim. In turn, it contains two child cases (child covers):
Users can add child cases to parent cases using the Other Actions >Add Work submenu located in standard cover Perform and Confirm harnesses and Action sections, and in the My Cases tab on the Case Manager and Case Worker portals. You can specify supporting processes (commonly referred to as spin off flows) for out-of-sequence assignments. Users can add supporting processes to using the Add Work submenu.
As a best practice, use the Case Designer located in Designer Studio > Processes & Rules > Case Management to configure your case management application structure. The Case Designer provides options enabling you to visually model the hierarchy without having to directly edit the case type rules.
The functionality of the rule depends upon the type of work class that contains it.
All work classes — Use the rule to customize the starter flows that are displayed when the operator selects the New menu on the Case Manager portal.
Cover and covered classes — In addition to the above, you can:
Note: A cover work item can display its own attachments and those of its covered objects. This feature enables users to easily access documents and files related to work being performed throughout the application.
Remote case types represent cases, processed and stored in other applications, that will be created, viewed, and worked on using Federated Case Management features. See Federated Case Management - definition.
To enable a case type to be created and viewed by other applications, the case type must be made visible to other applications. Use the Advanced tab of the Case Type form to configure remote case type properties for use by other applications. See Case Type rules - Completing the Advanced tab.
Once this is done, a remote case type is defined in the other application that points to the case type by using the Remote Case Configuration tab to specify the remote system, the remote case type and the actions that can be performed by users. See Case Type form - Completing the Remote Case Configuration tab.
On the remote system, use the Advanced tab to make the case type available to other systems and publish properties that can be used by other applications in the federation.
A case type class references a case type rule. There can be only one case type rule in a class. Covered classes are referenced by the case type rule in the cover class. It’s not strictly true that the flows reference the case type rule. The flow form displays a link to it so you can configure aspects of a work class that you use from within a flow.
In the Records Explorer, select Case Type in the category Process to list all case type rules available to you. Use the Application Explorer to access case type rules that apply to the case type classes in your current application.
Case type rules are part of the Process category. They are instances of the Rule-Obj-CaseType rule type.
Process category