Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

When and how to use case specialization

Updated on October 9, 2015

You can a circumstance-qualify a case type rule with a single property, a date range, or a property and date range. In case management applications, circumstanced versions are referred to as specialized case types.

A property-circumstanced case type can:

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

Specialized case types are useful in situations where a case has a process that requires variations in order to meet special business requirements.

This article describes how you use the Case Designer to create specialized case types and their processes.

Note: Circumstance templates are not supported.

Suggested Approach

Example

You are working with a home loan case management application, which is structured as shown here:

Business requirements

The company provides home loans in three counties. Assessments in each county have their own tax reporting procedures and information requirements. The department has assigned one case worker to each county. The application's business analyst has determined that specializing the Tax case type enables a tax case, each with its own process, to be routed and assigned to the appropriate worker.

Configuration requirements

You will create specialized versions of the Taxes case type. Each version will have its own starting process. The cases are instantiated manually in the perform user form for the Assessment case. You will:

  • Create specialized versions of the Taxes case type.
  • Create a starter flow for each version.
  • Configure the covering relationships and the instantiation method in the parent Assessment's Case Type rule.
  • Configure the starter flows in the specialized Case Type rules so that they appear in the action area header's Other Actions > Add Work > add case submenu.

Create the specialized case types and starter flows

Open the Case Designer (> Process & Rules > Case Management > Case Designer) and select Taxes on the case types tree.

  1. On the Details tab, select the Specialization item (Edit) link.

    The Specialization dialog appears.
  2. Select the Single Value property County in the Define new specializations for Taxes on field.
  3. Click the Add Row icon ( ).
  4. In the new row, select the property's prompt value Middlesex.
  5. Select Create Starting Process? so that the system creates a non-circumstanced copy of the starter flow Work-.pyStandardCMAssignment for this specialized case type. The name is a concatenation of the word "Start" and the property value. This flow does not appear in the Starting Processes list on the specialized Case Type rule form or on the case types tree. On the Application Explorer, it appears but is not marked as a starter flow.
  6. Add two more rows and select Norfolk and Suffolk.
  7. Click OK to close the dialog. The thee new specialized case types appear on the tree beneath the base case type Taxes. By default, the Taxes starter flow is copied to each version. The Specialization item indicates that Taxes has three specialized versions.

    On the Application Explorer, the starting processes you created in the dialog appear as non-starter flows in the Taxes case type.

    You can test these three flows by clicking the Run icon ( ) on the Flow rule form.

 

Configure the covering relationships and instantiation method

  1. On the Case Designer, select Assessment.
  2. Select the Actions > Open menu item to open its Case Type rule form.
  3. In the Coverable Work Types array on the Processes tab, select County is Middlesex in the field to the right of the Taxes case type Applies To class. If the right field does not appear, move your mouse pointer to the right of the first field and click.
  4. Clear the Automatic instantiation checkbox.
  5. Add two more rows, enter the Taxes case type Applies To class in the left fields, and County is Norfolk and County is Suffolk in the right fields.
  6. Clear the Automatic instantiation checkboxes.
  7. Save the case type rule.

 

Define the starting processes in the specialized versions

  1. On the Case Designer, select the County is Middlesex version and open its case type rule from the Action menu.
  2. In the Starting Processes array on the Processes tab, replace the default StartTaxes process with StartMiddlesex, and save the rule.
  3. Replace the flows in the County is Norfolk and County is Suffolk Case Type rule forms.
    The flows do not appear on the Case Designer case types tree.

 

Test

  1. Create a Loan case, and subcases Collateral and Assessment.
  2. In the action area header on the Assessment perform harness. select Other Actions >Add Work > Start Middlesex.
  3. Create the specialized Taxes subcase in the new harness.
  4. In the Taxes perform harness, click the Assessment link.

    This opens the Assessment review harness. The Start Middlesex process has started.

Tags

Pega Platform 6.2 SP2 Case Management Financial Services Healthcare and Life Sciences Insurance Communications and Media Government Healthcare and Life Sciences Consumer Services

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us