Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Changing the data source of a data page

Updated on March 16, 2021

After running the Integration wizard, open the data page to replace the source with the connector to indicate where to source information from, and then set up your mapping transforms.

Pega Customer Service Implementation Guide
This scenario describes how to integrate contact details. For more information about other data page sources, see Changing the data source of a data page.
  1. In the navigation pane of Dev Studio, click RecordsData ModelData Page.
  2. Search for and open your data page.
    The example used in this is particular data integration scenario uses the default D_Contact_Details data page.
  3. In the Data Sources section, in the Source field, change the data source into an aggregated data source.
    Note: It is recommended to use an aggregated data source because aggregated data sources support a much larger set of use cases, for example, multiple connector calls and post-call enrichment.
  4. In the Aggregate source name field, enter the name of your source, for example, Con, to indicate a contact.
  5. In the Source field, select Connector.
  6. In the Type field, select REST.
  7. In the Name field, enter or select your GetContact connector.
  8. In the Request Data Transform field, enter GetContact_Down and then click Open to create and configure the transform.
    Setting up the Down request data transform indicates mapping to the integration data model.

    Note: Pega uses a naming convention for the request and response data transforms. It is recommended to name the request data transform: your method name_Down. For example, GetContact_Down. The same rule applies to the response data transform: your method name_Up. For example, GetContact_Up. The _Down suffix maps to your connector (your integration data model), and the _Up suffix maps from your connector (to the Pega Customer Service contact data model). It is not recommended to use the _Request and _Response naming convention because if you are calling a service it will be flipped.

    1. In the Context section, point to your application layer.
    2. Click Create and open.
    3. In the Action field, select Set.
    4. In the Target field, press the Down arrow key, and then enter .request.query_GET.ContactId, based on the structure created by the system.
      Note: Depending on your business needs and how your connector is structured, your .request.query_GET.ContactId structure will vary. The .query_GET is always a part of a GET method request, but if you passed parameters instead of a query string or added headers when running the Integration wizard, the Target field will look different.
    5. In the Source field, enter your ContactId value, which is specified on the Parameters tab on the data page.
    6. Click Save.
  9. Under the Request Data Transform field, click Parameters, select the Pass current parameter page check box, and then click Submit.
    When you select the Pass current parameter page check box, the system passes the current parameters from the Parameters tab of the data page.
  10. In the Response Data Transform field, enter GetContact_Up and then click Open to create and configure the transform.
    Setting up the _Up request data transform indicates mapping from the integration data model.
    1. In the Context section, point to your application layer.
    2. Click Create and open.
      When you create data transforms directly from the data page, the system prepopulates the Definition tab with useful actions, for example error handling, which you can enable by right-clicking an action and selecting Enable.
    3. In the 1.1 row, in the Action field, change the default value to Set.
    4. In the 1.1 row, in the Target field, enter .FirstName.
    5. In the 1.1 row, in the Source field, press the Down arrow key, and then enter .response_GET.Contact.FirstName.
      Note: The response data transform is the same as the response XML parse Map to key , on the Methods tab of the REST connector: response_Method.Class name.Property, for example, respone_GET.Contact.LastName.
      An example GetContact_Up data transform setup for multiple properties
      An example setup for multiple properties in the GetContact_Up data transform
    6. Click Save.
  11. Under the Response Data Transform field, click Parameters, select the Pass current parameter page check box, and then click Submit.
  12. If the endpoint URL is different than the endpoint URL in the connector rule, in the Endpoint URL field, enter the correct URL.
    An example connector setup on the data page screen
    An example connector setup with an aggregate source
  13. Click Save.

Tags

Pega Customer Service 8.6

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us