Digital process automation in Pega CPSSA
What the domain tests
Digital process automation in Pega CPSSA focuses on modeling work as case types and controlling how work moves, waits, escalates, and is routed. Expect questions on case type inheritance, stages and processes, optional actions, routing, service levels, and urgency.
Core rules
- A case type defines a lifecycle. Stages are the major phases; processes hold the steps that people and automations perform.
- Reuse through case type inheritance, and specialize behavior with circumstancing rather than copying a case type for every variation.
- Optional actions belong to a stage and appear only when the case is in that stage and the user has the privilege.
- Route work to a work queue with skills, or to a specific operator, using routing rules; keep routing data on the case, not in the UI.
- Service levels can be defined at case level or stage level. A stage-level goal/deadline is recalculated when the stage is re-entered; a case-level SLA is not reset in the same way.
- Use urgency and escalation to prioritize work, but do not encode policy in urgency alone.
Worked example
An insurer needs a claims case with Intake, Review, and Approval stages. In Review, an adjuster can choose 'Request more information'; that action should not appear in Approval. Route Review work to a queue named ClaimsReview with a required skill, set a 3-day stage-level goal, and escalate to a supervisor at deadline. For a state-specific approval rule, use circumstancing on the approval decision rather than a new case type. Reasoning: the optional action is stage-scoped, the queue/skill controls eligibility, and the stage SLA follows the phase. Circumstancing preserves one lifecycle and avoids duplicate maintenance.
Traps
Putting all conditional logic in one process makes the lifecycle opaque; prefer optional actions and stage transitions. A stage-level SLA that resets on re-entry can surprise testers. Routing by hard-coded operator IDs breaks when staff change. Inheriting a case type without checking inherited stages, SLAs, and access can leak behavior into the child.