MODULE 8 · Testing and Troubleshooting

Configuration issues and performance basics

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

Learning objectives

Understand the concept

Slow or incorrect behavior may come from repeated data access, an unsuitable refresh policy or unexpected rule selection. Reproduce the problem with measurable evidence before choosing a fix. Performance changes must preserve correctness.

Use focused tests to validate rules and broader tests to validate journeys. Compare expected and actual data before changing configuration. Tracer and Clipboard help investigate rule execution and runtime values where supported. Use diagnostic tools in controlled environments and avoid exposing personal data. Deployment requires functional, integration, security and regression checks.

Compare one intake journey with expected versus repeated service calls. Propose a cache change and identify how to test that applicant data stays isolated and current.

IntakeAssessmentDecisionResolution

A configuration example

For an approval-routing defect, reproduce a known amount and risk combination. Inspect input values, the decision result and the assignment destination. Add a boundary regression test after fixing the responsible rule.

Application: Loan Origination
Case type: Loan Request
Learning focus: Configuration issues and performance basics

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

Compare one intake journey with expected versus repeated service calls. Propose a cache change and identify how to test that applicant data stays isolated and current.

Create a test plan for intake, validation, routing, service failure and resolution. Include a permission-denied scenario. Record expected results and rerun the affected journey after a change.

For this lesson, focus your notes on configuration issues and performance basics. Record the inputs, configuration choice, observed result and one alternative that you rejected.

Common mistake

Changing several rules at once can hide the original cause. Form a hypothesis and verify one relevant change at a time.

Knowledge check

Why combine unit tests with a complete case journey?

Check your understanding

A rule may work in isolation while the surrounding mappings, permissions or workflow produce an incorrect overall result.

Go deeper with official resources

Pega Academy System Architect mission
Official ’25 certification objectives