Automation Workspace v.36 release
- Updated: 2025/07/03
Automation Workspace v.36 release
Review what's new and changed, and the fixes and limitations in Automation Workspace for the v.36 release.
What's new
| Control Room, devices, and Bot Agent |
|---|
|
License
dashboard in Automation Command Center
A new
License dashboard has been added
to Automation Command Center (ACC), enabling effective
monitoring and analysis of Automation 360
license usage. With the intuitive interface, you can:
These features provide a comprehensive view of your license usage, facilitating better management and optimization of resources. |
|
Support
for RDP based deployments on Azure AD joined device
(Service Cloud Case ID: 02145409) The RDP based deployments are now supported on Pure Azure AD joined devices. |
|
Picture-in-Picture
(PIP) support for Citizen Developers and 专业开发人员
(Service Cloud Case ID:
01903569, 02153763) Citizen Developers and 专业开发人员 can now run their automations in parallel with regular work. This enhancement provides an option to run their private automations in a virtual window, improving adoption of Citizen Developer Program. |
|
Connector Builder
enhancements
The Connector Builder is enhanced with the following capabilities:
|
|
Web triggers
enhancements
You can also view, monitor, and control automations from the Event triggers page. The Event triggers page displays the number of web triggers that are configured for an automation, and the status of the configured web triggers. |
|
API Tasks
enhancements
The API Tasks now support Web triggers. You can stop the API Tasks that are in progress from the In progress activity page. |
|
BeyondTrust
Password Safe integration with Automation 360
Automation 360 now supports BeyondTrust Password Safe for Cloud deployments, adding flexibility for bot auto-login use cases |
|
Run time
variable support for work item values
As a Bot Creator, you can now use the variable expressions in the Record attribute values. You can now specify a variable as work item value and the corresponding variable value will be fetched at run time. |
What's changed
| Control Room, devices, and Bot Agent |
|---|
|
Revised
audit log for notification settings
With this improvement, the audit logs for notification settings have been revised to make it more readable and consistent across the Control Room. |
|
On-Premises: Package usage
visibility in automations
A Control Room administrator and authorized users with valid package permissions can now view which automations use a specific package or a specific package version. This enhancement lets you review or update the related automations if any changes are required. |
|
Production
label selection on parent automation is applied to dependent
automations (Service Cloud Case ID: 01804743) If Production label option is selected on a parent automation, the corresponding dependent automations with the Production label are also automatically selected when you use the Run, Schedule or Run with queue options. However, if any of the dependent automations does not have the production label applied, the Latest version of the automation is selected. |
|
No
Elasticsearch (OpenSearch) index and service status
validation during update (Service Cloud Case ID:
02150976) When you update to this release from any of the previous three releases (n-3), the Elasticsearch (OpenSearch) index and service status validation is no longer performed. |
|
Global
value scoping during
Export and
Import operations
As a Control Room user, you can now include scope of global values when performing export and import operations. This enhancement enables you to include the global value scope across the Control Room (both source and target). With this adjustable scope, you can change the global values more easily. |
|
Table
customizations saved across sessions and browsers
(Service Cloud Case ID: 00807835, 01788099, 01615306,
01820487, 01878510, 01971500) Changes made to the landing pages of tables are now successfully saved in the database, ensuring they persist across sessions, browsers, and devices. |
|
Credential
transfer changes (Service Cloud Case ID: 02096892,
02168258) Users can now transfer credential ownership of a credential to another user if the user is part of the locker. This ensures continuity and enables access control. |
|
Support
for customer certificates in intra-cluster communication for
OpenSearch
Automation 360 now supports the use of customer-supplied certificates for intra-cluster communication in On-Premises deployments for OpenSearch. This enables enhanced security and compliance by allowing customers to use their own trusted certificates. |
|
Updates
to license grace policy notifications
The notifications for license grace expiry and grace entry have been updated to reflect the license grace entry and license grace expiry scenarios. This update ensures accurate and timely notifications for these events. |
|
Data
retention with AI Guardrails
Sensitive entities like PII, PHI, and PCI in prompts are replaced with non-sensitive tokens, securely stored for 30 days, and restored to their original values in model responses when AI Guardrails is enabled. |
|
On-Premises: Enhanced Automation Anywhere Control Room Monitoring
Service
With the enhanced Automation Anywhere Control Room Monitoring Service, we are
now monitoring data of various services which include:
|
Restricted number or size
of work items returned for POST
/v3/wlm/queues/{id}/workitems/list API
As part of continuously enhancing our APIs, we have implemented a new restriction for Workload Management work item list API. With this enhancement, the number of work items retrieved is limited to 1000 or the total size of the work items retrieved is limited to 300 MB. The API response will look for either of the limits, whichever is encountered first. If the number or size of work items for the corresponding API request exceeds these limits, the API response will fail with an error message. To resolve the error, reduce the number or size of work items retrieved by the API request. If you are currently making requests with a larger number or size of work items exceeding the specified limits, we recommend you to reduce these values. Alternatively, if you require a window to adhere to these new limits, contact Automation Anywhere Support for assistance so that your specific use case and requirements can be captured, and to help us identify alternatives to avoid any unexpected failures. |
Fixes
| After you update
to this release, the email that is triggered when an associated
run-as user is deleted from a schedule activity now contains the
URL for the correct tenant. Service Cloud Case ID: 02197645 |
| If you have
integrated BeyondTrust Password Safe in your Control Room, you can now fetch multiple secret
mappings without any errors. Previously, an error was logged in such a scenario. Service Cloud Case ID: 02215044 |
| After
you update the Bot Agent to the version
available with this release, execution errors no longer occur
and the automations are deployed successfully. Service Cloud Case ID: 02183438, 02198192 |
| The maximum number of items
displayed per page in the Control Room is now
fixed at 200 to ensure consistent and optimal performance. Few
examples of pages where this change is implemented:
Service Cloud Case ID: 02209143 |
| After
updating Automation 360 to this release, in the
Control Room if the option is enabled for automatically updating the
Bot Agent version, or if you use the option to update the Bot Agent version, the MV3 extensions of Google Chrome and Microsoft Edge are no longer disabled.
Service Cloud Case ID: 02207128, 02207131, 02207391, 02207683, 02207128, 02207788, 2209168, 02209185, 02209700 |
| When you update
to the Bot Agent version available with
this release, RDP based automation deployments that use the
username in the UPN (User Principal Name) format now work
without any
issues. Service Cloud Case ID: 02203327, 02203319 |
| When you update
to this release, automations that have the same scanned and
manual dependencies no longer fail with pre-processing error
message on multiple deployments. Service Cloud Case ID: 02202339 |
| After you update
to the Bot Agent version available with
this release, the AWS Workspace
no longer crashes even when Bot Agent is
uninstalled from the device. Service Cloud Case ID: 02161601 |
| After you update to
this release, the unattended Bot Runner
deployments get processed if there are no active executions.
However, if there are active executions, these automation
deployments will be queued and deployed when the currently
running executions complete.. Service Cloud Case ID: 02159985, 02170822 |
| Publish the custom packages
that you create with Connector Builder
successfully. Previously, a signature verification failure error caused the publishing process to fail. Service Cloud Case ID: 02196908, 2203315 |
| You can
install or update Automation 360 to this release
without any issues even when the default installation directory
for the Control Room installer has changed.
Service Cloud Case ID: 02199702, 02199685, 02200287, 02201584, 02201917, 02201939 |
| After
you update to this release, the automation deployments
(console-based) on unattended Bot Runner devices
with the log off state no longer fail. Previously, this would
happen intermittently when a Bot Runner device
received an automation deployment request before the existing
session was logged off. Service Cloud Case ID: 02182119, 02180333, 02183912, 02184142, 02181532, 02183285, 02184230, 02184242, 02185154, 02184044, 02183402, 02183457, 02184226, 02185775, 02185671, 02183811, 02185293, 02188077, 02189887, 02194235, 02185002, 02185009, 02185051, 02185019, 02185045, 02185608, 02195155, 02202232, 02180495 |
| After
updating to this release, both attended and unattended
automation deployments (including the ones that last longer than
60 seconds) complete without any issues, and the execution
details are captured in the log files. Service Cloud Case ID: 02170893, 02185666, 02185667,02187302, 02188440,02178128, 02187946,02196547, 02197595, 02188189 |
| After updating to
this release, intermittent runtime error messages are no longer
displayed even when you deploy automations is short succession.
Service Cloud Case ID: 02150714, 02164931 |
| For a file creation
event using File and Folder trigger, the
associated bot logic is deployed for the event only once.
Service Cloud Case ID: 02175501 |
You can now use
the Google Cloud > Vertex
AI: Connect and
Disconnect actions within the
Generative AI package without any errors related to
JacksonFactory. Previously, automations
using these actions would experience connection failures when
using the Connect and
Disconnect actions.Service Cloud Case ID: 02161408 |
| In a multi-tenant
deployment, the job execution completes successfully on the
remaining tenants even when the Control Room
license has expired on any one of the tenants. Service Cloud Case ID: 02137519 |
After updating to
this release, the automation run clip is now saved without any
issues when the following conditions are met:
|
The v2/repository/file/list API now includes
the missing fields in the API response and ensures the
locked field correctly indicates whether an
automation is checked out. Previously, the
v2/repository/file/list API returned an incomplete response,
missing fields like lockedBy,
productVersion, and
latestVersion. Additionally, the
locked field did not accurately reflect the
checked-out state of automations, leading to
inconsistencies.Service Cloud Case ID: 02152083 |
| When you perform a
bulk package update using the Bot
update option, you no longer encounter any error
or exception messages. Service Cloud Case ID: 02105984, 02131991 |
|
You no longer encounter an error message when copying a Recorder action from a cloned bot. Service Cloud Case ID: 02146968 |
| After editing a
workitem, the details are now saved successfully in the
Audit log comment section.
Additionally, these saved comments can be viewed in the
Update work item details
section. Service Cloud Case ID: 02163256 |
| When you export a bot which has the production label, it no longer
exports the dependencies from the latest bot
version. Additionally, it imports the bot
successfully without dependencies from the latest bot version. Service Cloud Case ID: 02158809 |
The
/v3/activity/list API accurately reflects
the modifiedBy for in-progress
bots.Previously, the Service Cloud Case ID: 02148994 |
| When automation recording is turned on and an automation deployment fails because of issues like wrong device credentials or an unavailable session, the automation recording stops. As a result, the Bot run clip section in will not be displayed. |
|
Packages (such as Database, Task bot, or
Dictionary) where the Add variables
mapping option is available. When you enter the
key name in the Add key field and then
create a variable to map the key to the variable, you will no
longer encounter an issue as the keys and the mapped variables
are now populated correctly. Previously, due to an error, the keys and the mapped variables were not populated, and the mapped variables table displayed blank values. Service Cloud Case ID: 02167368, 02177340, 02178160 |
|
When a bot with captured images is checked in and secure recording was enabled during capture, the images will no longer be visible when the bot is opened in view mode from the public repository, nor will they appear in the metadata folder. Service Cloud Case ID: 02164805 |
| When you execute
package version updates using repository management APIs, the
request is now completed for both parent and dependent bots. Previously, when the parent bot ID was only passed, the request would be completed for the parent bot, and the dependent bots would get stuck in the In-progress status. Service Cloud Case ID: 02161948 |
| A
scheduled automation is now executed successfully when the
associated Run-as user that was previously disabled is
enabled. Service Cloud Case ID: 02165361 |
| Event details in
the audit log are now displayed in the language selected by the
user in the details column. Previously, error messages during bot import were logged in a language different from the user's selection. Service Cloud Case ID: 02150311 |
| When creating
custom roles, the Download data files
permission is successfully saved. Previously, some users could not select the Download data files permission check box after creating a custom role Service Cloud Case ID: 02163477 |
| On the license
group edit page (), you can now successfully transfer grouped GUIDs
from the available instances of the Control Room
to the Selected pane at a time.
Previously, when users attempted this action, the transferred GUIDs did not appear in the Selected pane. |
| Locker owners can
now access lockers with view or edit permissions alone.
Previously, users required additional permissions when accessing the locker. Service Cloud Case ID: 02177097 |
| When a user with a custom role but with View Settings permission logs into Control Room (), the page loads successfully. Previously, this action resulted in an error and required Manage Settings permission in addition to View Settings permission. |
| An On-Premises
Control Room with a default tenant ID of all
zeros can now connect and synchronize licenses with the Cloud license server, even if multiple
instances share the same tenant ID. Previously, only the last instance of the Control Room could successfully install a Cloud license, while other instances of the Control Room entered fail-safe mode (a state with limited functionality due to licensing issues). We recommend that you do not create new Control Room instances from an existing database to avoid these problems. Service Cloud Case ID: 02163947 |
| You can
successfully install a new GUID on Cloud
Control Room instances even if the earlier GUID
has expired on or before 1st Jan 2025. Previously a new GUID could not be installed for a Cloud Control Room if the earlier GUID had expired on or before 1st Jan 2025. Service Cloud Case ID: 02199670 |
| Users can now
successfully allocate Google Document AI and Document Automation licenses to a license group.
Previously, license distribution across different instances of the Control Room failed as the license server incorrectly extended the validity of metric-based licenses to the maximum end date, causing insufficient license errors when creating groups. Service Cloud Case ID: 02180364 |
| You can use the
Bot Scanner to scan automations that are
using Gmail with Basic authentication mode in the Connect, Send,
Forward, Reply and Reply All actions in the Email package and
Email Trigger. Previously, users could not perform these operations. Service Cloud Case ID: 02180604 |
| The issue where
users could see outdated execution records as active on their
devices has been resolved. Now, only executions from the past 90
days are displayed accurately. Service Cloud Case ID: 02201315, 02201426, 02201443, 02201562, 02201770, 02202297, 02202249, 02202247, 02202528, 02202367, 02202314, 02202253, 02202359, 02202352, 02202304, 02202380, 02201432, 02202277 |
| You can now view
entries for deleted users in the Manage custom secret
mapping pane, allowing you to remove these
entries if the user has been deleted from the Control Room. Previously, when a user was deleted from the Control Room and had custom secrets mapping enabled for device auto login, the user mapping was not displayed (). Service Cloud Case ID: 02203198 |
| When you have more than 10 devices or 10,000 data rows in the Device utilization details widget, it no longer shows incorrect device details data. |
| Fixed security
vulnerability issues by updating Apache Ignite version to
2.17.0. For more information, click the release download link
and view the Security & Compliance reports at A-People Downloads page (Login required). Service Cloud Case ID: 02189688, 02193476 |
| Fixed security
vulnerability issues by updating Azure library version to
1.15.1. For more information, click the release download link
and view the Security & Compliance reports at A-People Downloads page (Login required). Service Cloud Case ID: 02170378 |
| You can now upload
the files which have empty content type or Type label as
Other such as VB Script, ps1 Script,
or Excel to Control Room without any
error. Service Cloud Case ID: 02196714 |
Limitations
| If you add a child automation
(bot) with manual, scanned or metadata
dependencies as a dependent to a parent automation, a runtime
error is displayed when you run that parent automation and the
deployment fails. Service Cloud Case ID: 02213434, 02212482, 02213903, 02214567 |
| When you use the Loop
action and change the loop iterator from CSV/TXT
(for each row in CSV/TXT) to Database (for each row in a SQL
query dataset), an error is encountered on the Bot editor screen that prevents you from
developing the automation. Workaround: After you set the CSV/TXT (for each row in the CSV/TXT iterator), save the bot to avoid the error on the screen. |
| In the Event triggers page, when adding an API Task with web triggers, the Choose a user modal displays all the users in the Control Room instead of displaying the users with run permission for the folder in which the API Task is checked in. |
| When you create a bot (below Automation 360 v.36) with trigger and disable the trigger, the bot is shown up in the Add event trigger window after checking in it into the public workspace. Also, the bot shows incorrect values even if the triggers are disabled. |
| When you perform bulk package update for List
package, an Any
variable that is used as List, returns
the Undefined
type.
Workaround
|
| Limitations from previous releases |
|---|
| The expand/collapse option is not available in the Triggers section of API Tasks in the Bot editor. |
| When you deploy an old version bot that has the Production label and latest version have recaptured the metadata, the bot deployment fails. |
| When you check-in a bot to the folder with the name System, the bot version is not displayed correctly. |
| When you copy or save a bot as a template that contains metadata with an expiration date set, the copied or saved template file shows metadata records without an expiration date. |