MODULE 2 · Case Management

Case types and lifecycles

Original learning guide · Pega ’25 path · Content v1.0.0

Learning objectives

Understand the concept

A case type defines repeatable work, while a case is one instance of that work. A lifecycle organizes major milestones. Model stages around meaningful business progress rather than arbitrary form boundaries.

A case type describes a repeatable business outcome. Stages group major milestones; processes organize work inside a stage; steps describe user tasks or automations. Assignments wait for a person or queue. Routing selects the responsible resource. Goals and deadlines describe service expectations; urgency helps prioritize work but does not replace a routing policy.

Create an Intake, Assessment, Decision and Resolution lifecycle. Explain what must be true for an individual request to leave each stage.

IntakeAssessmentDecisionResolution

A configuration example

Design Intake → Assessment → Decision → Resolution. Intake collects applicant details. Assessment routes a credit review to a work queue. A conditional approval process requests additional authority for larger amounts. Resolve the case only after communicating the decision.

Application: Loan Origination
Case type: Loan Request
Learning focus: Case types and lifecycles

Given: a known applicant and a documented policy
When: the configured step or rule executes
Then: compare actual data and routing with the expected outcome

Conceptual configuration plan, not an importable Pega rule. Labels and tools vary by release. Use the official mission environment to inspect current screens.

Try it yourself

Create an Intake, Assessment, Decision and Resolution lifecycle. Explain what must be true for an individual request to leave each stage.

Sketch the four stages. Add one assignment to each of the first three. Define a goal of one business day for assessment and a deadline of two. Add a child case only if a separately tracked piece of work has its own lifecycle.

For this lesson, focus your notes on case types and lifecycles. Record the inputs, configuration choice, observed result and one alternative that you rejected.

Common mistake

Using a status as a substitute for a stage makes the lifecycle difficult to understand. Status reports current state; stages organize the work that changes it.

Knowledge check

When is a child case more suitable than another step?

Check your understanding

When the related work needs an independent lifecycle, ownership or completion tracking while remaining related to the parent.

Go deeper with official resources

Pega Academy System Architect mission
Official ’25 certification objectives