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

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

What's new


Control Room, devices, and Bot Agent
New permission for custom dashboards A new permission, Publish custom dashboards, has been added to the Control Room. This allows users to publish custom dashboards and make them available to all. Feature permissions for a role
Add labels to connector lines in Process editor Process editor now supports adding a text label to any connector line between two nodes to describe the intent of that transition. This makes complex process flows easier to review and maintain without requiring you to open each node to understand the transition between steps. Line titles for connector lines in Process editor
Improved Go to connection visualization We enhanced the Go to connection visualization to improve process readability and the overall process‑building experience. The process editor now displays a clear, explicit visual connector, a green line between each Go to node and its mapped target node on the process canvas. This enhanced visual indicator makes it easier for developers to trace logical jumps, reduce design errors, and improve the maintainability of complex process models. Add Go to node to a process automation
Enhanced mechanism for process failure recovery Process execution now provides greater control over failure recovery. You can configure a process to automatically suspend when a task fails, allowing authorized users to review the failure and retry or skip the failed task instead of restarting the entire process from the beginning. When retrying, users can correct supported input variable values before resuming execution. This enhancement includes the following changes: You can select Suspend process execution on task failure to automatically suspend a process when a task fails. Users with Manage activity permission can then retry or skip the failed task to recover the process. This setting applies only to new process instances and does not affect instances that are already running. When you select Retry for a failed node, the current input values for that node are displayed. You can correct supported variable values before retrying, and the updated values are validated before the retry. Read-only and process-level variables cannot be modified. From the process instance details, you can select a failed node, add a retry comment, and resume execution from that node instead of restarting the process. The process diagram and status update as execution continues, and the retry is recorded in Action and Audit history. Retry a failed process node \| Recover a suspended process
Intermediate triggers in Process editor Intermediate triggers in the Process editor allow dynamic pausing and resuming of processes for adaptive, long-running orchestration. These triggers listen for the configured events and pause the execution until the preconfigured message name and the associated correlation key are received. Once the process receives this message-key combination, the execution resumes and proceeds as per the configuration.

What's changed


Control Room, devices, and Bot Agent
Device modification details standardized( Service Cloud Case ID: 02220750, 2326658) After updating to this release, the information of a device in the Last modified column in Manage > Devices is now updated to System if the associated user account was deleted or disabled, system-driven events such as starting or stopping the Bot Agent service, device updates, device disconnects, or reconciliation operations occur. About Windows devices
Automated retry of automation recording in unattended mode (Service Cloud Case ID: 02194806, 02195345) Starting from this release, Bot Agent retries the recording attempt continuously throughout the automation execution if device's desktop is not available. However, as soon as the desktop becomes available (at any point during execution), recording starts automatically from that moment without manual intervention. Record automation execution
Unified AI credit consumption AI Evaluations credit consumption logic for AI Skills and AI Agents has been updated in this release to provide consistent tracking by combining input and output tokens and converting them to AI credits. Licensing model for AI Evaluations
External vault autologin UI management Automation 360 now supports managing autologin credential mappings for individual users directly within the Control Room interface. You can add, update, or remove a mapping for a specific user using inline row-level editing, without needing to perform a CSV upload. For bulk updates or as an alternative for single-user changes, the existing CSV upload method continues to be supported. Custom secrets naming convention
OAuth Dynamic Client Registration Automation 360 now supports OAuth Dynamic Client Registration (DCR), enabling authorized users to register automatically with Automation 360 server without requiring manual client setup in Control Room. OAuth Dynamic Client Registration
Export automations and files from a private workspace Automation developers can now export automations and files directly from their Private workspace. This enhancement enables developers to transfer their work without first checking it in to the Public workspace, simplifying collaboration and migration scenarios. Users with the required export permissions can export supported automation assets, including bots, API Tasks, processes, AI Skills, AI Agents, Templates, and files. The export workflow also supports selecting dependencies and packages, and the exported file can be imported into either a Private or Public workspace.
Role-based visibility for Bot Insight in Control Room Access to Bot Insight in Control Room is now aligned with the user’s assigned permissions, roles, and licenses. The Insights tab under Activity and the Bot Insight link under Quick links are displayed only when the user has the applicable access. The enhancement includes the following navigation changes: If the user has required Automation Command Center (ACC) and Bot Insight permission, Insights opens the Access dashboard. The Bot Insight link is available in the upper-right corner of the Access dashboard. If the user does not have ACC permission but has Bot Insight permission, the Bot Insight link appears directly in the left navigation bar. If the user has ACC permission but does not have Bot Insight permission, Insights opens the ACC dashboard, but the Bot Insight link is not displayed in the upper-right corner. If the user does not have either ACC or Bot Insight permission, the user has no access to Insights.
Enforcement of global RDP session timeout by administrators Control Room administrators can now enforce a global RDP session timeout that takes precedence over all other RDP-related timeout settings configured on user devices, including the legal disclaimer screen timeout. This ensures consistent session timeout behavior across the environment. Configure RDP-based deployment for multi-user devices
Discovery Bot Role Removal As part of the Discovery Bot end-of-life process, Automation Anywhere has removed Discovery Bot roles from existing Automation 360 user assignments. Users previously assigned only a Discovery Bot role might need a new role assignment to maintain workspace access.

Fixes


You can now remove the description of a task automation from the Bot editor > File properties page. Previously, when you cleared the Description field and clicked Update, the empty value was ignored and the previously saved description remained. Service Cloud Case ID: 02308740
Fixed security vulnerability issues. For more information, click the A360 Package Releases > <month>-<year>-Periodic Package Release > Security & Compliance folder and download the file with the corresponding package name at A people Download page (Login required): A-People Downloads page (Login required). Service Cloud Case ID: 02328235
Fixed security vulnerability issues. For more information, click the A360 Package Releases > <month>-<year>-Periodic Package Release > Security & Compliance folder and download the file with the corresponding package name at A people Download page (Login required): A-People Downloads page (Login required). Service Cloud Case ID: 02328235
Fixed an issue in Connector Builder where map attribute values did not appear automatically when importing JSON to define request or response payload in an action. Now, Connector Builder automatically displays the map attribute values. Service Cloud Case ID: 02308874, 02337027
After updating to this release, the Daylight Saving Time (DST) spring-forward will be changed and the daily schedules no longer runs an hour earlier than the intended time. Service Cloud Case ID: 02300924, 02304504
When you update to this release, filtering of Run-as users by Username or Platform in the Schedules > Run-as tab now returns the correct results, and the displayed record count also matches the actual filtered results. Service Cloud Case ID: 02308636
After updating to this release, when you re-enable a hidden column after rearranging or resizing columns on the Scheduled activities page, that column is now displayed correctly. Service Cloud Case ID: 02309834
A license group is no longer mapped to its entitlements incorrectly that caused validation failures when editing and saving an OAuth application on the Settings > OAuth tab. Service Cloud Case ID: 02308641
After updating to this release, the email notifications are now displayed correctly in the user's configured default language, ensuring a consistent and localized user experience. Service Cloud Case ID: 02293004, 02302245
Starting from this release, when you search an automation or activity name in the Historical tab, correct results are now displayed even if the search term contains an underscore (_). Service Cloud Case ID: 02332919
The API-based updates to bots in the public workspace are now restricted, protecting bots from direct content changes outside the supported interface. Previously, users with upload permission could directly modify bot content in the public workspace through a migration API without creating a version history entry. Service Cloud Case ID: 02290962
Fixed an issue where Split (with Branch Start and Branch Exit) and Merge nodes appeared in the Elements panel for users without an Enterprise Platform license. Additionally, importing a process that contains these nodes now displays an error message.
Cut and paste operations now preserve the process structure and all connections correctly. Previously,after using cut and paste to move elements in the Process editor, the process structure became incomplete and connections between elements were lost.
Fixed an issue where selecting check box in the End node without adding input data did not display a validation error at runtime.
Fixed an issue where consecutive Human tasks with similar form structures could display incorrect or mixed label text when navigating between tasks or refreshing the process. Each Human task form now consistently renders its correct label, regardless of navigation or refresh actions.
Each automation now uses the work item template associated with its selected bot version or label, allowing different queue schemas to run in parallel. Previously, when you created multiple WLM automations using different versions of the same bot, the automations used the work item template associated with the latest bot version instead of the template associated with the selected label. Service Cloud Case ID: 02304343
A new Created at column is now available in the work items list. You can sort the Created at column to display work items based on their creation date. Sorting by Work item ID is no longer available. Previously, sorting work items by Work item ID did not display the work items in the expected sequence. Service Cloud Case ID: 02328104
Invalid saved sorting preferences are now handled appropriately, allowing users to access and view bots in their private workspace. Previously, some users could not view bots in their private workspace when their saved sorting preferences contained an attribute that was no longer supported and `Unable to filter the results because of invalid input` error was shown. Service Cloud Case ID: 02313845
When you edit text or JSON files in the Control Room, multibyte characters are now displayed correctly as you enter them. Previously, when you edited text or JSON files in the Control Room, entering multibyte characters could cause characters to be duplicated or displayed incorrectly. Service Cloud Case ID: 02316086
Completed work items are now automatically purged from the queue according to the configured Auto purge retention period. Previously, in Workload Management, completed work items were not automatically purged from a queue based on the configured Auto purge retention period, even when the setting was enabled. Service Cloud Case ID: 02322609
Command scope lines now display correctly without overlapping other commands. Previously, in the bot editor, command scope lines could overlap other commands, particularly when expanding or collapsing scoped commands such as `Error Handling`. Service Cloud Case ID: 02313831, 02304699, 02316676
Date elements now show the date value correctly without the additional character. Previously, date elements in forms could incorrectly show the character b as part of the date value when users selected the bM/bD/YYYY, bD/bM/YYYY, or YYYY/bM/bD date format.
The Submit button in a Form task page now remains fully visible and properly aligned after you refresh the page. Previously, refreshing the Form task page could shift the button layout and partially hide the Submit button.
The Process editor now displays the appropriate icons for Task, Conditional, and Event elements on the process designer canvas. Previously, only the element names appeared and the corresponding icons were missing.
The Update All option now correctly updates package versions for all applicable bots without stopping after 1,000 bots. Previously, in Automation 360 On-Premises, when you used Bot update > Update package version > Update all to update package versions, the update process could stop after processing 1,000 bots when the environment contained more than 1,000 bots. Service Cloud Case ID: 02293365, 02341350, 02334434
Fixed an issue where some properties such as Current state ,Current automation, Last modified were not appearing in the Activity details panel for processes in the In progress and Historical activity views.

Limitations


When you restore a Git branch after partitioning and deleting a folder from the Public workspace, the restore operation becomes blocked if a folder with the same name exists at the same hierarchy level in the Public workspace. The Public tab might become unresponsive, preventing you from completing or canceling the restore operation. Workaround: Before initiating the Git restore operation, rename or delete the folder with the conflicting name from the Public workspace.
When a process contains a GoTo node that jumps to a Filter node, the process fails to compile and does not run. This issue occurs with the V2 process execution engine.
When you use Bulk Package Update to update multiple bots that contain a large number of package dependencies, some bots might fail with a `General failure` error because the compilation process exceeds the available memory. Workaround:: Instead of selecting all the packages at a time, update the bots by selecting small batches of packages at a time. If the issue persists, reduce the batch size further or update bots with the largest number of package dependencies individually. Service Cloud Case IDs: 02280521, 02283364, 02287121, 02328640, 02335501, 02337170
When you create an automation using the Interactive Forms package and run it, the Zoom in, Zoom out, and Fit functionality does not work from the second form document onward. Workaround: Use the mouse scroll to zoom in and out on the document.