Adding an external data source to a data type
1 Task
25 mins
Scenario
You are a Solution Builder working on TGB's HRApps application. The medical plan options presented to employees during benefits enrollment are currently sourced from data stored locally within the application. To ensure employees always see the most current and accurate plan information, you will reconfigure the application to source medical benefit data from an external REST API.
You will create a new Data Object connected to the live REST API, update a Data Transform to map the external data to the existing Data Model, and integrate the externally sourced data into the Select Medical Coverage view.
The following table provides the credentials you need to complete the challenge:
| Role | User name | Password |
|---|---|---|
| Solution Builder | SSA@TGB | pega123! |
After completing this challenge, you should be able to:
- Create a Data Object with an external REST data source.
- Map response fields from a REST API to a Data Object.
- Update a Data Transform to append and map data from an external Data Page.
- Configure a Case View to display externally sourced data.
Detailed Tasks
1 Adding an external data source to a data type
Use the technical documentation linked in the Journey map 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 a Data Object with an external data source
- A Data Object named Medical Benefit is created with a new system configured as follows:
Field Value Name Medical Benefit Description Medical Benefit plans Endpoint URL http://localhost:8080/prweb/api/HRAppsPackage/v1/benefits Authentication Basic Username SSA@TGB Password pega123! - The following fields from the Plans object are mapped from the REST response:
DeductibleOutofPocketMaxTierPlanIdName
- The wizard automatically creates the MedicalBenefit Data Object and the
D_MedicalBenefitsavable Data Page.
Task 2: Update the MedicalPlans data source
- A copy of the MapMedicalPlans Data Transform is saved to the current application Ruleset.
- The Pages & Classes tab is configured as follows:
Page Name Class Primary.pxResultsTGB-HRApps-Data-MedicalPlansD_MedicalBenefitTGB-HRApps-Data-MedicalBenefit - The Definition tab contains the following steps:
Step Action Target Relationship Source 1 Append and Map to Primary.pxResultseach page in D_MedicalBenefit.Plans1.1 Set .PlanIdNone .PlanId1.2 Set .NameNone .Name1.3 Set .DeductibleNone .Deductible1.4 Set .OutofPocketMaxNone .OutofPocketMax1.5 Set .TierNone .Tier
Task 3: Update the Select Medical Coverage view
- In the Benefits Enrollment Case Type, the MedPlan (Medical Plans) Query Data Object is added to the Select Medical Coverage Step User Action view with the following fields in order:
Order Field Type 1 Waive Medical Boolean 2 Medical Plan ID Picklist 3 MedPlan (Medical Plans) Query 4 Medical plan cost Currency - The MedPlan view is configured with the following properties in order:
NameOutofPocketMaxPlanIdTierDeductible
Directions
- Navigate to Data and create a new Data Object named Medical Benefit, creating a new system with the connection and authentication configuration as detailed in the Acceptance criteria.
- Click , map the required fields from the Plans object, and click to complete the wizard.
- Open the MapMedicalPlans Data Transform, save a copy to the current application Ruleset, and configure the Pages & Classes and Definition tabs as detailed in the Acceptance criteria.
- Open the Benefits Enrollment Case Type, navigate to the Select Medical Coverage Step, and add the MedPlan (Medical Plans) Query Data Object to the User Action view as detailed in the Acceptance criteria.
- Configure the MedPlan view properties as detailed in the Acceptance criteria.
- Save your changes.
Disponibile nelle seguenti missioni:
Want to help us improve this content?