Pega Robot Manager allows you to manage your RPA robots by starting, stopping, scheduling, and terminating them. You can configure Pega Robot Manager to fully meet the needs of your organization. You can also create and view reports on robot health, exceptions, and usage data.

• Storing robotic automation packages in Pega Robot Manager

  Make your robotic solution fully compatible with your data storage policy by configuring Pega Robot Manager to use a repository for package binary files.

• Migrating Pega Robot Manager applications by using DevOps

  Simplify the process of migrating Pega Robot Manager applications (including their associated automation package files and metadata) between environments by using Deployment Manager. In this way, you avoid manually downloading and uploading package components, and avoid generating multiple copies of the same package.

• Robot registration and work group assignment for RPA (unattended) robots

  Before an unattended robot can run any automations, that robot must successfully register with Pega Robot Manager.

• RPA Service-assisted robots and stand-alone robots

  Pega Robot Manager supports both RPA Service-assisted robots and stand-alone robots.

• Stand-alone robot registration

  A stand-alone robot registers with Pega Robot Manager by using the applicable administrative credentials. This type of robot cannot be started or scheduled from the Pega Robot Manager interface.

• Configuring how robots are assigned to work groups (initial robot registration only)

  A robot can request to join a specific work group. If a specific work group is not specified by the robot, Pega Robot Manager attempts to find the work group that the robot should join based on pyGetWorkGroupByRobotID and pyGetWorkGroupForRobotByRequestorOperatorID decision tables.

• Defining work groups that a robot can move to

  To move robots between work groups, either manually or by using a schedule, you must define a list of eligible candidate work groups for each administrative operator (registration operator) that registered the robots. All robots that were registered by the same administrative operator can move to those work groups.

• Enabling scheduling of robots

  The ProcessRobotScheduleActions agent checks whether a schedule is defined for a given robot, and runs the defined schedule.

• Enabling monitoring of robot and RPA Service health

  The MonitorRobotCommandAndHeartbeat agent checks the status of robots and the status of the RPA Service. This checks whether the RPA Service and robot are sending a heartbeat signal regularly, and then checks whether the robot responds appropriately when it receives commands such as start or stop.

• Enabling automatic cleanup of disconnected robots

  The ProcessStaleRobots agent finds running robots that have lost their connection to Pega Robot Manager, and stops them. Robots that have lost connectivity (are no longer heartbeating) appear with a red error state (Needs attention).

• Enabling automatic cleanup of stale automation assignments

  The RoboticAssignmentProcessing agent finds stale automation assignments that have been in a robot's personal work queue for longer than expected, and then moves them to the list of automations that have timed out. You can view automations that have timed out in Time-outs on the Issues page.

• Default dynamic system settings for Pega Robot Manager

  While Pega Robot Manager is running, you can change the dynamic system settings data instances that are related to robotic operations in your application to answer your specific business needs.

• Associating access groups and roles

  Access roles and access groups determine the permissions of each user in your application. When you add a user in Pega Robot Manager, you associate a given access role to a given access group in order to apply the role permissions to the user.

• Configuring notification thresholds

  Pega Robot Manager can notify users of unexpected behavior or errors by webgadget and email.

• pyCompleteAutomation flow action

  In Pega Robot Manager, pyCompleteAutomation is marked as an Extension. Its default behavior is to treat the automation status as Complete, and to move the flow to the next stage of the case life cycle.

• Job schedulers (agents) that clean up history records

  Pega Robot Manager adds new job schedulers (agents) to clean up an excessive number of history records.

• Configuring automatic cleanup of robotic automations, events, or operator history records

  Depending on your business needs, you can configure Pega Robot Manager to automatically clean up automations, events, or operator history records.

• Localization considerations

  When localizing applications that use Pega Robot Manager, ensure that you adhere to the following guidelines.

• Installing Pega Robot Manager
• Using Pega Robot Manager
• Reporting in Pega Robot Manager