Skip to main content

Simulating an external data source

1 Task

10 mins

Visible to: All users Applies to: Pega Platform '26
Beginner
Data Integration
Data Management
English

Scenario

In the Travel Management Customer Support (TMCS) application, many guest complaints concern a specific booking. U+ Hotels integrates with an external Global Distribution System (GDS), the centralized reservation system named in the Blueprint integration framework, which exposes live booking details over a REST service as JSON.

The GDS is not yet available in the development environment, so you cannot call the live service while you build the Complaint Resolution case. To avoid blocking development, your Lead System Architect asked you to build the integration against a simulated data source that returns representative JSON. You can then build and test the case now, and re-point it at the live GDS later by turning the simulation off, without reworking the case.

Note: This challenge has been configured with Single sign-on (SSO) using your Pega Academy credentials. If you are not automatically signed-in to the challenge environment after initializing the instance, you may use the credentials provided.

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 Data Object with a REST integration.
  • Simulate an external data source by using a Data Transform.
  • Surface simulated data on a Case Type by mapping a parameter.

You must initiate your own Pega instance to complete this Challenge.

Initialization may take up to 5 minutes so please be patient.

Detailed Tasks

1 Simulating an external data source

Solution Builder Intermediate Simulating an external data source Doc Journey

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 the Property Contact Data Object

  • A Data Object named Property Contact is configured in the TMCS application.
  • The integration is configured as follows:
    • Name: Property Contact Integration
    • Description: Retrieves property contact details
    • Method: GET
    • URL: https://localhost:8080
  • The initialize call uses the following Sample JSON Response:
    <code>{
      "propertyName": "U+ Hotels Downtown",
      "city": "New York",
      "contactPhone": "+1-111-555-1111",
      "frontDeskEmail": "[email protected]"
    }</code>
  • The following Text fields are created automatically by the wizard on the Property Contact Data Object: PropertyName, City, ContactPhone, and FrontDeskEmail.

Task 2: Simulate the data source

  • A Data Transform is used to simulate the external data source.
  • The Data Transform applies conditional logic on Param.BookingID as follows:
    <code>When Param.BookingID == "RES-1234"
      PropertyName = "U+ Hotels Downtown"
      City = "New York"
      ContactPhone = "+1-111-555-1111"
      FrontDeskEmail = "[email protected]"

    When Param.BookingID == "BK-7001"
      PropertyName = "U+ Hotels Central"
      City = "London"
      ContactPhone = "+44-20-5555-1111"
      FrontDeskEmail = "[email protected]"

    When Param.BookingID == "BR-8492"
      PropertyName = "U+ Hotels Marina"
      City = "Dubai"
      ContactPhone = "+971-4-555-1111"
      FrontDeskEmail = "[email protected]"

    When Param.BookingID == "BR-9876"
      PropertyName = "U+ Hotels Lakeside"
      City = "Chicago"
      ContactPhone = "+1-222-555-2222"
      FrontDeskEmail = "[email protected]"

    When Param.BookingID == "BR-2022"
      PropertyName = "U+ Hotels Golden Gate"
      City = "San Francisco"
      ContactPhone = "+1-333-555-2222"
      FrontDeskEmail = "[email protected]"</code>

Task 3: Surface the property contact

  • The Complaint Resolution Case Type includes a field named Property Details.
  • The field is a single page, uses Property Contact Data Object class and source is configured as the above simulated Data page.
  • The parameter mapping sets BookingID to .ReservationID.
  • Property Details Fields PropertyName, City, ContactPhone, and FrontDeskEmail are added and displayed as Read only in Gather Supporting Evidence step under Intake Stage.

Directions

  1. Create a Property Contact Data Object with a REST integration configured as detailed in the Acceptance criteria, using the initialize call JSON to generate the PropertyName, City, ContactPhone, and FrontDeskEmail fields.
  2. Configure a Data Transform to simulate the external data source, mapping the Param.BookingID values to the property records as detailed in the Acceptance criteria.
  3. In the Complaint Resolution Case Type, add a Property Details field that is a single page and uses the Property Contact Data Object.
  4. Configure the parameter mapping so that BookingID is set to .ReservationID.
  5. Save your changes.


Available in the following mission:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice