Pega Robot Manager 8.7.3

Released on November 25, 2022

This maintenance release of Robot Manager:

• resolves a number of issues. For more information, see Resolved Issues in 8.7.3

• introduces a queue processor that automatically performs updating activities when updating Pega Robot Manager from version 8.6.1 (or earlier) to version 8.7.3.

  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.7.2

Released on March 16, 2022

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

Pega Robot Manager 8.7.1

Released on January 28, 2022

See the following list for a summary of what changed:

• You can now manage work groups and assignment types and their associated settings directly in Pega Robot Manager:
  • You can now modify several work group settings from a single location in Robot Manager. In the new Edit work group dialog box, you can change the work group name, names of assignment types, and how the robots in this work group prioritize assignments, such as by Auto-balancing, by urgency, or by assignment type.

    For more information, see Modifying work groups.

  • You can now delete the work group in Robot Manager. When you delete a work group, the system deletes all assignment types that are associated with the work group. Additionally, you can delete a specific assignment type from a work group if it meets specific criteria.

    For more information, see Deleting work groups and assignment types.

    Caution: Deleting an assignment type that is referenced in a case type prevents the case from completing. When deleting work groups and assignment types, it is important to verify that case types in Dev Studio are not using the assignment type that you plan to delete.
  • When you create a work group, you also create at least one assignment type for the work group. During initial setup, you might not know all of the assignment types that you want to include in the work group. After initial setup, you can now continue to add assignment types for work groups directly in Robot Manager as needs change. A new Add assignment type link is available under the list of assignment types for each work group.

    For more information, see Creating assignment types.

  • You can modify assignment type settings from a new Edit option that is provided for each assignment type within a work group. By using this option, you can update the name of the assignment type, the maximum threshold for queued assignments, the length of time in which the automation is expected to complete, and the estimated monetary amount that will be saved by performing one automation all from one dialog box.

    For more information, see Modifying assignment types.

• This release includes the following improvements that make it easier to find and manage packages:
  • The Packages landing page now displays only the list of the packages that are associated with the Robot Manager application.
  • The Packages landing page now includes the version of Robot Runtime that is required for each assigned package in the work group, department, and user screens.
  • New filters and search capabilities across all views make it easier to find information, particularly if your organization has a large number of assignments.

    For more information, see Modifying package details.

• The Users and Departments pages include new filters and search capabilities. You can search by name or identifier. These pages also now include the required Robot Runtime version for each assigned package.
• In preparation for the security enhancements in Robot Runtime version 21.1, Robot Manager now supports signing packages, encrypting packages, or both.
  Note: For Robot Runtimeversion 19.1, the current capability for signing packages from Pega Robot Studio is still available.
• Robot Manager now tracks all the attended and unattended Pega Robotic Process Automation (RPA) licenses. You can access this information by using a custom report.

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 updating 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:

  

  

  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 name	Modification
  Data-Robot-Command	Added a BLOB column.
  Data-Robot-Schedule	Added a BLOB column.
  Data-Robot-Schedule-Action	Added a BLOB column.
  Data-Robotic-AutomationPackage-DeploymentLevel	Added a BLOB column.
  Data-RobotManager-Agent-Metadata	Added a BLOB column.
  Link-Robotic-RuntimeConfigAssignment	Added a BLOB column.
  Link-Robotic-PackageAssignment	Added a BLOB column.
  Data-Robot-Metrics-UnderPerformingBots	Added 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-Events	Added 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-Archive	The new pxPrimaryInsKey property 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 table and pr_history_data table, 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-Metadata	2. History-Data-Robot-Command	3. History-Data-Robot-Metadata
  4. History-Data-Robot-Metrics-ActivityStatus	5. History-Data-Robot-Metrics-ActivityStatus-Archive	6. History-Data-Robot-Metrics-UnderPerformingBots
  7. History-Data-Robot-Metrics-UnderPerformingBots-Archive	8. History-Data-Robot-Schedule	9. History-Data-Robot-Schedule-Action
  10. History-Data-Robot-WorkGroup-Metadata	11. History-Data-Robotic-AutomationPackage	12. History-Data-Robotic-AutomationPackage-Version
  13. History-Data-Robotic-AutomationPackage-Version-Config	14. History-Data-Robotic-NotificationAlert	15. History-Data-Robotic-OperationalStatistics-Exception
  16. History-Data-Robotic-OperationalStatistics-Exception-Archive	17. History-Data-Robotic-OperationalStatistics-Health	18. History-Data-Robotic-OperationalStatistics-Health-Archive
  19. History-Data-Robotic-OperationalStatistics-Usage-Hourly	20. History-Data-Robotic-OperationalStatistics-Usage-Hourly-Archive	21. History-Data-Robotic-OperationalStatistics-Usage-Daily
  22. History-Data-Robotic-OperationalStatistics-Usage-Daily-Archive	23. History-Data-Robotic-OperationalStatistics-Usage-Monthly	24. History-Data-Robotic-OperationalStatistics-Usage-Monthly-Archive
  25. History-Data-Robotic-OperationalStatistics-Usage-Yearly	26. History-Data-Robotic-OperationalStatistics-Usage-Yearly-Archive	27. 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.

  

  

• 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, see 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 confusing automations that did not complete (on the one hand) with automations that were completed with errors (on the other hand). For more information, see Viewing work assignments with unexpected errors.
• Adding new users is simplified because you now can configure a custom operator ID other than an email address. For more information, see:
  • Adding users manually
  • Importing users
• 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 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 Analytics.
• 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 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.