New Robot Manager applications

Pega Robot Manager™ is available as an application type when you use the New Application wizard in Pega Platform™. Creating a new Pega Robot Manager application provides developers with the option to configure the necessary components for attended and unattended robotic process automation (RPA) applications. The application wizard includes the following configuration options:

For unattended RPA, the New Application wizard can add the configuration options during the application creation. The work groups and assignment types can also be added after the creation of the application through the Pega Robot Manager user interface. You can modify the decision tables after the creation of the application when new work groups and assignment types are created.

Work groups and assignment types enable unattended robots to access cases from their respective work areas. For unattended RPA robots, work groups are defined in several places and follow a process dependent on configuration files and decision tables. You can edit decision tables after adding a new work group and assignment type through Pega Robot Manager for proper provisioning or moving robots to another work group.

During the installation process, the New Application wizard allows you to add operators to access Pega Robot Manager. After the application is installed, you can also add new operator roles through the Pega Robot Manger user interface. These roles consist of the following types:

• Administrator – Administrators can perform all actions in Pega Robot Manager. Only these users can deploy packages to the Production deployment level.
• Developer –  Developers can publish and manage automation packages.
• User Administrator – User Administrators can manage run-time users and the organizational hierarchy.
• Run-time user – Run-time users cannot log in to Pega Robot Manager. Run-time users are typically caseworkers who merely fetch an automation package assignment from Pega Robot Manager

Applications that are designed to use unattended RPA must create a Robot Registration Operator ID. A single Robot Registration Operator ID can be used for multiple unattended RPA robots. A Robot Registration Operator ID determines what work groups the robot has access to through the use of the candidate work group decision table. The robot should have access to all applications and credentials required to work in any work group on the candidate work group list.

Use the advanced configuration options in the New Application wizard to set the application's org/div/unit structure. Once the application is created, the administrator can add any built-on application and ruleset to extend the functionality. Although the New Application wizard creates a new application, you can adjust the application's configurable items by using Dev Studio once the application is created.