Back Forward Case Type rules
Completing the Processes tab
  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... 

Complete the Processes tab to define this case type's processes, and its parent/child relationships.

Many of the fields on this tab can be configured using the Case Designer (Pega button> Process & Rules > Case Management), and are noted below. Where appropriate, your edits in the landing page also update and save this rule (can be in a locked RuleSet version). See Process and Rules category — Case Management page.

Field

Description
Work Parties Rule SmartPrompt Optional. Specify a work parties rule if you want the system to use this rule rather than the one referenced in the Work parties field on the Process tab of any starting Flow rule form in the case's class.

Use the Parties item on the Case Designer Details tab to update the work parties rule.
Starting Processes SmartPromptSelect a flow (starter or non-starter) in this case type to designate it as a starting process. When you enter at least one flow, this case type rule – not the Creates a new work object? checkbox on the Flow form's Process tab – defines the starting processes. The system disables the checkbox on all Flow rule forms in this case type; flows not in the list are designated as non-starting processes. If you leave this list empty, use the checkbox on the Flow rule form to configure starting processes. See Flow form – Completing the Process tab.

Click the run icon () to run the flow.

Note the following:

  • If this case type is covered, enter a starter flow so that users can create cases ( ) in the Other Actions > Add Work submenu on the parent case user forms.
  • When you enter a non-starting flow in this field, the system enables the Work Object Creation Settings area on the Flow rule's Process tab.
  • If this case type is listed on the Application rule form's Details tab, flows in this list appear in the New menu on the Case Manager and Case Worker portals. You can override this behavior using the Remove in New Work Menu menu option on the case types tree.
  • When you create a case type either in the Case Designer or in the Application Express, the system generates a default starting flow and populates this field.

Specialized starting processes

If this is a specialized (circumstanced) case type rule, you can specify starting processes independently of those defined in the base case type's Starting Process list. Specialized starting processes do not affect the Creates a new work object? checkbox on the case type's Flow rule forms. For example, a non-starting flow entered here does not appear as a starting flow in the Application Explorer, or as a starting process on the case types tree. However, the flow enables the user to create a specialized case from the Add Work menu.

When creating a specialized case type using the Specialization item on the Case Designer Details tab, select the Create Starting Process? checkbox to automatically create a starter flow for the new version. This flow does not appear on the case types tree and appears as a non-starter flow on the Application Explorer.
Supporting Processes SmartPromptSelect a flow that can be added to an open case created by a previous flow execution. You can use these flows as you would spin off flows for out-of-sequence assignments in the case process.

When you enter at least one flow, the system adds the Supporting Processes Settings to the Process tab on the Flow rule form (in this case type rule's Applies To class). Use the settings to automatically route available assignments to available operators or workbaskets when the flow starts. See Flow form — Completing the Process tab.

Use the Supporting Processes item on the Case Designer Details tab to update these values. You can also use the Add > Process menu on the case types tree to update this list.
Manually start Select to allow the caseworker to start this process from a user form or the My Cases tab on the Case Manager and Case Worker portals.

On user forms, users can start supporting processes () in the Other Actions > Add Work submenu on user forms.

SmartPrompt When — Optional. Identify the When Name key part of a when rule that controls the conditions under which caseworkers can start this process.
Automatically start when parent case starts Select to automatically start this process when the parent case starts. Select if you want the system to start the process when the case is created.

SmartPrompt When — Identify the When Name key part of a when rule. If this rule evaluates to true when the parent case starts, this process also starts.
Parameters Optional. Appears when Automatically start when parent case starts is selected. The parameters in the array are defined on the flow's Parameter tab. Enter values that will appear when the property appears on a work form.
Coverable Work Types This array appears only if the Applies To class for this rule is derived from Work-Cover-. Classes in this array appear as items () in the Other Actions > Add Work submenu available in the action section on Perform, Update, and Confirm user forms. Users select an item to create a case.

SmartPrompt Select a class derived from Work- or Work-Cover- class in the current application that you want to include.

Note the following:

  • If you intend to aggregate properties in a class using the Coverable Work Types list on the Calculations tab, add the class here.
  • If Temporary object? is selected on the flow Process tab, the flow will not be available.
Use the Action > Add or Remove menus on the Case Designer case types tree to update this array.

Specialized case types

You can circumstance-qualified (by property) case type instances using the Specialization item on the Case Designer Details tab. See Process and Rules category — Case Management page. Referred to as specialized case types, these versions can:

  • Cover or be covered by other base or specialized case types.
  • Be auto-instantiated (the system copies the circumstanced property onto the subcase).
  • Use attachment categories and auto-attach functionality.
  • Use the Stages display.
  • Used in Add Work submenus.
  • Employ data propagation.

If you enter in the Coverable Work Types field a subcase type that has specialized versions, a second field appears.

SmartPrompt Select one of the following:

  • Any Specialization — Cover all specialized versions of the selected subcase type.
  • <Specialization name and value> — Select the specialized version you want to cover. To cover other versions individually, add a row ( ), enter the same subcase type in the first field, and select another version in the second field.
Manual instantiation Select so that users can instantiate this case type from the Other Actions menu on a user form, or from the My Cases tab on the Case Manager and Case Worker portals. Selected by default.

Permitted When: Optionally, identify the When Name key part of a when rule. If this rule evaluates to true, the user can create this subcase.
Automatic instantiation Select so that the system automatically creates subcases for this case type. Selected by default.

Select one of the following:

  • Upon Parent Case Start — The subcase begins when a parent case type is instantiated. Optionally, enter a when rule in the Permitted When field. If this rule evaluates to true when a parent case is created, this subcase is also created.
  • Upon Dependency Fulfillment — The subcase begins when the conditions in the dependencies definition for this case type are met. Use the Dependencies item on the Case Designer Details tab to define the dependency conditions. See Process and Rules category — Case Management page.
Max Instances Optional. Enter a positive numeric value to indicate the maximum number of instances of this case type that can be created and left unresolved.
Required Optional. Select if an instance of this subcase type must be created and resolved in order to resolve its parent. Default is not required (empty checkbox).

For complex conditions, such as requiring resolution of two out of three instances, set up tickets on the relevant assignment shapes.
Data Propagation Optional. Enabled when a Coverable Work Type is defined. Click to open the Data Propagation modal dialog. Define the propagation of properties (not property definitions), such as work parties and descriptions, from a case to its subcases. In the form, declare one or more property-set statements. They are invoked at runtime when performing an add-to-cover action such as adding a subcase to a case. The system checks the case type rule for its parent case type and searches for any defined propagation. For an example, see Process and Rules category — Case Management page

Use the Supporting Process item on the Case Designer Details tab to update these values.
Definitions action section, cover, instantiate
Related topics About flows

Up About Case Type rules