Back Forward About Case Type rules
 

Process category
  1. About 
  2. New 
  3. Processes 
  4. Calculations 
  5. Stages 
  6. Attachment Categories 
  1. Advanced 
  2. Remote Case Configuration 
  3. Pages & Classes 
  4. History 
  5. More... 

Purpose

Case type rules enable you to nest cover objects within other cover objects in a parent-child (case-subcase) 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.

This rule type provides an expanded alternative to V5.1 Cover Class settings (which can still be used) on the Process tab of a flow.

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 subcases (child covers):

Users can add subcases ( )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 > 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.

Using 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:

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.

Federated Case Management

Federated Case Management uses Internet Application Composer (IAC) connectivity to establish case management relationships between a PRPC system (control) where users create and work on cases in an application hosted on another V6.3+ system (remote).

Use the Case Designer on the control system to create abstract classes called federated case types. Each of these classes has a one-to-one relationship with a concrete case type in an application on a remote system. Federated case types have specially configured (remote) case type rules. The Remote Case Configuration tab on these rules specify the remote system, the remote case type, the actions that can be performed by control users (create or work on cases), and data transformations used by control system FCM user interface gadgets.

On the remote system, use the Advanced tab to make the case type available to the control system and publish properties that are available for use in the gadgets.

Where referenced

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 display a link to it so you can configure aspects of a  work class that you used to have to from within a flow.

Access

In the Rules 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.

Category

Case type rules are part of the Process category. They are instances of the Rule-Obj-CaseType rule type.

Definitions cover, specification, case management, ad hoc work, cover, folder, subcase, instantiate, case type, Federated Case Management, remote system, control system
Related topics Process and Rules category — Case Designer
About Remote System data instances
Understanding the Pega-ProcessEngine agent
About Declare Trigger rules
About Flows
Atlas Atlas — Standard Case Type rules

Process category
Help System home pageHelp Home