Public automations created in Pega® Robotic Automation Studio can be easily invoked from within Pega Platform 8.2 (or later) applications. Use Dev Studio to create the Pega Platform application that invokes the automation, and then map the input and output parameters to Pega class fields. With public automations, you do not need to know class names when you develop automations using Pega Robotic Automation Studio.
- Pega Robotic Automation 8.0 SP1 2029 or later
- Pega Platform 8.2 or later
- Pega Robot Manager 8.2 or later
- A compatible repository, such as Jfrog, S3, or Artifactory, for storing the published automation packages.
Before you begin
To use public automations, you must enable the PegaDevServer server type in the CommonConfig.xml file for Pega Robotic Automation Studio. Enabling the PegaDevServer server type sends package metadata to the PegaDevServer server instead of the RobotManager server. The CommonConfig.xml file is located in the C:\ProgramData\OpenSpan folder.
<Server name="PegaDevServer" baseURL="https://DevPegaInstance.com/prweb" enabled=true" proxyAddress="" />.
Use public automations to pass and return inputs and outputs. Creating a public automation generally follows the same process as any other automation, with a few exceptions. For more information, see the following illustration, which details the process of creating the automation and publishing it to the Pega Platform:
When creating public automations in Robotic Automation Studio, keep in mind the following best practices:
- The name that you assign to public automations cannot include spaces.
- Public automations can only have one entry point and one exit point.
- You cannot move public automations outside of their folder.
- You can invoke public automations by using Robotic Desktop Automation (RDA) mechanisms from the Pega Platform.
- If, in a project, a RobotActivity and a public automation have the same name, the public automation takes priority when invoked through RDA.