Skip to main content

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

Stage-based case management

Updated on October 8, 2023


This content applies to On-premises, Client-managed cloud and Pega Cloud environments

Case management was introduced in PRPC 6.1 to enhance existing Work Objects. In Pega 7.1 Stages were introduced as the key starting point for Case configuration. Initially Stages were linked to Statuses, but these Stages were reworked to be independent from the Case Status.

Work Objects rely on a single Flow rule with embedded Flow rules to define the overall process. Staged-based case management replaced the previous way of developing processes, because it is more modular and scalable.

Advantages of staged-based case management include:

  • Processes are easier to reuse.
  • Improves compatibility with App Studio
  • Improves alignment with business teams.
  • Improves compatibility with new case management capabilities, such as Personas and Data Management

For more information about case management, see:

How to identify

The rows in the output report from the Pega Cloud Readiness Tool are:

Area:  Stage-based Case Management
Rule Type:  Rule-Obj-CaseType or Rule-Obj-Class

How to modernize

Pega recommends using Pega Express to define each process, including the stages, steps, data types, personas, and so on.

To implement staged-based case management, begin by analyzing the existing process.  Re-think the existing process and adapt it to the latest business requirements, if need

Next, define the stages for the process.  Use top level sub-Flows to create a first draft.  For the draft, also capture alternative paths (such as tickets, or forks leading to alternative end shapes).  Convert these into Alternate Stages.

Before moving forward, confirm with the business users that the Stages meet the business requirements.   The new implementation can deviate somewhat from the original implementation, as long as the new implementation meets the business requirements.

After defining the stages, analyze the process at each stage to determine which Data Types and which Personas are needed.

Next, define the steps for each of the previously defined stages.  Identify possible steps to be defined by looking for utility shapes and assignment shapes within the sub-flow containing the stage you are working on.  Review the predefined steps within case management and use OOTB steps when ever possible.

Any functionality that was previously implemented using Activities must be reworked to use OOTB features.

Any activity or integration that executes a task that is not required as part of the synchronous process must be converted into a Queue Processor.

Confirm that all statuses are consistent with the original implementation.

For more information about Pega Express, see:


  • Previous topic Pega Modernization Implementation Guide
  • Next topic Data Pages to manage data from external systems (Live Data)

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us