Configuring a data page for sourcing from robotic desktop automation
After you configure your data type and your automation has been built, you can configure the data page to be sourced from a robotic desktop automation.
The automation is invoked only when the data page is requested from a browser; that is, the data page must be the source for a control in the user interface. The automation is not invoked if it is referred to by an activity or other rule running on the server.
- In Dev Studio, from the Data types explorer, expand the data type that you created in the previous task, and click the data page that you want to source from a RDA.
- In the Source field, click Robotic desktop automation.
- In the Robotic automation name field, select the robotic automation that was imported from the Pega Robotic Automation Studio.
- In the Timeout(s) field, enter the length of time that the data page should wait for automation to complete before timing out.
- In the Request data transform field, enter the request data transform to use to provide input data to the robot.
- In the Response data transform field, enter the response data transform to use to convert the results returned from the robot to the logical model used by the data page.
- Optional:
To write data back to the application with which the robot is interacting,
configure a save plan by performing the following actions:
- In the Data page definition section, in the Mode field, select Savable.
- In the Data save options section, in the Save type field, select Robotic desktop automation.
- In the Robotic automation name field, select the name of the automation that writes the data back to the application.
- Click Save.
After the data page is configured, you can use it in your user interface. The most common way to do this is by using section include on a Section rule. You invoke the automation by selecting Use data page in the Page Context field and selecting data page. Select Defer load contents to allow extra time for the robot to fetch the data before rendering the user interface. For more information, see Harness and section forms - adding a section.
If you configure a save plan, configure the flow action that triggers the post processing that writes data back to the application. For more information, see Saving data in a data page as part of a flow action.