When to use a sub-case

From PegaWiki
Dividing work with child case types / This is the approved revision of this page, as well as being the most recent.
Jump to navigation Jump to search

When to use a sub-case

Description When to use a sub-case to assist with processing work
Version as of 8.4
Application Platform
Capability/Industry Area Case Management



Sometimes work might break down into multiple pieces that have a relationship or dependency with one another. These separate pieces are called a child case. A child case is a case which represents a different, but related piece of work to the original or parent case. Use the following to help identify when to use a child case:

  • Is there a distinct case life cycle from the top-level case type?
  • Can this work be run independently or by many top-level case types?
  • Will you need to report on the work independently?
  • Will this work progress in parallel to other child cases or the top-level case?

Example[edit]

At a bank, opening a new bank account requires that the applicant has a credit check. Opening a new bank account is visualized in a case type, but the credit check has a case life cycle all on its own that is critical to the overall Microjourney™ of opening an account.

The Credit Check would be a child case since a credit check may be run independently from the other aspects of opening a bank account.

By separating the credit check into its own child case, it can be reused by other top-level case types, such as applying for a loan.

Related information[edit]

Creating a case type

Creating a top-level case type

Creating a child case type

Understanding case hierarchy