Tracer and Clipboard debugging
SUPPLEMENTAL / VERSION-DEPENDENTOriginal learning guide · Pega ’25 path · Content v1.0.0
Learning objectives
- Explain tracer and clipboard debugging 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
Tracer helps investigate rule execution; Clipboard helps inspect runtime data where supported. Use a narrow reproduction and relevant events to reduce noise. Access to diagnostic tools should be restricted and traces can contain sensitive information.
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.
Write a debugging plan for an incorrect approval route: verify input, locate decision execution, inspect output and check assignment routing.
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: Tracer and Clipboard debugging 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
Write a debugging plan for an incorrect approval route: verify input, locate decision execution, inspect output and check assignment routing.
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 tracer and clipboard debugging. Record the inputs, configuration choice, observed result and one alternative that you rejected.
Common mistake
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
