Attended robotic automations, formerly known as robotic desktop automations (RDA), run on client desktops and automate tasks and workflows. You can use attended automations as a source for a data page when the data page is requested from a browser on a Microsoft Windows client that is running Pega Robot Runtime.
A robotic automation robot can read data from a system or write data to a system, even if the system does not have an API. For example, you can use a robot to obtain a credit score from a legacy system, and then you can display that credit score on a Pega Customer Service™ application account overview dashboard and update a client's address on the system of record.
At run time, the browser requests the data page to be loaded. The data page notifies the client to run the requested attended automation, and then the browser notifies the robot to run the automation. The data that is returned from the robot is pushed back to the server. The server runs the response data transform, finalizing the data page, and the browser is notified to continue loading the user interface.
The run-time architecture depends on the version of Pega Robotic Automation as follows:
- In Pega Robotic Automation 19.1, the client makes requests directly by using the self-hosted REST service. The runtime architecture is shown in the following diagram.
- In Pega Robotic Automation 22.1 and above, the client makes requests by using the Messaging Service on Pega Platform. The runtime architecture is shown in the following diagram.
- Configuring a data page for sourcing from an attended robotic automation
After you configure your data type and your automation has been built, you can configure the data page to be sourced from an attended robotic automation, formerly known as a robotic desktop automation.