MODULE 3 · Data Modelling

Data objects, fields and relationships

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

Learning objectives

Understand the concept

A data object describes a business entity using typed fields. A relationship connects an object to another object or collection. Cardinality matters: one applicant may submit many requests, and each request may reference a particular product.

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.

Define Applicant, Loan Request and Loan Product. Choose suitable types for email, requested amount and application date; mark which relationships can contain several records.

IntakeAssessmentDecisionResolution

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: Data objects, fields and relationships

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

Define Applicant, Loan Request and Loan Product. Choose suitable types for email, requested amount and application date; mark which relationships can contain several records.

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 data objects, fields and relationships. Record the inputs, configuration choice, observed result and one alternative that you rejected.

Common mistake

A successful lookup does not mean the data will stay current. Define refresh behavior deliberately and distinguish an empty result from a connection failure.

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