Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Using a robotic automation to populate a data page

Updated on April 5, 2022

Robotic process automations (RPAs) are automations that run in the back office. For example, you can use an RPA to obtain a credit score from a legacy system that you can then display on a Pega Customer Service application account overview dashboard.

  1. In App Studio or Dev Studio, build a simple case type to model the overall robotic automation. Include the input fields that you want to pass to the RPA robot in the case data model, for example, customer ID, mailing address, or account number. In addition, include the output data fields that you want the robot to pass back to your Pega application, for example, credit score, account balance, or claim number.

  2. In App Studio or Dev Studio, build a simple case life cycle. The case life cycle must include the Route to robot smart shape. The smart shape queues the automation request to the RPA robot. This is the case that will be referenced on the data page.

  3. In Pega Robotic Automation Studio, build the automation logic for the robot to execute. Once your automation is completed, reference the robot activity name in the Queue for robot smart shape.

  4. Configure the location of the Robot Manager host server and the authentication profile to use when connecting to it.

  5. Configure the data page.

  • Previous topic Robotic automation as a data page source
  • Next topic Configuring the Robot Manager host server and authentication profile

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