Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

What's new in Pega Robot Manager

Updated on December 20, 2022

Pega Robot Manager is constantly improving your user experience and the efficiency of your robotic workforce. This article provides a summary of new features and key improvements.

Download Pega Robot Manager from one of the following locations:

For more information on how to update your version of Pega Robot Manager, see Updating the Pega Robot Manager version.

For more information on enhancements and new features in Pega Robotic Automation, see What's new in Pega Robotic Automation.

Learn about the latest updates to the Pega Robot Manager application.

What's new (by release)

Pega Robot Manager 8.6.4

Released on December 20, 2022

Note: Pega Robot Manager 8.6.4 requires you to install Pega Platform 8.6.6, which includes an important security patch.

This maintenance release of Robot Manager:

  • resolves a number of issues. For more information, see Resolved Issues in 8.6.4
  • introduces a queue processor that automatically performs post-updating activities when updating Pega Robot Manager from:

    • earlier than version 8.6.1 to version 8.6.4
    • 8.6.2 to 8.6.4
    Note: The queue processor cannot automatically perform post-updating activities when updating from version 8.6.1 to 8.6.4, therefore you must perform the required activities manually.

    The updating activities relate to:

    • associating robotic assignments to SLAs
    • updating records to reflect changes in database schema
    • purging redundant history tables

    Note: After updating Pega Robot Manager, you must restart the server to execute the above updating tasks automatically. The restart is required in order to add the queue processor.
    For more information, see Completing post-update tasks

Pega Robot Manager 8.6.3

Released on March 31, 2022

This maintenance release of Robot Manager focuses on improving user experience by addressing minor issues. For more information, see Resolved Issues in 8.6.3.

Pega Robot Manager 8.6.2

Released on October 1, 2021

See the following list for a summary of what changed:

  • When upgrading to Robot Manager version 8.6.2, you can adjust your existing data access layer (such as database tables and classes) in just a few clicks to reflect the improvements in the latest release and prevent system issues. In addition, a new icon in the Robot Manager header informs of any recommended post-upgrade tasks:
    The new icon indicates post-update tasks to perform
    The new icon indicates post-update tasks to perform
    For more information, see Completing post-update tasks.
  • Robot Manager database is now more flexible because of the improved database schema.

    See the following table for a list of modified database tables and the corresponding modifications:

    Modified database tables

    Class nameModification
    Data-Robot-CommandAdded a BLOB column.
    Data-Robot-ScheduleAdded a BLOB column.
    Data-Robot-Schedule-ActionAdded a BLOB column.
    Data-Robotic-AutomationPackage-DeploymentLevelAdded a BLOB column.
    Data-RobotManager-Agent-MetadataAdded a BLOB column.
    Link-Robotic-RuntimeConfigAssignmentAdded a BLOB column.
    Link-Robotic-PackageAssignmentAdded a BLOB column.
    Data-Robot-Metrics-UnderPerformingBotsAdded a BLOB column.
    Data-Robot-Metrics-UnderPerformingBots-Archive
    • Added a BLOB column
    • The new pxPrimaryInsKey property holds the pzInsKey of the entry in main table. pzInsKey includes the archived class name.
    History-Data-Robot-EventsAdded a BLOB column.
    History-Data-Robot-Events-Archive
    • Added a BLOB column
    • The new pxPrimaryInsKey property holds the pzInsKey of the entry in main table. pzInsKey includes the archived class name.
    History-Data-Robot-Automations
    • Added a BLOB column.
    • The new pxRefObjectKey property holds the case ID.
    • The new pxProcessedDateTime property holds the case update time.
    History-Data-Robot-Automations-Archive
    • Added a BLOB column.
    • The new pxPrimaryInsKey property holds the pzInsKey of the entry in main table. The pzInsKey includes the archived class name
    • The new pxRefObjectKey property holds the case ID.
    • The new pxProcessedDateTime property holds the case update time.
    Data-Robot-Metrics-ActivityStatus-ArchiveThe new pxPrimaryInsKey property now holds the pzInsKey of the entry in main table. The pzInsKey includes the archived class name.
    Data-Robot-WorkGroup-Metadata
    • The new pyfailuresthresholdperrobot column replaced the pyfailedautomationsthresholdperrobot column.
    • Removed the pyfailedautomationsthresholdperrobot column.

    For more information on how to update your database schema, see Completing post-update tasks.

  • Robot Manager performance was improved by creating dedicated audit tables for Robot Manager History classes. The new tables reduce the query time by eliminating the need to rely on the Pega Platform pr_history and pr_history_data tables, simplify data migration, reduce maintenance costs, and facilitate understanding of the actual amount of data that Robot Manager stores.

    See the following table for the list of classes that now have dedicated audit tables:

    Classes with dedicated audit tables in Pega Robot Manager

    1. History-Data-Robot-AssignmentType-Metadata2. History-Data-Robot-Command3. History-Data-Robot-Metadata
    4. History-Data-Robot-Metrics-ActivityStatus5. History-Data-Robot-Metrics-ActivityStatus-Archive6. History-Data-Robot-Metrics-UnderPerformingBots
    7. History-Data-Robot-Metrics-UnderPerformingBots-Archive8. History-Data-Robot-Schedule9. History-Data-Robot-Schedule-Action
    10. History-Data-Robot-WorkGroup-Metadata11. History-Data-Robotic-AutomationPackage12. History-Data-Robotic-AutomationPackage-Version
    13. History-Data-Robotic-AutomationPackage-Version-Config14. History-Data-Robotic-NotificationAlert15. History-Data-Robotic-OperationalStatistics-Exception
    16. History-Data-Robotic-OperationalStatistics-Exception-Archive17. History-Data-Robotic-OperationalStatistics-Health18. History-Data-Robotic-OperationalStatistics-Health-Archive
    19. History-Data-Robotic-OperationalStatistics-Usage-Hourly20. History-Data-Robotic-OperationalStatistics-Usage-Hourly-Archive21. History-Data-Robotic-OperationalStatistics-Usage-Daily
    22. History-Data-Robotic-OperationalStatistics-Usage-Daily-Archive23. History-Data-Robotic-OperationalStatistics-Usage-Monthly 24. History-Data-Robotic-OperationalStatistics-Usage-Monthly-Archive
    25. History-Data-Robotic-OperationalStatistics-Usage-Yearly26. History-Data-Robotic-OperationalStatistics-Usage-Yearly-Archive27. History-Data-RobotManager-Agent-Metadata
    28. History-Data-Robotic-AutomationPackage-DeploymentInfo

    For more information on how to purge redundant tables after the data was moved to dedicated Robot Manager history tables, see Completing post-update tasks.

Pega Robot Manager 8.6.1

Released on May 14, 2021

See the following list for a summary of what changed:

  • The new interface for Pega Robot Manager moves menu items to a left-side navigation bar, improving navigation, accessibility, and user experience. The new theme, provides a more intuitive and engaging environment for the management of your robotic workforce.
    Improved navigation in the Pega Robot Manager portal
    Improved navigation in the Pega Robot Manager portal.
  • The Robot Manager user interface now has breadcrumbs that increase the user awareness about where they are in the application, facilitate exploration, and provide a quick way to return to the previously visited pages. For example, breadcrumbs can prove useful when managing users, robots, or reviewing various settings in each work queue.
  • Pega Deployment Manager facilitates migrating Robot Manager applications and the package repository contents between environments. This solution removes the need to manually download and upload package components or generate multiple copies of the same package. For more information, see Migrating Pega Robot Manager applications by using DevOps.
  • Robot Manager users can provide comments, share content, or exchange ideas by using Spaces. By providing an entry point for sharing and developing ideas, Spaces facilitates collaboration and increases productivity. For more information, Collaborating with Pega Robot Manager users.
  • Automations that completed but encountered an error with outcome processing on the Robot Manager side are now classified as unexpected errors on the Issues tab. This reduces the likelihood of mingling of automations that did not complete with automations that were completed with errors. For more information, see Viewing unexpected errors for work assignments.
  • Adding new users is simplified because you now can configure a custom operator ID other than an email address. For more information, see:
  • Robot Manager was improved to prevent unnecessary alerts of the following types:
    • PEGA0053 alert - Caused by the D_pzCaseAssignmentsPastSLA being reloaded frequently.
    • PEGA0053 alert - Caused by the D_pxFetchEntityHierarchy data page being reloaded frequently.
    • SECU0019 alert - Caused by the following exception: Unauthorized request detected : Unregistered request encountered with params pyActivity:pzRunActionWrapper pySubAction:runAct pzActivity:pzMapChannelDataToClipboard eventSrcSection:Data-Admin-Operator-ID.pyRoboticOperatorContent

Pega Robot Manager 8.5.3

Released on July 28, 2021

This maintenance release of Robot Manager focuses on improving user experience by addressing minor issues. For more information, see Resolved Issues in 8.5.3.

Pega Robot Manager 8.5.2

Released on January 27, 2021

See the following list for a summary of what has changed:

  • Auto-balancing uses work group priorities to determine how the system assigns robots when there are not enough robots available to complete all assignments across work groups on time. For more information, see Auto-balancing robot workload across work groups.
  • The new Auto-balancing tab under the Settings menu provides a management center for Auto-balancing and SLA priority for all work groups in the current application. For more information, see Designating work groups for auto-balancing of robot workload.
  • The analytical dashboards now include the Performance and Performance timeline widgets, which provide both daily and hourly analysis of robot performance across work groups. For more information, see Analysis dashboards.
  • Auto-archiving and auto-purging of old or obsolete Pega Robot Runtime operational data now helps maintain the optimal performance of your robotic solution. For more information, see Cleaning up Pega Robot Runtime operational data. In work groups enabled for Auto-balancing, Robot Manager now automatically stops robots when no further work is available in a work group. Such robots can then move to higher priority groups to ensure that critical tasks are completed on time.

Pega Robot Manager 8.5.1

Released on October 6, 2020

See the following list for a summary of what has changed:

  • A new feature called Auto-balancing simplifies robot administration because you no longer need to manually move robots between work groups during peak periods or create schedules. For more information, see Auto-balancing robot workload across work groups.
  • Robot Manager now detects and stops underperforming robots, which reduces the number of failed assignments and decreases the maintenance effort needed from human operators to clear such assignments. For more information, see Handling underperforming robots.
  • Robot Manager can now control the repository of automation packages. You can now fully comply with your policy for data storage by having an option to store automation packages remotely. For more information, see Storing robotic automation packages in Pega Robot Manager.
  • Downloadable Robot activity logs provide insight into the root cause of processing failures. For more information, see Downloading robot activity logs.
  • New alerts to notify you about robots that consecutively fail their assignments (ROBO0010) or robots that cannot recover from the Not ready state (ROBO0011). For more information, see Performance and security alerts for Pega Robot Manager.
  • The list of available robot status types now includes the Started status type. For more information, see Robot status types.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us