Validation and data references
Original learning guide · Pega ’25 path · Content v1.0.0
Learning objectives
- Explain validation and data references 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
Validation enforces required structure and business constraints. A data reference points to existing information rather than always copying it. Decide whether the case needs the current referenced value or a historical snapshot for audit.
A data object groups related fields. Relationships connect objects without forcing all data into one flat case record. Data pages provide a consistent access pattern to sourced information. Refresh and scope choices determine when data is reused and when it is fetched again. Data transforms map or initialize values; validation rejects values that do not meet business requirements.
Require a positive requested amount. Decide whether an approved loan should retain the product rate used at approval even if the product rate later changes.
A configuration example
Create Applicant with Name, Email and Annual income. The Loan Request references Applicant and stores Requested amount. Use a data page to retrieve reference loan products. Calculate an affordability indicator from approved inputs rather than accepting a client-provided result.
Application: Loan Origination Case type: Loan Request Learning focus: Validation and data references 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
Require a positive requested amount. Decide whether an approved loan should retain the product rate used at approval even if the product rate later changes.
Draw Applicant → Loan Request → Loan Product. Identify the system of record for each object. Define when product data may be cached and when a fresh read is required. Write validation examples for missing email and non-positive requested amounts.
For this lesson, focus your notes on validation and data references. Record the inputs, configuration choice, observed result and one alternative that you rejected.
Common mistake
Knowledge check
How does a data transform differ from a validation rule?
Check your understanding
A transform sets or maps data. A validation rule checks whether data satisfies conditions and reports errors.
Go deeper with official resources
Pega Academy System Architect mission
Official ’25 certification objectives
