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

Table of Contents

Article

Introduction to Case Type design

The Case Type Definitions gadget (under the pega button > Process & Rules > Case Management landing page) is used to configure and manage the structure of the case management application. This article describes the information the gadget provides and some of the functions you can use.

Note: This article describes PRPC 6.1 SP2 features. For similar features in PRPC 6.2, see Introduction to the Case Designer.

About the gadget

The Case Type Definitions gadget is organized into a tree structure as shown here:

The tree comprises a group of case types, each of which inherits from Work-Cover- and has a Case Type rule. A case type can cover or be covered by another case type. The tree displays covered case types as indented nodes beneath the covering nodes.

Note: You can create work types that inherit from Work- . They can be covered but cannot cover other case or work types.

The tree structure uses three elements in the case type hierarchy:

  • Top-level case — Serves as a top-level parent case type within a work pool and is not covered by another case. A work pool can contain more than one top-level case. In the Employee OnBoarding Application shown above, New Hire Case is the top-level case.
  • Subcase — Nested beneath (covered by) a case at any level, a subcase typically must be created and resolved before the parent case can be resolved. A subcase can also parent other subcases. Unless referred to in the context of its parent/child relationships, a subcase is usually called a case. In the example, Orientation Meetings and Equipment Setup are subcases of New Hire Case.
  • Task — The gadget enables you to add a case type called a task. Its class structure and processing behavior are the same as a case.This term is used only to describe its role within the application. Although a task can be used at any level within the hierarchy, it most often represents low-level work nested under a parent case. For example, Benefits and Mentor Meetings are tasks nested under Orientation Meeting. (Do not confuse case management tasks with task shapes in a flow.)

Using the gadget

Use the gadget to:

  • Add new case types in the application. When you create a case type, you can designate it to display in the gadget as a case or as a task (each has its own icon). The gadget helps you simplify the process of creating the Class, Case Type, and other standard rules used by a case type.
  • Extend the hierarchy of subcases and tasks. As the application evolves, the gadget lets you quickly create or reuse existing case types,
  • For each case type, manage these work processing functions:
    • Define service level goals and deadlines.
    • Create attachments categories.
    • Determine whether to automatically create subcase work items when a parent case is started or enable the user to manually create the work.
    • Map user roles to work item access.
    • Indicate whether a subcase or task must be created and resolved in order to resolve its parent case.
    • Limit the number of subcases that can be created manually or automatically.

The gadget layout

The gadget uses a tree grid layout, which contains the following columns:

  • Name — The name of the case type. An icon appears in front of the name to indicate whether it has been defined as case or as a task.
  • Instantiation — States whether a work item for this case type is automatically started when the parent case starts, or when the user manually starts it while working on the parent case.
  • Required — A checkmark indicates that the case or task work must be created and resolved in order to resolve its parent.
  • Max Allowed— For this case type, the maximum number of case items that can be added to the parent.
  • Owner— Displays the access role associated with this case type.
  • Attachments — The number of attachment categories defined for each case type.
  • Legacy — Indicates that this work type extends from Work–, not Work–Cover–; it can be covered by case types but cannot cover other work or case types.

How to create a new case

  1. Add the case or subcase that is the top-level case directly to the work pool by right-clicking and choosing Add.
  2. In the Add dialog, enter a new case name and click OK.

    The new Health Benefits case appears under the work pool:

    The system creates the HealthBenefits class, a Case Type rule, a standard case management starting flow rule, and other supporting rules, which appear in the Application Explorer. (To prevent the creation of the starting flow, clear the Create Start flow checkbox in the Advanced Settings section of the Case Type Add dialog.)
  3. To modify the processing behavior of the new case or task, select the item and right click to open the Properties menu. The options enable you to define attachment categories, service level goals and deadlines, access roles, and instantiation preferences.
  4. To extend this case, select it in the gadget, right click, and add another case or task:

Optionally, use the Advanced Settings to configure the case as follows:

  • Derives From. Choose the work type this new type derives from.
  • RuleSet. Choose the RuleSet of the new type.
  • Version. Choose the RuleSet version.
  • Create start flow. Click to create a standard start flow rule for this type.

As you build out a case hierarchy, check your case definition tree structure using the Case Manager portal.

Revise the top-level case type tree structure to define case types that require, or may evolve, unique processes. Afterwards, you may further define the appropriate subcases, and add associated tasks.

Note: If the case or task is not a case type (not in Work-Cover- class) you can only Rename and Remove the node using the right-click menu.

About attachments

To create and manage Attachment Categories for a case or task:

  1. Right-click a case or subcase and choose Properties > Attachments.
  2. In the Attachments dialog, click () to add a new attachment category:
  3. Enter the attachment description, select its type ( file or URL), and choose the attachment category. Indicate whether the attachment is required. If the attachment type is a file, click the Browse button to locate it. Its name appears in the File Name field. If the attachment is a URL, enter the address in the Reference field. Indicate whether the system will create the attachment automatically. See How to enable attachment security using attachment categories and How to control access to categorized attachments.
  4. Click OK to save your edits and close the dialog.

About Goals and Deadlines

The Goals And Deadlines configuration screen allows you to easily view and change the Overall Service Level settings for the selected case type.

  1. Right-click a case or subcase and choose Properties > Goals & Deadlines.
  2. Use the Goals and Deadlines for (case item name) will be calculated from: field to define when the starting flow's goal and deadline countdowns begin. One of the following events starts the count:
    • Me — When the user starts this case
    • My Parent Case — When the parent case starts
    • My top-level case — When the top-level case in this application starts


  3. Select Goal time from Start and Deadline from Start, in days, hours, minutes, and seconds.

About instantiation

Instantiation allows subcase items or tasks to be created:

  • By the system when the parent work starts
  • When the user selects the item from the Add Work... action drop-down list in the parent case's work form.


Note: Users can also manually add subcase and task items (called ad-hoc work) to existing cases within the Case Management portal. Ad hoc work items are not case types and are not formally included in the case management application structure. These items appear only in the portal and not in the gadget.

Tags:

Published September 13, 2010 — Updated October 7, 2014


50% found this useful

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.