Skip to main content


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

Mapping Blue Prism request and response data in your application

Updated on April 6, 2022

Process Blue Prism automation results in your application in an efficient way by mapping the Blue Prism process data model to the case data model.

Running a Blue Prism process as part of a case type consists of the following stages:

  1. Your application sends a request to Blue Prism with the input that is required for running an automation.
  2. Your application matches the output values with specific case properties so that the case can progress.

Pega Platform handles the mapping of input and output properties through request and response data transforms that you can configure while defining stages and steps of a case type.

Before you begin:
In this scenario, you create request and response data transforms for a sample Blue Prism process to check the share price of a company. Based on the stock symbol that your application supplies to Blue Prism, the automation returns the current share price, currency, and the queue item ID to match the request and response. The following figure shows the Blue Prism process in Pega Platform:
Input and output configuration in a Blue Prism process
A sample Blue Prism process with input and output properties that you map to your case data model.
Important: All property names in the Blue Prism process data model are case-sensitive. Ensure that the property names match exactly in your Blue Prism implementation.
  1. In the navigation pane of Dev Studio, click Case types.
  2. Open the case type that you want to edit.
  3. On the Workflow tab, click the Assign to robot queue step.
    Blue Prism process integration in a case type
    Define the request and response data transforms while editing stages and steps in a case type.
  4. Creating a request data transform

  5. On the General tab of the step properties pane, next to the Request data transform field, click the Open icon.
  6. On the New tab, configure the data transform record.
    1. In the Label field, specify the data transform name.
    2. In the Additional configuration section, in the Data format field, select JSON.
    3. In the Context section, specify the applicable ruleset and the ruleset version for the data transform record.
    4. Click Create and open.
  7. On the Definition tab of the data transform record, map case properties to all Blue Prism input fields.
    For example: Create a step to map the value of case property that holds the company stock symbol to the corresponding input property in the Blue Prism process, as shown in the following figure:
    Request data transform for mapping Blue Prism input data
    The steps required to map case properties to Blue Prism input properties.
    For more information, see Data transforms.
  8. Save the data transform.
  9. Creating a response data transform

  10. On the General tab of the Assign to robot queue properties pane, next to the Response data transform field, click the Open icon.
  11. Repeat step 5 to add a data transform record.
  12. On the Definition tab of the data transform record, map case properties to output fields that Blue Prism returns after completing an automation.
    For example: Create steps to map the Blue Prism price and currency property values to the corresponding properties in your case data model, as shown in the following figure:
    Response data transform for mapping Blue Prism output data
    The steps required to map case properties to Blue Prism input properties.
    Note: Do not include the itemId property in the response data transform because Pega Platform handles this mapping automatically.
    For more information, see Data transforms.
  13. Save the data transform.
  14. Save the case type.
  • Previous topic Configuring the connection between Blue Prism and Pega Platform
  • Next topic Configuring a case type with Pega Open Robotics

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.

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

Close Deprecation Notice
Contact us