Statuses, service levels and urgency
Original learning guide · Pega ’25 path · Content v1.0.0
Learning objectives
- Explain statuses, service levels and urgency in the context of a loan application.
- Identify the configuration decisions and test an expected outcome.
- Recognize a common mistake before it affects users.
Understand the concept
Status summarizes the state of work. A service-level agreement defines timing expectations such as goals and deadlines. Urgency influences prioritization. Time calculations depend on the configured calendar and should be tested across non-working periods.
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.
Choose a pending status for credit review. Define a goal and deadline and document the expected behavior when the deadline is missed.
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: Statuses, service levels and urgency 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
Choose a pending status for credit review. Define a goal and deadline and document the expected behavior when the deadline is missed.
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 statuses, service levels and urgency. Record the inputs, configuration choice, observed result and one alternative that you rejected.
Common mistake
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
