MODULE 6 · Integration Fundamentals

Request and response mapping

SUPPLEMENTAL / VERSION-DEPENDENT

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

Learning objectives

Understand the concept

Mapping translates between external and internal names, types and structures. Treat third-party responses as untrusted input. An amount represented as a string or in smaller currency units must be transformed deliberately.

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.

Map external applicant_id and credit_score into internal fields. Test a missing score, a malformed value and an unexpected extra response field.

IntakeAssessmentDecisionResolution

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: Request and response mapping

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

Map external applicant_id and credit_score into internal fields. Test a missing score, a malformed value and an unexpected extra response field.

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 request and response mapping. Record the inputs, configuration choice, observed result and one alternative that you rejected.

Common mistake

Treating an integration failure as valid business data can create incorrect decisions. Preserve a separate error outcome and avoid logging secrets.

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