Resolved issues in Pega Robot Manager
Learn about resolved issues in the Pega Robot Manager
application. Pega Robot Manager continuously improves the user experience and
optimizes application performance, including resolving issues, as described
below. Resolved Issues BUG-760841 BUG-760833 BUG-734580 BUG-761409 BUG-760830 BUG-761413 BUG-760835 BUG-760832 BUG-761407 When starting or stopping an assignment type, stamping the assignment
type on every robot in that work group sometimes fails, which means that
robots that are not stamped with the assignment type do not process
automations as required. When starting or stopping an assignment type, all the required robots are
now updated correctly. BUG-759197 BUG-760831 BUG-761414 BUG-761677 BUG-764983 BUG-765043 BUG-768080 Pega Robot Manager continuously improves the user experience and
optimizes application performance, including resolving issues, as described
below. BUG-706125 BUG-706191 BUG-706207 BUG-710079 BUG-710359 deleting the deployed version of the package (for all
non-inherited packages) On a Package drill-in page, no error message is
displayed when either adding a deployment version to a package or
when deleting the deployed version of the package. BUG-710361 On a Package drill-in page, a new deployment
level is displayed correctly between the UAT
level and the Production level. BUG-711475 When publishing metadata from Automation
Importer to Pega Robot Manager, the
Data-Robotic-AutomationPackage record and
the Data-Robotic-AutomationPackage-Version
record are updated with the name of the appropriate application
Ruleset in Pega Robot Manager. BUG-711644 In Deployment Manager: on the DevOps landing page, the
Last completed deployment
date-time information is not displayed in accordance with
the operator’s time zone. In Deployment Manager: on the Pipeline drill-in page, the
Last updated date-time
information is displayed in accordance with the
operator’s time zone. BUG-711689 When a work queue is deleted in Dev Studio, the
work queue priority of the remaining work queues is updated to
correctly reflect the new order of work queues. Pega Robot Manager continuously improves the user experience and
optimizes application performance, including resolving issues, as described
below. BUG-657076 BUG-655573 BUG-650196 BUG-671394 Widgets on the Dashboard and specific pages might display the wrong
DateTime value for time-outs because they use
the pxSaveDateTime property. The
DateTime value changes every time the case is
updated rather than maintaining the DateTime
value of the automation time-out. For example, if an assignment times out, after a certain period of
time, the assignment exceeds its SLA. If an SLA agent updates the
case, the DateTime value shows the date and time
of the update instead of the date and time of when the automation
timed out. This incorrect value displays on the Dashboard under
Automation issues, and on the
Issues page (under Time-outs) in the
Time of occurrence column. Pega Robot Manager continuously improves the user experience and
optimizes application performance, including resolving issues, as described
below. The validation message was changed to: Operator <operator_ID> has no work group specified
in the work group and requestor mapping
table.Resolved Issues in 8.6.4
Pega Robot Manager, 8.6.4
Issue ID (internal tracking only) Description Solution When deploying multiple packages with multiple versions from a source
instance to a target instance, records relating to package security keys and
etags are not created in the target environment All appropriate records are now created in the target
environment When calling the import packages REST service for
SSO, the response is mapped incorrectly. When calling the import packages REST service for
SSO, the response is now mapped correctly. If a user configures Pega Robot Manager to use a
ruleset that is in the form of Major-Minor-Patch, then the user is not able
to enable and disable Auto-balancing. It is now possible to enable and disabling Auto-balancing when the
configured ruleset is in the form of Major-Minor-Patch. The Upgrade tasks option is not visible when
upgrading from Pega Robot Manager 8.2. The Upgrade tasks option is now visible when
upgrading from Pega Robot Manager 8.2. When deleting from the system any business units to which other
business units report, a null pointer exception is sent to the logs when
navigating to the Packages landing page. The exception is handled appropriately. When there is a communications issue between Pega Robot Manager and RPA service in an
unattended solution, which results in a
NotifyRPAServiceisDown notification, a
blank operator is created, which is incorrect. Following a NotifyRPAServiceisDown
notification, no blank operator is now created. When deploying automation packages from source environment to target
environment, even when an error occurs, the task status for Deploy
robotic packages Is set to
In-progress instead of to
Open-Error. When a Deploy robotic packages task is running,
but there is an error, then the task status is now set to:
Open-Error. When an operator record is deleted from Pega Robot Manager or Dev Studio, the
value of Assignment users is not calculated
correctly. In Pega Robot Manager, it is not possible to assign a
Runtime Configuration to Org/Div/Unit unless
Org/Div/Unit is associated to a ruleset that is directly declared in the
current application. It is now possible to assign a Runtime
Configuration to Org/Div/Unit when the Org/Div/Unit is
associated to a ruleset that is inherited. When the same package is viewed in two sessions, if the package is
deleted in session 1 and then the screen is refreshed in session 2, then
this incorrectly triggers the 'Package ID is invalid' error message on the
screen in session 2. When the same package is viewed in two sessions, if the package is
deleted in session 1 and the screen is refreshed in session2, then this
triggers a message on the screen in session 2 that the package was deleted
in a different session. When carrying out a Zero Downtime Upgrade (ZDU), the work group
metadata is not transferred correctly. When carrying out a Zero Downtime Upgrade (ZDU), the work group
metadata is now transferred correctly. After clicking on in Pega Robot Manager's left navigation pane, the title of the
landing page is truncated and aligned incorrectly. This means that you
cannot create or update reports. The landing page header is now displayed correctly, and therefore you
can create and update reports. When a package version was deployed to a deployment level, if the
deployment level is re-ordered, a record is incorrectly added to the history
of the deployment level. After re-ordering a deployment level, the records in the history of the
deployment level are now correct. When exporting a monthly or yearly operational statistics report that
includes the Collection interval column, the
Collection Interval values are missing. (1) For reports that are created with Pega Robot Manager 8.6.4, an exported monthly and yearly
operational statistics report now contains all required data. (2) Even after updating to
Pega Robot Manager 8.6.4, this issue still exists for
reports that were created before updating to Pega Robot Manager 8.6.4. On a package details page, it is not possible to re-order deployment
levels for the package because a security alert is raised. After updating to Pega Platform 8.6.6, which contains an important
security update, you can now re-order deployment levels on a package details
page. Resolved Issues in 8.6.3
Issue ID (internal tracking only) Description Solution A call to the Runtime configs endpoint fails for
both attended and unattended cases. A call to the Runtime configs endpoint succeeds
for both attended and unattended cases. The number of attempts for the START command
to complete under a schedule is not correct. Instead, the value for
attempts is being incremented, but without checking if the command is in
progress, has completed, or has timed out. The number of attempts for the START command
to complete under a schedule is calculated correctly. Although a work queue was deleted in Dev Studio,
it is still possible to stop or start that work queue. This is not
correct because the work queue no longer exists. An error message is shown when attempting to start or stop a work
queue which was deleted in Dev Studio. When a case that is corrupt is moved to the work queue that contains
timed-out automations, an exception is raised. In addition, it is not
possible to view the details of the corrupt case. When a case that is corrupt is moved to the work queue that contains
timed-out automations, the system handles the raised exception. In
addition, it is possible to view the assignment details of the corrupt
case in the logs. On a Package
drill-in page, the
pxUpdateRecord:failed error message
is displayed when: On a Package
drill-in page, a new customized deployment level is not being displayed
in the correct location (between the UAT level
and the Production level), but is incorrectly
displayed after the last level, the Production
level). When publishing metadata from Automation
Importer to Pega Robot Manager, the
Data-Robotic-AutomationPackage and the
Data-Robotic-AutomationPackage-Version records
are not updated with the name of the appropriate application Ruleset in
Pega Robot Manager. When a work queue is deleted in Dev Studio, the
priority of the remaining work queues in the same work group is not
updated to correctly reflect the new order of work queues. Resolved Issues in 8.6.2
Resolved Issues in 8.6.2
Issue ID (internal tracking only) Description Solution BUG-671539 When you upgrade from Robot Manager 8.6.1, a database error can occur
during the package import due to a column name exceeding 30 characters. An upgrade utility copies data to a new column to ensure that the
package import completes without errors. BUG-669475 When a robot posts an assignment for the first time after the alert
evaluation interval, the system uses the default consecutive threshold
value of 5 instead of the value in the work group
metadata.The system now accesses the work group metadata when comparing
consecutive threshold values. BUG-660185 Selecting a user from a drop-down list on the Runtime
Config assignment flow is inefficient when the list is
long, and this is not possible if the list exceeds 10,000 users. Lists that exceed 10,000 users do not affect the Runtime
Config assignment flow. Rather than scrolling through a
drop-down list, you can use the auto-complete feature to filter the list
of users. The field lists matching results after you enter three or more
characters. The user list cannot exceed 10,000 records, which causes issues with
package assignment. Lists that exceed 10,000 users do not affect the package assignment
flow. BUG-626059 Cloud: Cannot download the log file from the
Issues landing page when the content storage
differs from the Pega database. You can now download automation issue log files when your content
storage differs from the default Pega database. BUG-670641 In Settings, when completing a manual archive or
a purge on the Reports page, the page does not show
the progress and completion banners for these actions. The Reports page now displays the progress and
completion banners for manual archive and purge actions. BUG-602485 The system receives a code status of 200
if a robot posts the same assignment result twice. If a robot posts the same assignment result twice, for example, due
to an issue with runtime configuration, the assignment status now
displays the status: 404 - Resource not
found. BUG-672455 Work group and work queue names that include the following characters
result in errors in the Robot Manager portal and in Dev Studio:
+, !,
=, [, and
] When saving a work group or work queue, the system now checks for the
+, !,
=, [, and
] characters, and includes these characters
in the error message. BUG-672099 The work group name cannot include a $
character, but $ is not in the error message that
lists the characters that are not allowed. The error message that lists the characters that are not allowed in
work group names now includes the $
character. BUG-668448 After a user deletes data on a page, such as the
Reports page (in Settings
), the message to inform users in other sessions of the page
that they have to refresh the page for the latest data does not show the
name of the user that deleted the data. The message that informs users to refresh to get the latest data now
lists the name of the user who deleted data in a different
session. BUG-661218 The system migrates binaries and metadata to the deployment
repository for packages that are not in the deployment information
table. Error handling logic now displays an error message, and prevents the
migration of binaries and metadata, for packages that do not have
records in the deployment information table. BUG-661221 If a metadata file is missing from the development environment, an
error message does not warn of this issue when publishing from
development to the production environment. If a metadata file is missing from the development repository, an
error message indicates that the metadata is not present when users
attempt to publish to the production environment. BUG-664745 Navigating to a drill-in page for any package from the
Packages page results in an access control
warning message. The system does not display an access warning message when you
navigate to drill-in pages from the Packages page.
BUG-646626 On the Assignment types drill-in page, if you
click Activity, and then click a page link at the
bottom of the results, the system displays an error message because live
updates are still occurring. When you launch a new page of activity results, the system now blocks
live updates to the list, and does not display an error message. BUG-649557 After an upgrade, work groups display incorrect KPI values for
assignment types and robots. The KPI values are incorrect because the
system correctly archives the automation history before the upgrade, but
then omits archived automations from the KPI calculation after the
upgrade. The work group KPI calculation now includes archived
automations. The DateTime value now reflects the correct
DateTime value for when an automation timed out,
where appropriate. BUG-650530 The system allows the user to add two work groups that have the same
assignment type name in the new application wizard. The system now prevents users from adding work groups that do not
have unique assignment type names. BUG-651247 The screen does not display messages for 401, or 403, errors if these
issues cause the Robot Manager deployment to fail. The screen now shows these error messages if the Robot Manager
deployment fails due to any 401, or 403, errors. BUG-652223 If you edit the name of a unit in the hierarchy, an error occurs when
you try to add a user to the unit. The refresh setting ensures that the system saves edits to unit names
in the hierarchy, and selects the new name in the Create new
user dialog box. BUG-653031 While checking whether Auto-balancing moves a robot, Robot Manager
does not consider the state of the robot. Added a new check that identifies if robots are in a running state,
stopped state, or standby state, to ensure that robots moved to work
groups for Auto-balancing later return to their scheduled work group
when appropriate. BUG-657370 PDC: The pyGetNotificationsForOperator query
causes the PEGA0005 alert. Improved the report definition to accelerate query
completion. BUG-657408 PDC: The pzGetCommandAndSvcOpDetailsForAllRobot
activity causes the PEGA0005 alert. Improved the report definition to accelerate query
completion. BUG-657409 PDC: The pzGetRuntimeConfigAssignmentsForOrg
activity causes the PEGA0005 alert. Improved the report definition to accelerate query completion.
BUG-657369 PDC: The pzUpdateRobotHeartbeatWrapper activity
causes the PEGA0005 alert. Improved the report definition to accelerate query
completion. BUG-657368 PDC: The pzValidateRoboticOperatorAvailability
activity causes the PEGA0005 alert. Improved performance by retrieving details from the report definition
to reduce the number of database queries. BUG-653107 PDC: The pyGetNotificationsForOperator query to
get notifications takes too long to complete, causing the
PEGA0005 alert. Improved the report definition to accelerate query
completion. BUG-649686 PDC: Prolonged database queries by the Auto-balancing engine cause
the PEGA0005 alert. Improved the report definition to accelerate query
completion. BUG-655001 PDC: The D_pzCaseAssignmentsPastSLAByApplication
activity causes the PEGA0053 alert. Improved the report definition to accelerate query completion.
BUG-653400 PDC: The CommandStatus REST service causes the
PEGA0011 alert. Removed redundant steps to decrease the duration of the REST
call. BUG-649806 PDC: The Heartbeat REST call causes the
PEGA0011 alert. Removed redundant steps to decrease the duration of the REST
call. BUG-653405 PDC: The Packages REST service causes the
PEGA0011 alert. Removed redundant steps to decrease the duration of the REST
call. BUG-661164 PDC: The Packages_Assignment REST service causes
the PEGA0011 alert. Updated the strategy for loading page data to decrease the duration
of the call. BUG-653404 PDC: The Profile REST service causes the
PEGA0011 alert. The report definition now allows the null value for filters that
might not have a value and checks for case. BUG-653401 PDC: The Register REST service causes the
PEGA0011 alert. Removed redundant steps to decrease the duration of the REST
call. BUG-653402 PDC: The RM_Details REST service causes the
PEGA0011 alert. Removed redundant steps to decrease the duration of the REST
call. BUG-653399 PDC: The RPA_Svc_Heartbeat REST service causes the
PEGA0011 alert. Removed redundant steps to decrease the duration of the REST
call. BUG-653407 PDC: The RuntimeConfig REST service causes the
PEGA0011 alert. Removed redundant steps to decrease the duration of the REST
call. BUG-658353 PDC: The
pzGetOperatorsBelongToCurrentApplication
activity causes the PEGA0053 alert. Updated the data loading strategy to load data pages only if a user
enters three or more characters. BUG-649905 PDC: The pzSetWorkGroupAdditionalDetails
activity causes the PEGA0005 alert. Improved the activity performance. BUG-658441 PDC: The
D_pzGetOperatorsBelongToCurrentApplication
activity causes the PEGA0053 alert. Updated the refresh strategy of the data page to reload data more
efficiently. BUG-577319 PDC: Frequent reloading of the
D_pxFetchEntityHierarchy data page causes the
PEGA0053 alert. Updated the reload strategy of
D_pxFetchEntityHierarchy to reload data less
frequently. BUG-653558 PDC:The D_pzGetRuntimeConfigByEntity activity
causes the PEGA0053 alert. Updated the refresh strategy for the data page to reload by time
interval instead of by each interaction. Updated the activity to clear
the data page when appropriate, such as when an assignment is removed in
Robot Manager. BUG-653473 PDC: The pzGetRepositionPrivilegeValue activity
causes the SECU0019 alert. Moved the activity registration to a different section. Resolved Issues in 8.5.3
Resolved Issues in 8.5.3
Issue ID (internal tracking only) Description Solution BUG-654301 A stale robot operator ruleset was deleted after upgrade. The ProcessStaleRobot agent no longer deletes
stale robot operators from the Robots landing page
by removing the associated ruleset from the operator record after an
upgrade. Instead, the agent stops stale robots and moves them to the
Offline status. BUG-654928 The All robot activities window in the
Robot drill-in does not list activities that
are in progress. The activities that are in progress are available in the
All robot activities window for each robot
operator. BUG-654957 The work group name cannot exceed 32 characters. The work group name can have up to 64 characters. BUG-654968 Receiving the 200 status code, and the
207 status code, if a robot posts the
same assignment twice. If a robot posts the same assignment result twice (for example, due
to an issue with runtime configuration), the assignment status now
displays the status: 404 - Resource not
found. BUG-654298 Standby robots and active robots with enabled schedules are not
auto-balanced. For robots running on schedule and in the
Otherwise state, Robot Manager moves
such robots between work groups as expected if no scheduled action is
going to take place in the next 15 minutes. BUG-654299 Robot Manager UI links do not work after clicking Open
Robot Manager in an email notification. The URL in the Open Robot Manager email button
now addresses the issue. BUG-654300 Robot Manager does not delete the STOP_NOW
command, or any other command, when a robot machine crashes. When the machine that hosts a robot crashes, then Robot Manager
deletes all pending commands for that robot. BUG-654347 An incorrect icon displays on work group tiles for users with
read-only access. For users who have read-only access to the list of work groups in
Robot Manager, and applications built on Robot Manager, the icons that
indicate the work group settings (for example, that auto-balancing is
enabled) display correctly. BUG-654348 Robot Manager deletes a reporting setting when multiple users are
simultaneously modifying that setting. When a user updates a reporting setting in one session, but another
user has already deleted that setting from the application in a
different (simultaneous) session, Robot Manager creates a new version
with the updated value. BUG-654352 In the Robot drill-in page, the Last
active date-time property value becomes empty when the
status of the robot changes while the View all
audit window is open. When clicking View all audit for a robot, that
robot's status on the Robot drill-in page updates
correctly. The Last active property now displays the
actual value. BUG-654520 Robot Manager shows an incorrect number of users assigned with a
package version in a department unit. Robot Manager now uses the identifier to determine the number of
users assigned with a package version in a unit. BUG-654933 A confusing validation message is displayed when a user does not have
a work group associated with them in the Work group and
requestor mapping decision table. BUG-654985 The Last active property value for new robots is
not blank. The Last active property value in the
Robot drill-in screen is empty for new robots,
or for robots that never became active. BUG-655288 Assignments in Robot Manager have Unknown
automation status if no file attachment was
sent. Assignments that did not include a file attachment in the robot
response message (for example, error log), but were completed
successfully, are correctly classified as
Completed in Robot Manager. BUG-655598 The user list cannot exceed 10,000 records, which causes issues with
package assignment. User lists can now exceed 10,000 records, without impacting the
package assignment flow. In addition, you can now find a specific user
record by using autocompletion in search. BUG-655551 Redundant information in the logs in response to a RPA Service
registration error. If a user does not have the
pyGetAccessGroupForRobotByWorkGroup decision
table entry empty, the error message in the logs returns only the
necessary information, for example, Robot registration
failed: Found an empty access group when registering
<robot_name>. BUG-654296 Robot Manager does not count excess robots properly in work groups
enabled for auto-balancing. The step to re-calculate the number of excess robots after the
auto-balancing engine issues the STOP command to
robots in the ready state now provides the
correct value. BUG-657080 Cannot view the user list if that list exceeds 10,000
records. You can navigate through a user list when the database contains more
than 10,000 records. BUG-659474 Cloud: Cannot download the log file from the
Issues landing page when the content storage
differs from the Pega database. The content storage implementation was improved to eliminate the
issue. You can now download automation issue log files when your content
storage is different from the default Pega database. BUG-650125 Robotic work groups display the wrong KPI values because of omitting
archived automations from calculations. Work group KPI calculation now includes archived automations. BUG-660854 With more than 10,000 users in an application, the Robot
Manager portal is not responding while assigning a
Runtime configuration file to a user from the
Runtime config drill-in screen. You can now search for users by using a new autocomplete
field. BUG-660866 PDC: The CommandStatus REST service causes the
PEGA0011 alert. Decreased the REST call duration. BUG-661937 PDC: The Heartbeat REST call causes the
PEGA0011 alert. Decreased the REST call duration. BUG-662184 PDC: The Packages REST service causes the
PEGA0011 alert. Decreased the REST call duration. BUG-653406 PDC: The Packages_Assignment REST service causes
the PEGA0011 alert. Decreased the REST call duration. BUG-660868 PDC: The Register REST service causes the
PEGA0011 alert. Decreased the REST call duration. BUG-660867 PDC: The Get RM endpoints REST service causes the
PEGA0011 alert. Decreased the REST call duration. BUG-662629 PDC: The pzGetCommandAndSvcOpDetailsForAllRobot
activity causes the PEGA0005 alert. The report definition has been improved to accelerate query
completion. BUG-661657 PDC: The pzUpdateRobotHeartbeatWrapper activity
triggers the PEGA0005 alert. Decreased the activity processing time. BUG-661427 PDC: The pzValidateRoboticOperatorAvailability
activity triggers the PEGA0005
alert. Decreased the activity processing time. BUG-659772 PDC: Prolonged database queries by the Auto-balancing engine trigger
the PEGA0005 alert. The report definition was improved to accelerate query
completion. BUG-659779 PDC: The pyGetNotificationsForOperator query to
get notifications takes too long to complete, causing the
PEGA0005 alert. The report definition was improved to accelerate query
completion. BUG-659780 PDC: The pyGetNotificationsCountForOperator
query to get the notification count takes too long, causing the
PEGA0005 alert. The report definition was improved to accelerate query
completion. BUG-661409 PDC: PEGA0035 alert in the activity
pzGetRoboticWorkBasketAssignments Improved the report definition to address the root cause of the
alert. BUG-661170 PDC: The
D_pzGetOperatorsBelongToCurrentApplication
activity causes the PEGA0035 alert. The reload strategy of the
D_pzGetOperatorsBelongToCurrentApplication
activity has been updated. BUG-654346 PDC: The D_pzCaseAssignmentsPastSLA activity is
being reloaded frequently, causing the
PEGA0035 alert. The reload strategy of
D_pzCaseAssignmentsPastSLA has been
updated. BUG-655208 PDC: Frequent reloading of the
D_pxFetchEntityHierarchy data page causes the
PEGA0035 alert. The reload strategy of D_pxFetchEntityHierarchy
has been updated. BUG-663783 PDC: EXCP0001 found in the
pxTransferAssignment activity when invoked from
the pzProcessRoboticAssignments activity. A detailed log message was added for orphan assignments. BUG-663805 PDC: EXCP0001 found in the
pzGetRoboticConsolePeopleList activity. The exception was removed. BUG-664274 PDC: The Package drill-in screen causes the
SECU0019 alert. The section was updated to receive live updates. BUG-654303 PDC: The Robot drill-in screen causes the
SECU0019 alert. The section was updated to receive live updates. BUG-654551 The assignments are not completed properly after the upgrade. The issue was resolved.
Previous topic What's new in Pega Robot Manager Next topic Getting started with Pega Robot Manager and automations