Automation Workspace v.37 release
- 最終更新日2025/07/01
Automation Workspace v.37 release
Review what's new and changed, and the fixes and limitations in Automation Workspace for the v.37 release.
What's new
Control Room, devices, and Bot Agent |
---|
Update
to Automation 360 from previous four
releases
Starting from this release, you can update Automation 360 directly to the latest version from the previous four releases (that is, from n−4 releases, where n refers to the latest release). As long as your current Automation 360 version is within the last four releases, you can update to the latest version without needing to go through the intermediate updates. This streamlines the update process, allowing for quicker adoption of new features and improvements. |
Support
for Red Hat Enterprise Linux 9.5 (Service Cloud Case
ID: 02114364) Red Hat Enterprise Linux (RHEL) 9.5 introduces enhancements to security and automation in order to support modern workloads across hybrid cloud environments. These improvements are aimed at better supporting modern workloads, particularly in hybrid cloud environments, where resources are spread across infrastructures. Starting from this release, you can deploy Automation 360 on Red Hat Enterprise Linux 9.5 version. |
Enhanced
workload management through parallel queue
processing
Parallel queue processing enables WLM to simultaneously process multiple queues across devices, enhancing the speed and efficiency of queue processing. By optimizing the use of devices, parallel queue processing ensures that workloads are distributed evenly, leading to improved system performance and reduced wait times for queued tasks. |
Improved
reporting through grouping of automation run hours
The Automations dashboard in Automation Command Center (ACC) provides detailed grouping of automation run hours. With the detailed grouping, you can now monitor automation run hours metrics grouped by various entities; thus realizing your most valuable automations, users and devices. It enables you to view automation run hours over a specified time range, with the ability to group by specific entities and view the data in a histogram. |
Support of Simplified
Chinese language in Control Room
(Service
Cloud Case ID: 02171136, 02170860, 02176637, 02190266) Automation 360 now provides localization support for Simplified Chinese for its user interface (UI), automation, and documentation. To access it, navigate to the Control Room interface, click the language icon (globe icon) next to the user profile setting (My settings), and select the Simplified Chinese language from the list. |
Import of
pre-built templates on a predefined
schedule
As a Control Room administrator, if you have enabled the settings for auto-importing of pre-built templates in the Control Room, the pre-built templates from the Bot Store will be auto-downloaded on the first of every month at midnight local time. Previously, these predefined templates were imported on a quarterly basis, but this new monthly schedule enhances the availability and accessibility of templates, ensuring that you have the latest resources. |
Support of Event
triggers with auto login using external key-vaults
(Service Cloud Case ID: 02172540, 02192012) Event triggers now support auto login using external key vaults. Whether you are an attended, unattended, or bot developer user, device credentials are set through external vaults (such as CyberArk, HashiCorp, or AWS) in the Control Room. On the bot run, the auto-login credentials are retrieved seamlessly from external key vaults. |
Trigger count on Event
triggers page for Citizen Developers
Citizen Developers can view the number of triggers that they configure for their automation in the Private tab on the Event triggers page. Citizen Developers can also monitor and track the triggers from this page. |
Web
triggers enhancements
The Jira,
Microsoft 365 Outlook, and ServiceNow web triggers support
server-side filters.
|
Connector Builder enhancements
Connector Builder now supports importing API definitions with Open API specification version 3.x Connector Builder also supports the inclusion of special characters . and @ in request header keys and request parameter keys. You can now import actions with these special characters when you create a connector using the Import API definition option. |
Support for
Windows authentication using gMSA for database
connectivity
We now support gMSA(Group Managed Service Accounts) for Windows authentication when gMSA was selected to run the CR services to automate password management. This support reduces manual effort and enhances security by handling password rotation and eliminating manual entry. |
Introducing
automation credits for simplified license
management
Automation Credits license information on the Licenses page ( ) allows you to use a single credit type for any license, simplifying management and tracking. |
APIs and integrations |
---|
Workload
Management (WLM) APIs
|
What's changed
Control Room, devices, and Bot Agent |
---|
Optimizing
automation deployments across devices in a device pool
(Service Cloud Case ID: 01961764) Optimize automation deployments across devices in a device pool by managing and distributing automation tasks to ensure efficient use of resources, improved performance, and reliability. When you select a device pool that contains multi-user devices that have available sessions, the automation deployments are now managed correctly among these devices to ensure that deployment load is spread evenly across the devices in the device pool. |
Automatic
deletion of metadata for the updated automations and
packages older than 30 days
Starting from this release, package update details specific to an automation available in the Bot updates table that are older than 30 days will be deleted automatically. This feature is designed to maintain an organized and efficient automation environment. This reduction in data volume can lead to faster access times and improved overall performance of the automation environment. With less outdated metadata to manage, system administrators can focus on more important tasks, simplifying the maintenance and management of the automation environment. |
Alert
message displayed when run-as users associated with schedule
activity is deactivated
Starting from this release, if
any of the associated run-as users of scheduled activity is
deactivated, an alert is displayed in the
Scheduled activities page. The
alert message provides immediate feedback that a run-as
user, who is crucial for executing scheduled activities, has
been deactivated. This ensures that administrators are
promptly informed of any potential disruptions in automation
processes. This alert message plays a crucial role in
maintaining the reliability and security of automation
schedules by ensuring that any changes in user status are
quickly addressed.
Note: The alert is
no longer displayed when the deactivated run-as users
are activated.
|
Support for
master key rotation in Credential Vault
(Service Cloud Case ID: 00800093, 02140852) Key management operations for AWS key management service and Google Cloud Platform now includes enabling of master key rotation, thereby enhancing compliance and security. |
Support
for Active Directory role mapping with users
or groups from different domains (Service Cloud Case ID:
02131291) Control Room now supports group mapping with users or groups from different Active Directory domains on On-Premises deployments. |
Expired
license behavior in license group management
The Create group and Edit group ( ) options show only active and future active GUIDs for license group addition, with icons indicating expired and active GUIDs for easy identification. |
User
experience enhancements for license grouping
The user interface text on the page has been updated for improved clarity. |
Update to
log in error message
The login error message has been updated to inform the user to log in again to connect to the Control Room if there are already 5 concurrent sessions active and the user attempts to log into a 6th session. |
New audit
events added
The following new audit event types are
added when you create, edit or delete a role with
runas user permissions:
|
File size
limit for Control Room objects
The Control Room objects, such as bots, processes, templates, forms, and AI Skills, now have a size limit of 50 MB. Also, the maximum default size for all repository bots is now 50 MB. This improvement helps prevent out-of-memory (OOM) and Control Room shutdown issues caused by large file sizes. For example, when you perform a bulk package update, the bot size limit of 50 MB prevents OOM issues in the Control Room. |
Revised Workload permissions for better user
experience
With revised Workload Management (WLM) APIs, Workload permissions are enhanced to
use minimal permissions to manage queues and work items.
This enhancement includes:
|
Generative AI
Package: Global Session Support
The Generative AI Package has been updated to include support for Global Session. This allows for the propagation of session context from a parent bot to its invoked children bots when using Generative AI actions, improving state management across complex automations. |
Fixes
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 on the Bot editor screen is no longer displayed and allows you to develop the automations. |
When you use the
If action with multiple conditions,
including a Recorder condition with
secure recording enabled and Recorder preview
image option is enabled, the images will be
temporarily saved to the repository with an expiration time
stamp of one hour after the image is saved. Service Cloud Case ID: 02188888 |
When you do a bulk package update of bots, the bot size is now limited to 50MB. This helps
prevent Out of Memory (OOM) issues in the Automation 360
Control Room. Previously, in such cases, for example, during Database package update, JSON file size increased from 15MB to 260MB causing OOM issue and Control Room went down for some time. Note:
Service Cloud Case ID: 02196714 |
The captured images
are no longer stored in file system when checked in as part of
secure recording. Previously, when you were using secure recording feature, the captured images were still persisted in the repository which led to a security issue. |
Device
pool owner can now edit a device pool and save the changes
successfully even if any one of the other owners of this device
pool is disabled. Service Cloud Case ID: 02201801 |
When you use the
Delete unused versions feature, it no
longer deletes packages that are used by
automations in the public repository. Service Cloud Case ID: 02176850, 02204971 |
When you navigate to
public repository with sub-folder more than 1000 and open any
Task Bot or configuration file, it now
takes less time to expand and load folder and does not show any
error message. As a result, you can view the folder hierarchy
correctly in the left panel on the Public
or Private workspace tab. Service Cloud Case ID: 02149276, 02210524 |
On the Event triggers page, when you add an API Task with web triggers, the Choose a user modal displays only the users with run permission for the folder where you check in the API Task. |
When
you have a custom role with one or more run-as users and if some
or all the selected run as users are deleted, the Run
as selected count now reflects correctly in the
custom role. Additionally, when you add or update run-as users
for a role, and if the selected run as users are either disabled
or deleted, you no longer encounter an error message when
creating or editing a role. Service Cloud Case ID: 02180578, 02197309, 02210550 |
Remove icon is easy to locate and use. Previously users found it difficult to locate the icon for removing the attribute, and it appeared that there was no option to remove the credential attribute ( ). |
Only a user with
Manage all queues permission or the
owner of the queue can now delete the queue. Previously, any user with an Export or Import queues permissions and a queue participant or consumer was able to delete a queue. Service Cloud Case ID: 02213384 |
Limitations
While updating Automation 360 to this release, if the filepath for
uploading the OpenSearch certificate.zip has a
semicolon (;), the installation will not work. Workaround: Ensure that you do not have a semicolon (;) in the filepath that is used to upload the OpenSearch certificate.zip file. |
Limitations from previous releases |
---|
When you check-in a bot to the folder with the name System, the bot version is not displayed correctly. |
When you perform bulk
package update for List
package, an Any
variable that is used as List, returns
the Undefined
type.
Workaround
|