Pega's Case Life Cycle

Microjourneys® are the Life Cycles, or units of work, that deliver a meaningful result to customers and users. Microjourneys are a part of the overall customer journey that achieves all or a subset of the required business outcomes.  

Identifying Microjourneys requires you to consider an end-to-end experience for end users. This exercise delivers an incremental piece of functionality that teams can put into production quickly, which adds immediate value. You can capture Microjourneys directly in Pega Platform by breaking the Microjourney down into the building blocks, which we call the three pillars of your application.   

The diagram below shows the three pillars of your application. The three pillar are the Case Types and Strategies, Personas and Channels, and the Data and Interfaces associated with the Microjourney:

As a Business Architect, capturing the three pillars directly in App Studio, allows you to build consensus quickly and easily around the solution by visually documenting:

• The Microjourney (Case Life Cycle) visualizes the path of your business processes toward resolution.
• Personas represent the people that are involved in your processes and the Channels that they use to interact with a Case.
• Data is the information that your workflow requires to achieve resolution, and the Interfaces are how that data is accessed.

A Case Type is an abstract model of a business transaction. Case Types model repeatable business transactions. A Case is a specific transaction instance. To model the online order transaction in Pega Platform, you define an online order Case Type that advances from submission to processing and then delivery. As shown in the following image, each time a user submits an online order, Pega Platform creates an order Case and assigns the Case a number.

You define the Case Life Cycle for a Case Type to help you visualize the work that must be completed as part of the desired business transaction. The Case Life Cycle represents the business model of the Microjourney™. The Case Life Cycle models the path your Case follows to resolution. The major building blocks of the Case Life Cycle are Stages, Processes, and Steps.

The following image depicts the Case Life Cycle for the online order Case Type. 

In the following figure, click the + icons to learn more about the building blocks of a Case Type:

Consider the following naming conventions when you create Case Types as well as Stages, Processes, and Steps in a Case Life Cycle.

When you select a name for the Case Type, focus on the outcome of the business process rather than on the actions that users need to complete. Ensure that the name of the Case Type clearly conveys the purpose of the Case Type. For example, the name Financial operations is ambiguous and non-specific, but the names Loan Application Review, Mortgage Request Review, or Credit Card Dispute precisely communicate their purpose.

Name Stages by using a noun, noun phrase or gerund (which acts as a noun phrase) to describe the section context. As much as possible, try to use no more than two words. Use names that are meaningful and relevant to business users. In the previous example, the company processes the order in the second Stage of the order Case Life Cycle, so you name the Stage Processing.

For Stages that do not resolve the Case, test your Stage naming choice by checking if it sounds correct in the following test sentences:

• This Case is in <Stage name>.
• When does this Case move to <Stage name>?
• How many Cases are in <Stage name>?

Read the sentence aloud with your proposed Stage name. If the Stage name does not correctly fit in these sentences, consider revising. 

Name Processes and Steps by using the verb + noun naming convention. In the order Case example, in the Processing Stage, you name the process Process order. You name the Steps in this Process Check inventory and Pack items.

Check your knowledge with the following interaction: