Integration-backed data pages
SUPPLEMENTAL / VERSION-DEPENDENTOriginal learning guide · Pega ’25 path · Content v1.0.0
Learning objectives
- Explain integration-backed data pages 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
A data page can use integration results as its source and present a consistent structure to callers. Parameters identify the requested record; the refresh strategy governs reuse. Handle source failures separately from legitimate empty data.
A REST integration exchanges structured requests and responses with another system. A connector defines connection behavior; a data page can present the result to application rules through a consistent interface. Mapping translates external fields into the internal model. Timeouts, authorization errors, malformed responses and empty results require different handling.
Design a parameterized applicant credit data page. List success, no-record and service-failure outcomes and the caller’s response to each.
A configuration example
Simulate a credit-rating service with a response containing applicantId, rating and checkedAt. Map the rating into a dedicated result object. Route service failures for follow-up instead of treating them as a negative credit decision.
Application: Loan Origination Case type: Loan Request Learning focus: Integration-backed data pages 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
Design a parameterized applicant credit data page. List success, no-record and service-failure outcomes and the caller’s response to each.
Write sample success, unauthorized and timeout outcomes. Map the successful response. Decide which failures are safe to retry and how a user can continue without exposing credentials or raw service errors.
For this lesson, focus your notes on integration-backed data pages. Record the inputs, configuration choice, observed result and one alternative that you rejected.
Common mistake
Knowledge check
Does an HTTP success response guarantee useful business data?
Check your understanding
No. Validate the response structure and business meaning before using the data.
Go deeper with official resources
Pega Academy System Architect mission
Official ’25 certification objectives
