Version 22.214.171.124 Release Notes
Review the new feature, changed feature, fixed features, security fixes, and known limitations in Version 126.96.36.199 for Automation Anywhere Control Room and Enterprise Client.
for Manifest V3 extension
Any of your existing automations that use Manifest V2 extensions for Google Chrome browser will be affected based on Google's planned deprecation for Manifest V2 extensions. By default, Enterprise 11 Version 188.8.131.52 (and later) supports Manifest v3 extension by default for the features that use Google Chrome browser. We recommend that you now implement a plan to switch your automations to use the Manifest V3 extension.
Automations that use Google Chrome Manifest V2 based extensions will stop working after June 2023. The deprecation timelines for Manifest V2 based extensions are currently under review and subject to change by Google. For more information, see:
Support for TLS 1.2 to connect to the SMTP server
(Service Cloud Case ID: 00691755)
You can use TLS 1.2 secure connection to connect to the SMTP server and automate the email-related task.
schedule runs properly as per the occurrence set, even when the
schedule is updated before, or after, the DST (Daylight Saving
Time). Previously, such actions resulted in a schedule running
Service Cloud case ID: 00769779, 00791071, 01811334
Bot deployment failures due to package file being
in use by another process or service is fixed now.
Service Cloud case ID: 00807186, 1707179, 01760114
Analyze tab in Bot Insight dashboard is enhanced to display the
total permitted number of directories and sub-directories that
exceed 2100 (for SQL Server) and 1000 (for Oracle
Service Cloud case ID: 01879764
connecting to the CyberArk vault, the HTTP client that consumes
the ephemeral ports works properly. Previously, this action led
to port exhaustion resulting in an unresponsive Control Room.
Service Cloud case ID: 01688015
|The data in
the .CSV file generated from the Export filtered
items option in the Audit log utility matches
the data shown on the Control Room dashboard.
Previously, there was a mismatch with the data count between the
generated .CSV file and Control Room dashboard.
Service Cloud case ID: 01253785
Devices list displays without any
observed slowness, even when the Control Room
contains large numbers of created Users and Roles.
Service Cloud case ID: 00792857, 01272816
Java 11 updates without any vulnerabilities
that affect the Control Room.
Service Cloud case ID: 01870708
the folders under My Bots sort by
Service Cloud case ID: 01581684, 01753558, 01578833, 01698746, 01755816, 01765512, 01782302, 01788348,01798499, 01753429
work item details under the Queue column
only displays the correct user ID for those users who have
access to the queue.
Service Cloud case ID: 01830283
default entry is correctly inserted in the database and the
status is set to False on bot.
Service Cloud case ID: 00787717, 01780064, 01823313
updating to Version 184.108.40.206, the contents of
all aapkg files are validated before
Service Cloud case ID: 00803771
in the WLM queue complete without issues because you can add a
custom path to store files instead of using the default system
Service Cloud case ID: 00647695, 00812334, 00830851
items in queue status or in progress process without any errors.
Service Cloud case ID: 01865475, 01889119
|The library version for the
vulnerabilities reported in the security scan has been
Zendesk ID: 161610
contents of all aapkg files within the
imported bots are validated before
Zendesk ID: 65807 | Service Cloud case ID: 00803771
error message is displayed without the entire filepath when you
download the Acknowledge API.
Service Cloud case ID: 00803776
is updated to a non-vulnerable version.
Service Cloud case ID: 00376109, 00682821, 00682821
|When you upgrade the Control Room to Version 220.127.116.11, you might experience some downtime. Before you start the upgrade, pause all the WLM queues and ensure that there are no Work Items in progress.|
|When you attempt to uninstall the Version 18.104.22.168 patch, a warning message appears, and you cannot uninstall the Version 22.214.171.124 patch. You must uninstall the Version 11.3.5 base version.|
you install Version 126.96.36.199 patch in
Silent mode, the Manifest V3 registry
entries might not be present in the Registry editor. As a
result, you cannot extend the Manifest V2 extensions using the
For workarounds and more information about the issue, see How to install Google Chrome Plugin.