Pega Robot Manager 6.2
Use Pega Robot Manager™ to monitor the performance, health, and throughput of your robotic process automation (RPA) robots.
You can do the following tasks:
- Manage robots – start, stop, schedule, and move between work groups
- Manage assignments – start, stop, and set key thresholds that allow for end-user notifications
- Configure the organizational hierarchy of departments and users
- Apply roles to users to define the tasks that they can perform
- Update automation packages and deploy them to robotic work groups, departments, and users
- Securely manage the package life cycle from development, testing, and up to the production stage
- Configure email notification in the case of unexpected issues with robots or scheduling
For more information about configuring and using RPA with Pega Platform™, see Configuring robotic process automation.
Pega Robot Manager versions 6.1 and 6.2 are maintenance releases. They are functionally equivalent to Pega Robot Manager 6.0, with the added support for Pega Platform 8.1 and bug fixes summarized here and here.
Pega Robot Manager 6, 6.1, and 6.2 for Pega Platform 7.4
Pega Robot Manager 6.0, 6.1, and 6.2 are supported on Pega Platform 7.4. To download Pega Robot Manager from Pega Marketplace, go to the Pega Robot Manager page.
You must also use Pega Robotic Automation 8.0 SP1 2019 at a minimum. For best results, use the latest version available (8.0 SP1 2025 or later).
For information about Pega Robot Manager, see the following articles:
- Upgrading to Pega Robot Manager 6 for Pega Plaform 7.4
- Configuring Pega Robot Manager 6 for Pega Plaform 7.4
- Configuring authentication for Pega Robot Manager 6 for Pega Plaform 7.4
- Using Pega Robot Manager 6 for Pega Plaform 7.4
Pega Robot Manager 6.1 and 6.2 for Pega Platform 8.1
Pega Robot Manager versions 6.1 and 6.2 are supported on Pega Platform 8.1. To download Pega Robot Manager from Pega Marketplace, go to the Pega Robot Manager page.
You must also use Pega Robotic Automation 8.0 SP1 2023 at a minimum. For best results, use the latest version available (8.0 SP1 2025 or later).
For information about Pega Robot Manager, see the following articles:
- Upgrading to Pega Robot Manager 6 for Pega Plaform 8.1
- Configuring Pega Robot Manager 6 for Pega Plaform 8.1
- Configuring authentication for Pega Robot Manager 6 for Pega Plaform 8.1
- Using Pega Robot Manager 6 for Pega Plaform 8.1
Enhancements in Pega Robot Manager 6
Pega Robot Manager 6 includes the following enhancements
- Redesigned work groups interface – each work group has a separate page containing a list of associated robots, assignments, packages and performance metrics.
- New assignment prioritization method: By urgency.
- New performance metric: Savings.
- New robot state – "Standby". Robot is ready to accept commands or a schedule.
- Ability to manually start, stop, and terminate robots that are running with the RPA Service. Termination is possible if there is an error while stopping the robot.
- Ability to move robots between work groups.
- Ability to create schedules for robots that are running with an RPA Service.
- Ability to perform bulk actions on multiple robots (start, stop, move) on the redesigned list of all robots.
- Configurable email notification in the case of unexpected issues with robots or scheduling, including scheduling service down, robot loses connectivity, assignment past SLA deadline, and so on.
- Ability to simulate metrics on the dashboard.
Updates and improvements in Pega Robot Manager 6.2
| Item ID | Description |
|---|---|
| SR-D32599 | Resolved an issue with assigning packages to a user when the Pega Web Accessibility (Pega-WAI) ruleset is in the stack. |
| SR-D25616 | Eliminated a limit on the maximum number of work groups that are listed on the Robot Manager work group tile screen. |
| SR-D21763 | Improved error log formatting for scenarios where robot registration failed. |
| SR-D23962 | To improve performance, Pega Robot Manager no longer adds history records for schedules and scheduling actions to the database. |
| BUG-509839 | Resolved an issue where archive and purge utilities of events and automations table could fail when configured using an agent. |
| BUG-512058 | Resolved an issue where actions that are scheduled to run on the last week day of the month (for example, the last Tuesday of August) might not be executed by the scheduling agent. |
| BUG-513134 | When adding a second-level department, all child departments of the parent department now move under the new second-level department. |
Updates and improvements in Pega Robot Manager 6.1
| Item ID | Description |
|---|---|
| EPIC-36530, US-250166,US-266340, US-265090, US-264911, US-265090, US- 266842 | UI related updates:
|
| US- 266842 | Removed the ability to include a comma in the name of a work group or assignment type. Also required at least one assignment type when creating a work group through the UI. |
| US- 266842 | Resolved an inconsistency with the MSSQL Server database that could occur when adding an assignment type to a work group. |
| Start/Stop actions are now allowed for robots that were once standalone but are now controlled by an RPA Service. | |
| Added a Work group to START command issued to the RPA Service enabling a Robot Runtime capability allowing for robot to select Windows session credentials based on work group assignment. Requires Robot Runtime version of 8.0 SP1 2032 or 19.1.2 or later. | |
| US-267713, US-268641 | Improved the logging of deferred scheduled actions in the Audit table. |
| US-266289 | Resolved inconsistencies related to scheduling in regards to Daylight Savings Time and other time zone and scheduling issues. |
| US-267943 | System info now displays the version of the Robot Manager, along with the platform version |
Improved security with revised access roles defined for Robot Manager and updated Bankerpro sample application’s access groups to include minimum required roles. Access roles shipped with Robot Manager have been re-structured to allow Administrative (also called Registration) Operator to register RPA robots and RPA Service operators, without requiring access to PegaRULES:SysADM4. | |
| BUG-422740, BUG-422743 | Resolved bug around receiving notifications when the RPA Service is down during a scheduled action. |
Previous topic Using Pega Robot Manager 8.2 Next topic Upgrading to Pega Robot Manager 6 for Pega Platform 7.4