Creating data relationships
1 Task
10 mins
Scenario
During recent analysis and design workshops, U+ Hotels stakeholders confirmed that new Data Objects introduced at the application level must be added to Case Types so that users can capture and manage data efficiently during Case processing.
In the Complaint Resolution Case Type, to support the Collect Complaint Details Step, a new reusable reference Data Object called Complaint Category was created at the application level. This Data Object standardizes how complaints are categorized and is reused across workflows for routing, service-level agreement assignment, reporting, and analytics.
In the Partner Onboarding Case Type, onboarding teams must upload and track partner documents during the Upload Partner Documents Step. These documents are specific to each onboarding Case and must be stored with the Case for audit and compliance purposes.
As a Solution Builder, you are tasked with creating the appropriate data relationships to support both use cases.
-
The Complaint Category Data Object is related to the Complaint Resolution Case Type using a single‑record Data Reference relationship, allowing Cases to select a standardized category from centrally managed reference data.
-
The Document Data Object is related to the Partner Onboarding Case Type using an Embedded Data relationship, allowing each onboarding Case to store and manage its own set of partner‑submitted documents.
The following table provides the credentials you may need to complete the challenge:
| Role | User name | Password |
|---|---|---|
| Solution Builder | [email protected] | pega123! |
After completing this challenge, you should be able to:
- Create a single-record Data Reference relationship between a Case Type and a Data Object.
- Create an Embedded Data relationship that stores a list of records with a Case.
Detailed Tasks
1 Create data relationships
Use the technical documentation linked in the Doc Journey above to complete the assigned tasks. The technical documentation might have more information than you need to complete the tasks.
Acceptance criteria
Task 1: Create the primary Complaint Category relationship
- The Complaint Resolution Case Type includes a field named Complaint Category.
- Uses a Data Reference relationship.
- References the Complaint Category Data Object.
- Allows selection of one category per case.
- The Complaint Category data is not stored directly on the case.
Task 2: Create the Partner Documents embedded relationship
- The Partner Onboarding Case Type includes a field named Partner Documents.
- Uses Embedded Data.
- References the Document Data Object.
- Supports multiple document records per case.
- The Document data is stored with the case and is not reused across cases.
Directions
- Open the Complaint Resolution Case Type.
- On the Data Model tab, add a new field with the following configuration:
- Field name: Complaint Category
- Field type: Data Reference
- Data object: Complaint Category
- Options: Single record
- Save your changes.
- Open the Partner Onboarding Case Type.
- On the Data Model tab, add a new field with the following configuration:
- Field name: Partner Documents
- Field type: Embedded Data
- Data object: Document
- Options: List of records
- Save your changes.
Available in the following mission:
Want to help us improve this content?