Skip to main content

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

Verifying a scenario-based integration

Updated on March 16, 2021

After you create a REST integration and set up your data page source, verify your integration to check whether the integration is running end to end without errors. It is recommended to verify that the data page returns correct values, and then verify that the application UI uses the integrated data.

Pega Customer Service Implementation Guide
Validate your integration for the .FirstName property so that later you can clone the mapping for other properties and expand your integration.

    Verify that your data page returns correct values

  1. Review the connector configuration.
    Similarly to a service rule, a connector has methods. In this example, the connector has a GET method, which is a query string of ContactId that is mapped to .request.query_GET.ContactId. The connector also has a response, which is an XML parse rule with the response_GET.Contact ContactMap to key. The XML parse rule is the opposite of the string rule, in which you can see the Contact parameter with mapping and the underlying .FirstName parameter with mapping.
  2. On the data page screen, click ActionsTrace.
    Use the Tracer tool to debug flows, activities, services, parse rules, and declarative rules. The Tracer tool provides full debugging facilities, including step-by-step execution, breakpoints, and watch variables. For example, verify whether you provided the same parameters in both request and response. In this example, the system returns a value for the .FirstName property. Only one person can use the Tracer tool on a single service at a time. For more information, see Application debugging using the Tracer tool.
  3. On the data page screen, click ActionsRun.
    1. In the Value field, enter the value for your parameter.
      In this example scenario, enter the value for the ContactId parameter. Your parameters may vary, but the default parameter is ContactId.
    2. Click Run.
    3. Review the results.
      An example of the data page returning values
      An example Clipboard page with populated properties
      Result: If the data integration succeeded, the system will display the data. If there is no data displayed, switch to the Tracer tool to investigate the issue.
  4. Verify that your application UI uses the integrated .FirstName property

  5. In the header of Dev Studio, click Launch portalInteraction Portal.
  6. In the application header, run a new interaction by clicking NewPhone call and after verifying the contact, run the Update contact profile service case.
    Note: The system does not have enough details to populate the entire interaction because in this scenario only the first name was mapped in the interface data structure.
  7. In the Interaction Portal, in the upper-right corner, click Your operator nameClipboard.
  8. Search for and open your data page.
  9. Verify that the .FirstName property returns a set value.
Result: After you integrate one property and validate your integration, integrate more properties. For more information, see Integrating data after running the Integration wizard.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us