Automation Workspace v.36 release
- Updated: 2025/03/13
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 Azure AD joined devices. Auto login support for Bot Agent | Configure RDP-based deployment for multi-user devices |
Picture-in-Picture
(PIP) support for Citizen Developers and Professional Developers (Service Cloud Case ID:
01903569, 02153763) Citizen Developers and Professional Developers 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 The API Tasks now support Web triggers. 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. |
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. Administer notifications for Control Room | Enable or disable event categories | Manage notification email report | Enable email report channel |
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. Run automation from public workspace | Schedule an automation | Using the Run with queue |
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. |
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. |
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:
|
Fixes
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 |
After updating to this
release, scheduled automations are no longer queued with error
messages and are now deployed successfully. Service Cloud Case ID: 02162776, 02163343, 02155561, 02155562, 02155616, 02156240, 02162776 |
Event details are now displayed
in the language that user has selected in the details column of
Audit log. Previously, when errors occurred during the import of a bot and were logged in the Audit logs, the messages was displayed in a language other than the one selected by the requester. 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 |
In the license group edit (Available control rooms to
the Selected pane at a time.
Previously, when a user performed this action, the moved GUIDs were not displayed in the Selected pane. |
) page, you can now successfully move the grouped
GUIDs from the
Locker owners can successfully
access locker after updating to Automation 360.v34
release with view or edit locker permissions. Previously, users required additional permissions when accessing the locker. |
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 permission. |
Limitations
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. |
Limitations from previous releases |
---|
The expand/collapse option is not available in the Triggers section of API Tasks in the Bot editor. |