Automation Workspace v.38 release
- Updated: 2025/10/03
Review what's new and changed, and the fixes and limitations in Automation Workspace for the v.38 release.
What's new
| Control Room, devices, and Bot Agent |
|---|
| Introduced Quick add on
Bot editor Use the Quick add feature in the Bot editor, which allows you to add actions within the canvas contextually without needing to drag each action from the Actions palette. |
| Support for Co-Pilot for Automators and Autopilot in Next-Gen Process Composer The Next-Gen Process Composer now supports both
Co-Pilot for Automators and Autopilot, enabling faster and more intuitive
process design for developers.
|
| Microsoft Windows Server 2025 Datacenter
certification (Service Cloud Case ID: 02192693,
02192693, 02195408, 02197384, 02211921) Starting from this release, the installation of Control Room and Bot Agent is certified on Microsoft Windows Server 2025 Datacenter across Amazon Web Services Elastic Compute Cloud (EC2) environment. Microsoft Windows Server 2025 Datacenter | Operating system compatibility |
Integration with Delinea Secret Server for Cloud deployments Automation 360 now works with Delinea Secret Server for Cloud and On-Premises Control Room deployments. This enhancement increases the number of secure key vault vendors available for managing credentials and automation, making enterprise security even stronger.Control Room administrators can safely store secrets and credentials in Cloud and On-Premises environments. This storage is compliant with security standards. It also supports auto-login, allowing automations to easily access credentials stored in Delinea for secure login purposes. Service Cloud Case ID: 01803976, 01807571, 01829562, 01955811, 02183725, 02121986, 02199938 |
|
Enhanced Credit Consumption usage details A new Credit Consumption tab has been
added to the Usage details section of
the License details page. This makes
it easier to see and understand how credits are used. It
gives more detailed information about these types of
Automation Credit Licenses:
Before, users could only see a summary of credit usage. Now,
with the new feature, administrators can:
This gives better transparency and control over how credits are used, which helps with budgeting, planning, and checking automation workloads.
|
| Packages certified for Microsoft Office (LTSC Professional Plus)
2024 (Service Cloud Case ID: 02200452) Starting from
this release, you can use the Microsoft Office LTSC Professional Plus 2024
version of Microsoft Office within the
actions available in the following packages to build automations:
|
| Deploy
automations on RDSH session using VMware Blast and PCoIP
(Service Cloud Case ID: 02170282) Remote Desktop Session Host
(RDSH) is a Windows Server role that allows multiple users
to access individual desktop sessions on a single server,
typically through Remote Desktop Protocol (RDP). Starting
with this release, in addition to the Microsoft RDP you can
now deploy automations on sessions created using the
following VMware protocols:
|
|
Enhanced Edit role alert and audit logging To improve governance, transparency, and auditing within the Control Room, we have added a new alert and logging system. This system activates when users try to edit roles they are assigned to. It helps prevent unauthorized privilege increases while keeping administrative flexibility.
Service Cloud Case ID: 02139397 |
|
New consumption-based license model for Conversational Automation Automation Anywhere has introduced a new consumption-based license model called Conversational Automation Interactions (Number of Interactions). This license type is designed to track and manage usage based on how many human interactions start through the Automation Co-Pilot interface. This update helps in situations where pricing and scalability match actual usage, giving businesses the flexibility to adopt Conversational Automation at their own pace. |
|
Support for forward proxy in Control Room-managed OAuth connections Control Room-managed OAuth connections are now aware of the forward proxy set up in the On-Premises Control Room (if a forward proxy is defined). This is important for connecting to external services such as Google Suite APIs. In previous releases, OAuth connections did not recognize or use the forward proxy configuration, which caused problems in environments with proxies. To solve this, the Control Room now sends OAuth connection traffic through the forward proxy server that is configured in the Control Room. |
|
Configurable email notifications for locker membership changes Administrators can now decide if email notifications are sent when a user is added to or removed from a locker. This enhancement reduces unnecessary emails and lets users manage their email settings better. New options for email notifications have been added to the page, in the Email
Configuration tab. There are two new check
boxes:
Note: To keep things consistent
with the current system, which always sends email
notifications for these events, both check boxes are
turned on by default for new installations and version
updates.
|
| Cloud support for package usage visibility in automations Control Room administrators and authorized users with valid package permissions can now view which automations are using a specific package or package version in Cloud environments. This enhancement improves package management transparency by allowing teams to quickly identify dependencies and assess the impact of any package changes. |
| Enhanced
security for automation deployments through virtual
desktop (Service Cloud Case ID: 02152805) Citizen Developers and Professional Developers can now deploy automations directly to a Virtual Desktop environment from the Bot editor or repository. This enhancement introduces an additional security layer by allowing private automations to run within a virtual desktop session. Virtual Desktop environments maintain a distinct security context—similar to the main desktop—enabling more fine-grained access control, especially when interacting with Office applications or sensitive resources. |
| Enhanced
WLM bot testing with queue for Bot Creators (Service Cloud case ID:
02180623, 02002261) Bot Creators can now test their private Workload Management (WLM) automations using actual queue items directly from the Bot editor, in addition to dummy data. This enhancement enables developers to read from the queue directly without moving automations to a public workspace, improving the accuracy and reliability of automation logic early in the development cycle. With this update, Bot Creator license devices are supported for the Run with queue option in development environments—removing the earlier dependency on unattended Bot Runners. This streamlines and speeds up the bot creation, testing, and troubleshooting with WLM queues. validate-WLM-automation-developer-device.html | test-and-run-wlm-automation-from-.html |
|
Support for custom certificate configuration in OpenSearch (Linux Installer) Automation 360 now lets you use your own certificates for OpenSearch cluster communication in new Linux-based On-Premises installations. This improves security and compliance by allowing you to use your own trusted certificates. Note: Automation 360 requires a new installation to use
this feature. This capability is not supported in updates of
existing installations.
|
|
Group Managed Service Account option for service credentials configuration For Automation 360 On-Premises, we have added a new Use a Group Managed Service Account (GMSA) option to the Service Credentials screen in the installation setup wizard:
When you select this option, you need to enter the correct Domain/Username and matching Password. This update is helpful when you want to use a GMSA instead of a regular service account. It makes setting up credentials easier during Control Room installation and follows IT rules that require using GMSAs. |
|
File stream support in Connector Builder Connector Builder now supports file streaming, enabling you to create custom packages for file-based operations, that you can use in API Tasks. File streaming allows the packages to handle files directly from the data source thus eliminating the need to download and upload the files with individual actions. This capability also enables you to move files between different cloud storage locations without downloading and uploading them. |
| APIs and integrations |
|---|
|
Automations API - Activate and Deactivate API
endpoints Documentation is now available for the Activate and Deactivate API endpoints for schedule automations in Swagger and the documentation portal. |
|
BotInsight API - Get Bot Run Data endpoint The
New format:
Old format:
Data from bot runs executed before this release will continue to display the older timestamp format. No changes are required to existing API integrations, as the new format is backward-compatible with most standard date-time parsers. |
| macOS support |
|---|
|
Web triggers on macOS Web triggers are now available on macOS. You can use any of the out-of-box web triggers to trigger automation that you create macOS platform, when an event occurs in the connected SaaS application. Web triggers provide real-time responses and eliminate the need for manual intervention to start automations. This feature is available on both AWS and Google Cloud Platform deployments. |
| Support
for device registration on Cloud using
Safari Starting from this release, you can register your default macOS device using the Safari browser for Cloud deployment. The safariagent.app is bundled along with the Bot Agent version available with this release that enables in registering your macOS device on the Control Room. |
What's changed
| Control Room, devices, and Bot Agent |
|---|
| Enhanced Form element
behavior Starting with this release, there is a change
in how data is handled for forms containing the following
elements when used in process automation:
In both form tasks and approval tasks, you can configure list of values with default options for the following form elements: Checkbox Group, Multi-select Dropdown, Radio Button Group, and Dropdown. For these elements, if the check box is not selected, the predefined options configured in the form will be used at runtime. However, if the check box is selected, you can choose either a List or a Variable to provide your custom options and specify the values to be selected. |
| Username format enhancement
in Microsoft Entra ID in Windows 11 operating
system Microsoft Entra ID (formerly known as Azure Active Directory or Azure AD) is a directory service hosted in Microsoft cloud that stores user identities, groups, applications, and access policies. It securely handles authentication and authorization across cloud and on-premises environments. Starting from this release, various username formats are now supported for auto-login with Microsoft Entra ID in Windows 11 operating system. |
|
Product and license category name update We are changing the names of our product and license associated from Conversation AI to Automation Co-Pilot. This is part of our branding efforts to make our product identity clearer and consistent across all user interfaces and communications. You will see these changes on the following pages:
|
|
Granular process and AI Agent information through monitoring dashboard The monitoring dashboard in Automation Command Center (ACC)
now offers enhanced real-time visibility into both process
execution and AI Agent activity across all
operational states—Running,
Waiting,
Completed, and
Failed. This enhancement enables
you to view:
|
| Performance
optimization for cloned bots and device
acquisition time (Service Cloud case ID: 02128957) The
With this enhancement:
|
Feature deprecation
| Process Composer former
(legacy) editor deprecated When you create a new process automation or open an existing one, it opens in the new Process editor by default now. The former (legacy) editor is discontinued and will no longer be available from Automation 360 v.38. Upcoming feature deprecations | Deprecation of Process Composer legacy editor |
Fixes
| Fixed an issue
where you create an automation using
action, select manual Input option, and add a
long line of text. Now, when you use the scroll bar to move to
the extreme right, you will see that characters are no longer
getting trimmed. Service Cloud Case ID: 02198917 |
| You can now create a Task Bot and set up a variable, such as a String or a Dictionary, with a hyphen (-) while selecting the Input or Output check boxes. Then, proceed to create a process and add the Task Bot, inserting the variable into the Task name field of the Task Bot. Save and close the process. Now, when you reopen it, update any relevant information, such as the process title, save it again, and then close the process. You will no longer encounter any errors after you save the process. |
| When you start a new process with a form and use Create variable to create a Credential data type, the Credential data type will now be available in the data type list. |
| You no longer
encounter any issues with variable mapping in the Process editor. Previously, when you attempted
to map a table variable with a text field in the Expression
Builder, it was unable to map the row index of a table
element to a variable. Note: When you
update from Automation 360 v.37 to v.38,
and you edit a process to map variables using a nested
expression, and if the variable has an incorrect syntax,
it will not work. You must remap the variable
expression. Service Cloud Case ID: 02231643 |
|
In the Process editor, when you run a process, validation errors are displayed for any missing dependencies, highlighting the exact locations of each error within the process. However, the error messages are presented in JSON format. |
| When you use the
expression builder on the Bot editor to create a
List type variable and add the expression List:listSize
– Size, it now converts a list size number to a
string correctly. Previously, type casting from a number for list size to a string generated an invalid property error. Service Cloud Case ID: 02208779 |
|
When you use the Browser option in packages to refresh the windows you no longer encounter this error message: Unable to download the bot or the dependencies to the device; Error code: download.error. |
|
The automation compatibility tags are now calculated correctly whether you update and check in an automation that contains earlier package versions or update the packages using the bulk package update process. |
| After updating to
this release, the automation compilation failures that were
caused due to missing metadata no longer occur and the
automation deployments now compile successfully without
requiring manual database intervention. Service Cloud Case ID: 02228852 |
| After updating to
this release, if you change any settings or configurations on
the default device, Authorization Plugin in macOS
no longer causes issues in the security prompt such as
navigating away from the login screen when you try to enter the
credentials. Service Cloud Case ID: 02208796 |
| After updating
the Bot Agent to the version
included in this release, automations that previously failed due
to timing issue caused between completion and session expiry
will now complete successfully. Service Cloud Case ID: 02208934 |
| After
updating to this release, the column customizations that were
made to the table using the option are retained even if you navigate to any
other page such as Audit
log. Service Cloud Case ID: 02204502 |
| Name of
the registered device is now displayed correctly in the
In Progress page during automation
execution and in the Historical and
Audit log pages after the deployment
completes successfully. Service Cloud Case ID: 02190590, 02195263 |
| After updating to
this release, when an automation is deployed on a multi-user
device, if a new version of this automation is checked in and
deployed to the same device by another user, the first execution
no longer fails. Service Cloud Case ID: 02162102, 02186698 |
| If a Git
repository is configured in the Control Room, any changes that you make to the
directory name (including uppercase or lowercase characters) are
now recorded correctly in both the database and repository
filesystems. Service Cloud Case ID: 02174055 |
| After updating to this release, if you assign a production label to an earlier version of an automation that has more than two versions before you export it, the metadata linked to the production version is now exported correctly. |
| After updating to
this release, when you use the Compare
versions option, the labels of the automation
dependencies, including any duplicate entries that were removed
are now displayed correctly. Service Cloud Case ID: 02215103 |
| Multiple pop up screens to unlock the device are no longer displayed after automation runs even when a macOS based automation is scheduled to repeat execution on an unattended Bot Runner device across various time intervals. |
Fix for a
potential security vulnerability where non-privileged users
could access and download Recorder's metadata images via the
v1/repository/0/<fileID>/download?version=latest
endpoint. Previously, users with even basic roles could bypass
intended Role-Based Access controls (RBAC), leading to
unauthorized access and potential data enumeration of these
images. This has been resolved by enforcing proper permissions
on metadata image files, ensuring that repository operations now
correctly restrict access based on user privileges.Service Cloud Case ID: 02182733 |
Fix for an issue where the
v2/repository/file/list API now provides
accurate paging information. Previously, this API was providing
incorrect paging results, specifically misleading
total and totalFilter
values in the response, which made it difficult to accurately
paginate through large sets of files.Service Cloud Case ID: 02177927 |
When
TriggerListener.exe stops suddenly (like
during a log off, shutdown, or forced stop), a Send email
event used to be recorded in the Audit Log under
Email Notifications with a failure message:
Unable to connect to SMTP server. This made
customers think there was a problem with the SMTP setup, even
though the error was actually due to the service stopping
suddenly.Now, no audit or historical entries are made
when Service Cloud Case ID: 02171158, 02176125 |
Users had problems when exporting
filtered audit logs in bulk, especially when the filter included
Template download events. The export
operation did not work when the Auto Download Templates
Completed audit event was part of a bulk export
using custom filters.The event definition for Service Cloud Case ID: 02183647, 02186750, 02187179, 02188020, 02195898 |
| Fixed an issue where an error screen appears when you create, open, or edit a custom connector on the Packages page. |
| Fixed an
issue where API Tasks and Task Bots
failed to execute and returned the following error message:
No compatible target found in automation.
This failure occurred because the system did not skip validation
of disabled commands. Service Cloud Case ID: 02218278, 02221856 |
| With Remote
Git integration configured, authentication is now processed
quickly, ensuring that Task Bots are checked out
successfully without delays. Previously, in such cases, authentication could take an extended time, blocking subsequent check-in or check-out requests. Service Cloud Case ID: 02206735, 02209940 |
|
Fixed an issue where the screen blanks out and the form composer closes when you delete a API Task from the Form actions option in the Form rules tab. |
|
Fixed a security vulnerability that allowed you to access device information through the API, even if Control Room permissions restricted them from viewing that information in the UI. Your permissions now align between the Control Room UI and the API, so you can only retrieve the device information you are authorized to view. Service Cloud Case ID:02218875 |
| You edit a complex process in the new process editor and add two horizontal swimlanes. You can now move an element from the first swimlane to the second without any delay. |
| When you add an
Else if, the
Else node is now added along with the
Else if node. Previously, you could add an Else node independently on the editor through the Quick add option. |
| You can now
complete a request successfully for a process that has a filter
with an input form. Previously, due to an issue, the Filter task was not able to provide the filtered data. |
| When you create a process with a bot, form, or API task, you can now edit the form, bot, or API link and update the existing fields. |
| The List
package now updates successfully, and the
Any variable returns the expected
type without requiring a manual workaround. Previously, while performing a bulk package update for the List package, the Any variable became undefined. As a result, you had to apply a workaround (check out, edit a variable, save, and check in) to restore functionality. |
| An
issue where the Activity page and the
dashboard displayed inconsistent data is now resolved. The
number of in-progress automations on the Activity page now
matches the Running count on the
dashboard. Additionally, the Device
utilization details tab on the dashboard now
displays accurate data. Previously, the dashboard showed incorrect information for both automations and devices. Service Cloud Case ID: 02212344, 02219747, 02220167, 02188864 |
| Long XML files are now
fully scrollable in the Preview,
Dual, and Edit
modes, restoring expected functionality. Previously, long XML files were not scrollable in Preview and Dual modes, preventing users from accessing the complete file contents and copying values directly. Service Cloud Case ID: 02214147 |
| The bot
import workflow has now been optimized to remove blocking
behavior, ensuring smoother and faster imports. Previously, users experienced slowness during bot imports because the import process and the check-in operation were blocking each other, which led to performance delays. Service Cloud Case ID: 02206879, 02208434 |
| Fixed an issue where users could not import Postman collection or OpenAPI YAML files when they created custom packages using Connector Builder. Previously, the system displayed an invalid endpoint error if the Postman collection or OpenAPI files contained path variables in ({param}) or {{}} format. |
| When you downgrade packages (such as Database
or Excel advanced) with defined session names,
the original session name configurations are now preserved,
preventing bot run failures. Package downgrade operations also complete successfully without
errors. Previously, during package downgrade, session names were incorrectly reset to Default, which caused bot runs to fail. Service Cloud Case ID: 02184742 |
| You can now add
or remove more than 100 roles from a folder and perform sync
operations with more than 100 roles. Previously, the APIs retrieved only the first 100 roles, which caused add, remove, and sync operations to fail when the role count exceeded 100. |
| You can now
switch the Credential Vault connection mode from Manual to
Express when using a valid master key. Previously, the configuration could not be saved when switching modes with the same master key used during Control Room restarts, even if the user had full repository permissions and the server had been restarted. Service Cloud Case ID: 02202578 |
| You no longer
encounter intermittent errors when fetching or updating the
access token for Control Room–managed OAuth2
connections. Previously, when running automations that used the method action with Control Room–managed OAuth2 authentication, the access token update credential event would occasionally fail. This resulted in automation failures after several hundred executions. Service Cloud Case ID: 02188941 |
|
You can now log in to the Control Room configured with SAML authentication without errors. SAML settings are retained in the configuration table even when validated multiple times before saving, ensuring a successful login. Previously, if SAML settings were validated multiple times, the second validation attempt would remove SAML entries from the configuration table due to SAML assertion. Service Cloud Case ID: 02177248 |
| The Automation Co-Pilot Business User naming now displays
correctly across all licensing pages and license drill-down
pages. Previously, there was a mismatch between the license page and the license drill-down page. Service Cloud Case ID: 02226851 |
| Users added to
the Control Room through Active
Directory sync can now log in successfully when
email verification is disabled. Previously, when SMTP was configured, users were incorrectly flagged as unverified and prompted to re-verify their email address, even if the Require Verification option was disabled in email settings. Service Cloud Case ID: 02225069 |
| Users can now log
in successfully to the Control Room in the Automation 360
Cloud Sandbox environment when SAML
authentication with automatic user account provisioning is
enabled. Previously, when the Control Room was hosted on a Cockroach database, users with usernames containing uppercase or mixed-case characters were unable to log in and encountered errors. Service Cloud Case ID: 02242178 |
| The Recover button is now disabled when no items are selected even after the first recovery. |
| When you run a process with a record input variable, the initial step after selection of check box now shows the default value for record input variables. |
| When you create a
process in the process editor, the
ProcessRequest is now excluded from
the drop-down list, showing only valid nodes in the
Go to element. Previously, ProcessRequest appeared in the drop-down, despite not being a valid option. |
| When you create a form with the Date and Formula element and enter a dot after a date element name in the formula, such as $Date-Date0.$, the form no longer crashes. Also, it now displays an error message. |
Limitations
| When you use a local file path to update the Bot Agent version, the update process validates the current status of the signing certificate instead of relying on the original signature validity. If the certificate has expired, the local file is rejected, and the Bot Agent downloads the installer from the Control Room instead. Although the update completes successfully, it might result in a higher bandwidth usage. |
| When you create a custom connector using Connector Builder, you cannot save the connector if you set the Authentication action as Custom type and select the Stream file(s) during download check box. |
| Limitations from previous releases |
|---|
| If the request body of any action in the connector package contains more than 100 parameters, the publishing process fails. You can either delete the action or remove the excess parameters from the action to publish the connector package successfully. |
| API Task is a cloud-only feature. Currently, you can import API Tasks into On-Premises environments. You can view the imported API Task in the On-Premises Control Room; however, you cannot execute them as automations. |