MODULE 9 · Practical Project

Configure approval routing and validation

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

Learning objectives

Understand the concept

Translate the capstone approval policy into explicit conditions and routes. Validate required data before making a decision. Record who owns the policy and how future threshold changes should be reviewed.

Build the loan application incrementally around a traceable business outcome. Start with personas, stages and required data. Add views and rules only after the lifecycle is clear. Simulate external systems before connecting live services. Define acceptance criteria and test both success and failure paths.

Implement standard and specialist routes. Test a missing risk category, an exact threshold amount and a user without approval permission.

IntakeAssessmentDecisionResolution

A configuration example

Acceptance criterion: a complete standard-risk loan request reaches the loan-officer queue; incomplete income data blocks submission with an understandable message. A service timeout creates follow-up work and never silently approves the request.

Application: Loan Origination
Case type: Loan Request
Learning focus: Configure approval routing and validation

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

Implement standard and specialist routes. Test a missing risk category, an exact threshold amount and a user without approval permission.

Create the Loan Request case type. Add Intake, Assessment, Decision and Resolution. Configure Applicant data, intake views, approval logic and validation. Simulate a credit lookup. Test the journey as applicant, officer and reviewer, then document the results.

For this lesson, focus your notes on configure approval routing and validation. Record the inputs, configuration choice, observed result and one alternative that you rejected.

Common mistake

A working happy path is not a completed project. Include invalid data, unauthorized access, duplicate requests and external failures in acceptance testing.

Knowledge check

Why simulate a credit integration before connecting a production service?

Check your understanding

A simulation makes workflows and failure cases repeatable without relying on external availability or real applicant data.

Go deeper with official resources

Pega Academy System Architect mission
Official ’25 certification objectives