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:
  • Access license usage data for various users across the platform.
  • Analyze Bot creator license usage details based on number of logins, new automations, check-ins, and check-outs.
  • Drill down to specific license usage information.
  • Track usage trends over time.

These features provide a comprehensive view of your license usage, facilitating better management and optimization of resources.

Licenses | License dashboard
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.

Using virtual window (PiP) for developers | Run automations in virtual window (PiP)
Connector Builder enhancements

The Connector Builder is enhanced with the following capabilities:

  • Add multiple headers to the API Key based authentication.
  • Delete existing headers.
  • Display the number of actions that are configured for a connector. If enabled, the authentication action is included in this number.
  • Copy, enable, and disable the following in the connector editor:
    • Actions
    • Request parameters
    • Request headers
    • Form data request body parameters
    • Form URL encoded data request body parameters
    Note:
    • When you disable an action, a Disabled label is displayed next to the name of the action in the connector editor.
    • When you disable a request parameter, request header, or request body parameter, the Status column in the Headers table is updated accordingly.
  • When a custom connector fails to publish due to any errors, a notification with information about the error appears in the Control Room Notifications. The Audit log is also updated with the same error message.

Enable authentication action
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.

Event triggers
API Tasks enhancements

The API Tasks now support Web triggers.

Web triggers workflow

You can stop the API Tasks that are in progress from the In progress activity page.

Activities
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

BeyondTrust Password Safe integration
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.

Using Update work item action

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.

Package visibility
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
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.

Update nodes in a cluster setup
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.

Export bots | Import bots
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.

Persistent table customizations across sessions and browsers
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.

Transfer credential ownership
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.

OpenSearch custom certificate
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.

License grace policy and notifications
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.

AI Guardrails
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:
  • Active MQ service.
  • Elasticsearch service.
  • Ignite service.

Verifying Automation Anywhere services

Fixes

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 automation is executed successfully.
  • The upload quota for that user has not yet been allocated.
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 /v3/activity/list API did not accurately reflect the modifiedBy for in-progress bots.

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 Activity > Historical 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 (Administration > Licenses), 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 (Administration > Settings > Deployment), 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

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