Review what's new and changed, and the fixes in Automation Workspace for the v.39 release.

What's new

Control Room, devices, and Bot Agent

Streamlined access: View your latest AI Agents alongside automations

We have improved the Control Room Home Page/Dashboard to help developers find and continue their work more easily. The My Automations section now shows recently accessed or edited AI Agents. This gives you a unified view of your most important automations and AI-driven workflows, all in one place. This update makes your development workflow smoother by reducing the need to switch contexts and improving visibility of your key assets.

Process-level metrics for observability in the Processes Dashboard

Enterprise users can now explore special metrics pages for each process in the Processes Dashboard. This provides real-time insights into how automation is working and its reliability. It helps you understand how automation is performing, identify patterns, solve problems, and improve processes. You can:
  • Drill down into each process to see important charts: Cumulative Status, Success/Failure Trend, and Process Aging.
  • Check data using a default 30-day view with search, filters, and CSV export features.
  • Enjoy easy navigation with a Close button to return to the main dashboard.
  • This is available for On-Premises and Cloud Enterprise License users with the View all requests from public processes permission and the ENT_PROCESS_INSIGHTS flag.

Monitor, analyze, and improve your automations faster, right from the Processes Dashboard.

Processes dashboard

New Custom Date-Time range added to the Automations dashboard (Service Cloud Case ID: 02188024)

Now you can choose exactly how you want to filter and view automation run data using custom time filters from the Automations tab. This means you do not have to use broad pre-set time filters such as 24 hours or 7 days). For example, you can:
  • Get automation run data from 1st September to 10th September.
  • Review data on a monthly basis, such as September run data or October run data.
  • Access data from one year ago.
  • Look ahead 30 days into the future to get automation schedules for the next 30 days.

This gives you precise scheduling, better control, flexibility, and clarity for audits.

Automations dashboard

Expanded ARCON key vault integration

With this update, ARCON key vault integration has been expanded to include A360 service account, database, Active Directory, and SMTP. This feature is now available for both On-Premises and Cloud deployments, with different capabilities for each. On-Premises environments support ARCON key vault for auto-login, automation, A360 service account, database, Active Directory, and SMTP, while Cloud deployments support integration for auto-login and automation.

ARCON Key Vault integration

Expanded BeyondTrust Password Safe integration

With this update, BeyondTrust Password Safe integration is now available for both On-Premises and Cloud deployments, with different use case capabilities for each. For Cloud deployments, BeyondTrust Password Safe integration is available for automation and auto-login use cases, allowing administrators to configure it as the external vault so that automation credentials are securely managed from BeyondTrust. For On-Premises deployments, the vault integration supports auto-login, automation, A360 service account, database, Active Directory, and SMTP credentials. Currently, configuration for On-Premises deployments is performed using CRUtil.

BeyondTrust Password Safe integration

Custom naming option for key vault credentials

When creating credentials for supported key vaults such as AWS, CyberArk, Microsoft Azure, HashiCorp, users now see a checkbox that allows them to specify a custom secret name according to their own naming convention. This enhancement is available for both Cloud and On-Premises Control Room deployments.

Create credential

Licensing management for Automation credits

Licensing management features such as license capacity thresholds, license capacity notifications, grace period, and grouping are now supported for Automation credits.

Using Automation credits
Universal web triggers

This release introduces Universal web trigger package that allows you to create triggers for any application that supports webhooks or polling. The Universal web trigger contains Listener trigger and Poller. You can use the Listener trigger for webhook based workflows and Poller for polling based workflow.

Note: The Poller is currently in beta.
Support for AWS Signature in Connector Builder

Connector Builder now supports AWS Signature v4 authentication enabling users to create custom packages for AWS based workflows. This feature enables the packages to integrate easily with various AWS services such as EC2 APIs, Lambda functions and S3 storage, without exposing any sensitive data

Support for Spanish language in Connector Builder

The Connector Builder page is now available in Spanish language.
Task and Device platform details in Audit log

Starting from this release, automations that completed successfully will include the platform information (Windows or macOS) for the task and device in the Run bot finished details table. Administrators or users with View everyone's audit log actions permission can navigate to Administration > Audit logs, and click the automation with the Event type as Run bot finished to view the attributes in the Run bot finished details table.

Audit log | Audit events list
APIs and integrations
Automation Command Center (ACC) Automations APIs

Documentation is now available for the new Automation Command Center (ACC) Automations API endpoints in Swagger and the documentation portal.

ACC Automations API
Workload Management (WLM) Queue APIs enhancement

You can now use enhanced Workload Management Queue APIs to manage queues and related work items more reliably. The following endpoints were fixed and validated to ensure accurate request and response handling:

  • v3/wlm/queues/export and v3/wlm/queues/import
  • v3/wlm/queues/{id}/members/{memberId}
  • v3/wlm/queues/{id}/workitems/list
  • v3/wlm/automations/list and v3/wlm/automations/{id}
Export queue(s) (POST v3/wlm/queues/export):
Draft queues included in an export request now return a clear validation message indicating that queues in draft status cannot be exported. Previously, draft queues produced a generic error with a null message.
The Swagger and documentation has been updated to reflect the correct request payload parameter (encryptedPassword).
Queue Member APIs (POST v3/wlm/queues/{queueId}/members/{userId}):
Now validates all user and queue IDs. Invalid or nonexistent user and queue IDs now return a 404 Not Found status with descriptive messages such as “The user wasn’t found” or “The queue not found.” Previously, these requests returned 200 OK even though no update occurred.
Queue Update API (PUT v3/wlm/queues/{queueId}):
The autoRetryLimit field now validates values to ensure they are within the supported range (0–10). Previously, out-of-range values were accepted and incorrectly saved.

Workload Management API

What's changed

Control Room, devices, and Bot Agent

Enhanced WLM queue design for smarter and faster processing

We’ve introduced significant improvements to Workload Management (WLM) to make work item processing faster, more consistent, and more scalable. The key enhancements include:
  • Optimized query performance: Experience quicker retrieval and processing of work items with reduced CPU and I/O usage, improving overall system responsiveness.
  • Consistent and prioritized processing: Work items are now automatically served in a sorted order, ensuring that high-priority tasks are executed first. Sorting can be configured using up to three user-defined columns or defaults to insertion date.
  • Smarter queue design: A new sort order column in the database enables efficient lexicographical sorting across numeric, date, and text values, supporting complex prioritization use cases.
  • Simplified processing logic: The redesigned workflow eliminates the need for the Ready to Run status, resulting in a cleaner, more intuitive experience.
  • Improved scalability: Enhanced batching and sorting mechanisms ensure seamless handling of large volumes of work items without impacting performance.

Service Cloud Case ID: 02226601

Work item status and actions | WLM work item lifecycle

Enhanced access control for editing WLM automation

We’ve made it easier to view and control your scheduled automations at the folder level with the below enhanced permissions:
  • View all scheduled automations from my folders

    You can now see all Workload Management (WLM) automations running on bots in any folder you have access to.

  • Manage all scheduled automations from my folders

    You can now pause, resume, stop, or edit WLM automations on bots in your accessible folders. It gives you more flexibility to manage automations without needing broader admin rights.

Together, this enhancement makes it simpler to monitor and control automations across shared workspaces, improving efficiency and collaboration.

Service Cloud Case ID: 02185422, 02192197, 02186389

Edit Workload Management automations

Enhanced audit log message for email notification settings

The audit log message for email notification settings is now updated to capture detailed information about configuration changes. Previously, it used to record high-level headers. With this enhancement, the audit log message includes which configurations are updated (checked or unchecked), providing a clear difference between the previous and new states of the email notification settings.

Edit email notifications

AWS as the Default Global Cloud provider

Amazon Web Services (AWS) is now the default global Cloud provider for hosting tenants. However, if you have a strong preference for GCP, you should work with your account team to choose GCP as the preferred Cloud provider before closing the sales transaction. Existing customers are provisioned in the same region as their other tenants to ensure region affinity unless a different country is chosen during tenant provisioning.

Automation 360 Cloud FAQ

Automatic deletion of IDC users in Amazon Q upon Automation 360 instance deletion

This feature is applicable to all Cloud Control Room deployments where users have the Conversational Automation Co-Pilot User license assigned.

Previously, AWS IAM Identity Center (IDC) users were created in Amazon Q by Control Room, with user names starting with the Automation 360 Control Room instance UUID. With this new enhancement, when a Control Room instance is deleted, all corresponding IDC users are now automatically deleted in Amazon Q as well. This user management process is handled by Automation Anywhere.

License details Control Room UI updates

Document AI Credits is now renamed to Document Automation Credits in the License details page of Control Room.

Using Automation credits | Glossary
Remote Desktop login on Windows 11 with Network Level Authentication enabled

Starting from this release, while using the Remote Desktop on a Windows 11 operating system, the Require devices to use Network Level Authentication to connect option in Settings > Remote Desktop need not be disabled.

Auto-login support for Bot Agent
Successful deployment of automation when auto-login is disabled on macOS( Service Cloud Case ID: 02220602)
Starting from this release, automation deployments are executed successfully even when the auto-login plugin is disabled and Java accessibility is not added on the macOS device, whether it is in either locked or unlocked state. This enhancement also includes the following updates:
  • If the macOS device is locked, the automation runs without unlocking the screen.
  • If the macOS device is not locked, it will continue to remain unlocked after execution.
  • Log off scenarios (such as Always Create New Session or Reuse if available with Log off) are not supported under these settings.

Configure auto-login settings on macOS device
Extended the limit on the number of URLs in autoregistration.properties file (Service Cloud Case ID: 02229575)

After you update to this release, the total number of Control Room URLs and their corresponding registration keys that can be included in the autoregistration.properties file will be increased to 100 from the previously set limit of 20.

Configuring the Bot Agent Windows Installer file

Fixes

After updating to this release, the Compare Versions feature in Task Bot now displays the variable names correctly and ensures that hyphens and uppercase characters are preserved during version comparisons, maintaining clarity and consistency.

Service Cloud Case ID: 02152865
The View activity page is now updated to ensure that the messages that relate to any of the automations that completed or terminated are displayed correctly with all the corresponding details.

Service Cloud Case ID: 02207094
The Ignore Unexpected Pop-up runtime option is no longer displayed for macOS bots, as this option is not supported on the macOS platform.

The Running count in Automation status–public showed more automations than were actually active in In progress activity page. Old bot execution records were mistakenly included as running.

Now, there is no data discrepancy between the In progress activity page and the Automation Command Center (ACC) Dashboard.

Service Cloud Case ID: 2212344, 02219747, 02220167
After updating Automation 360 to this release, the scheduled tasks no longer fail as the process now handles parallel requests correctly, preventing transaction conflicts.

Service Cloud Case ID: 02223633, 02230378
We resolved a problem where bot execution metrics might not be created for a Control Room with over 2,000 users. This caused bot run metrics to be incomplete or missing in reporting dashboards. We improved the metrics generation process to manage large user groups without going beyond database limits. Now, all affected reporting services work as they should.
The total number of licenses consumed and available is now correctly displayed across all license groups.

Previously, it showed inaccurate values in some cases.

Service Cloud Case ID: 02233074
License consumption details on the license page are now displayed correctly across each control room.

Previously, it showed incorrect values unless you synced the license from the server.

Service Cloud Case ID: 02211894
You can now assign the Automation Co-Pilot Business User license via IdP group mapping without any issues.

Previously, the license would disappear after saving.

Service Cloud Case ID: 02278608
You can now register OAuth applications in the Control Room when customer licenses are grouped.

Previously, registration would fail under these conditions.

Service Cloud Case ID: 02219437
You can now successfully export audit logs with 100 or fewer entries per page.

Previously, exports would fail in this scenario.

Service Cloud Case ID: 02186751
You can now edit custom roles assigned to large user groups.

Previously, this triggered an error and the list of assigned users was not visible in the Users tab.

Service Cloud Case ID: 02196729, 02165691
Notification emails are now sent from the Control Room on On-Premises environment without requiring a service restart when the SMTP server recovers from an issue.

Previously, notifications were not delivered until the service was restarted.

Service Cloud Case ID: 02206905
Imports performed on repositories located on mounted file systems no longer fail intermittently with unexpected Missing dependencies errors. We’ve added a retry mechanism to make sure the file is ready before the system validates it. Imports and promotion workflows now run smoothly and consistently.

Previously, the import process could attempt to validate the uploaded file before it was fully created on the mounted drive, resulting in sporadic failures during import and promote operations.

Service Cloud Case ID: 02217270, 02219552