Automation Workspace v.29 release

Download as PDF

Feedback

HomeAutomation 360Release NotesAutomation 360 Release NotesPrevious Automation 360 Release NotesAutomation 360 v.29 Release NotesAutomation Workspace v.29 release

Table of Contents

Automation Workspace v.29 release

Download as PDF

Feedback

Updated: 2024/05/27

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

Important: Starting from this release, we have moved information about updates in each package (such as what's new, changed, fixes, and limitations) to package-specific pages. You can access these pages by navigating to Package updates overview > <package-name> releases.

For a consolidated list of packages updated in this release, see Packages updated in v.29.

What's new

Search:


Control Room, devices, and Bot Agent

Introducing Help Center: In-app help used to search for automation information Help Center is a centralized location that contains all the information developers need to develop automations. When you log in to the Control Room, the Help Center will show suggested topics related to the Home and Bot editor page in the widget. Developers can leverage the suggested topics or search for specific packages, actions, or information they need help with. Additionally, the documentation link from contextual help loads the content directly within the Help Center. This feature eliminates the developer from having to switch back and forth between the Bot editor and the documentation portal providing a distraction-free experience. In-product user assistance
Enhancement to Bot Agent installer (Service Cloud case ID: 01857405) We have enhanced the Bot Agent installer by including new .exe files for the Bot launcher, Node manager, Triggers, and Child session launchers. When you create and run a bot using actions from the File, Folder, or Excel advanced packages, and if your organization has configured security policies such as Document Security Solution (NASCA) DRM (Digital Rights Management), the files will be encrypted and secured by the security program. The following changes occur in the installer when you: Install the Bot Agent, java.exe will be replaced by NodeManager.exe. Run a bot, javaw.exe will be replaced by BotLauncher.exe. Configure a trigger, the trigger will be activated with TriggerListener.exe instead of javaw.exe. Run a bot with Automation Co-Pilot (integrations), javaw.exe will be replaced with ChildSessionLauncher.exe. Note: If your bots or scripts use java.exe or javaw.exe in the Bot Agent installer folder, we recommend that you modify your bots or scripts using the new .exe files. Ensure that the Bot Agent version installed on your system is the version that is released with Automation 360 v.29. Install Bot Agent and register device
Enhanced operational insights in Automation Command Center As an administrator, you can have a comprehensive view of the automation landscape in your homepage. The Automation Command Center (ACC) homepage combines all of the different functional areas onto a single page thereby increasing productivity efficiency. The homepage provides operational insights into automation and device statuses, license utilization, and code analysis policy compliance metrics. You can navigate to automation and device dashboards to review details for automation executions and related key performance indicators, and gain actionable insights for devices. Additionally, you can review total automation run hours, device utilization, and KPIs related to queues and work items. ACC provides the ability to navigate to specific functional areas, such as Policy management. ACC home page for administrators \| ACC home page for Pro and Citizen Developers \| Configure and assign code analysis policy
Enforce code analysis for bots check-in As an administrator, you can enforce code analysis during check-in of bots to the public workspace. You can restrict the RPA developers or Citizen Developers from checking in bots that contain code analysis violations. This is based on the permissions assigned to the developer in a custom role. When you create a custom role, you can use the following three new code analysis enforcement permissions: Enable enforcement for bot check-in Allow check-in with low severity violations Allow check-in with high severity violations All system roles only have the permission to check in bots without violations. If you only use system defined roles you must create new roles to assign the permissions to check in with violations. Code analysis enforcement
View license details (drill down) for users and Control Room instances You can view license allocation details by users and license usage across different Control Room instances. From the Licenses page, you can click a license type to view the License details page that provides the following information: View the license allocation details by users in the Control Room where you are viewing the license information. View the usage details for the license type across other Control Room instances. Manage licenses \| View license details
Notifications for invalid login attempts As a Control Room user, you are now notified for invalid login attempts. When you exceed the maximum number of allowed invalid login attempts (set by your Control Room administrator), the Control Room sends an instant email notification to your registered email address. With this instant notification, you can trace the Control Room authentication and restrict invalid access by resetting the Control Room password. Platform events
Time filter for historical activities As a Control Room user with appropriate permissions, you can use the Time filter option to search for and view specific historical activities based on time duration. Additionally, you can customize the date and time to view these activities. Time filter
Integrate HashiCorp Vault to retrieve credentials (Service Cloud case ID: 00833916, 01275490, 01762964, 01839196) Integrate HashiCorp Vault with the Control Room to retrieve credentials from the HashiCorp Vault. The credentials are securely stored and managed on the HashiCorp Vault. HashiCorp Vault integration
Automation capabilities for safe members from multiple CyberArk safes (Service Cloud case ID: 01834131) You can add multiple CyberArk safes on the Auto login settings page to enable safe members to deploy bots for unattended Bot Runners. CyberArk credential retrieval use cases
Audit log events for Active Directory default and allowed domains The following audit log events are logged for Active Directory: When a user or an existing mapping belongs to one or more domains When a user configures a domain as the default domain When a user adds a domain to the allowed domains list When a user deletes a domain from the allowed domains list Audit events list
Edit multiple devices As a Control Room administrator or a user with View and manage all devices role, you can select and edit multiple devices at the same time. Additionally, Control Room users can change Lifespan, Device type, and Log collection configuration settings across all registered devices at the same time. Edit multiple devices simultaneously
Run bot in elevated mode After updating to this release, an administrator can use the A360Elevater.exe application to run a bot in an elevated or administrative mode. This enables the Control Room users to run bots that might access any application that requires administrator credentials. Run a bot in elevated mode
Change variable values while debugging You can use the Debugger tool to edit the values of the following variable types added to the Watched variables list when you pause in debug mode during a bot run: Number String Boolean Datetime This enables you to troubleshoot and fix any bot related errors, determine the correct value to use during bot execution, and resolve the issue without stopping the debugger. Note: You cannot edit constant variables. Ensure that the Bot Agent version installed on your system is the version that was released with Automation 360 v.29. Debugging your automations \| Debugging tools
On-Premises Control Room diagnostic utility Use the On-Premises Control Room diagnostic utility to collect logs to troubleshoot any Control Room related issues. Using the Control Room diagnostics utility
Support for Microsoft Windows 11 Professional (Service Cloud Case ID: 02095408) Microsoft Windows 11 Professional version is now supported on Attended Bot Runner, Unattended Bot Runner and Bot Creator devices. Bot Agent device requirements \| Bot Runner device requirements

Search:


Building and running bots

Ability to edit workload management automations You can now edit a workload management (WLM) automation to add more run-as users and switch device pools for faster processing time. You can update the processing time, run-as users, and device pool details for queues that are currently being used. Edit workload management automations
Move bots across environments As an administrator or a user with Import bots, Export bots, and all folder level permissions, you can move bots and files, their dependencies, and packages between Control Room instances in a single flow. The promote bot feature simplifies the process by avoiding the multi-step export and import process when moving bots across different Control Room environments (Dev to UAT). Move bots across environments
Recover private repository of a deleted user (Service Cloud case ID: 01854109, 01956050) As an administrator, you can recover the bots and files created in the private repository of a deleted user (Bot Creator or Citizen Developer). You can transfer the recovered bots and files to an existing user (Bot Creator or Citizen Developer). Whenever users leave an organization, any automations they created are not lost and can be used by others in the organization. Recover bots and files
Improved searchability for bots and files in subfolders (Service Cloud case ID: 01759969, 01838997, 01858215, 01888077) You can quickly search and locate bots, files, processes, and forms within a folder and its subfolders in public and the private workspaces even if your repository contains multiple folders and subfolders. To enable this enhanced search feature, select the Include items within sub-folders check box. A new column, Folder path, is displayed which contains the location of the folder and subfolders for the bot.
View references for non-bot file dependencies (Service Cloud case ID: 01793080) You can view the references (immediate parents) for non-bot file dependencies such as: CSV, PDF, JPG, GIF, XLS, DOC, and PPT in public and private workspaces. You can use this feature to identify the bots, processes, or forms that refer to a non-bot file dependency. When you have many automations dependent on various file dependencies, it is easier to modify or delete the dependencies when you understand the impact of this change on the automations. You can efficiently check the effect of either modifying or deleting the dependency on the automations that refer to it.


APIs and integrations
New delete device API (Service Cloud case ID: 01805692, 01822981) To remove a registered device from your Control Room, use the new DELETE /v1/devices/id API. Before deleting a user, you can use this API to remove the device connected to the user, and then re-connect the device to another user. Device API

What's changed

Search:


Control Room, devices, and Bot Agent

Permissions for users to view only scheduled activities (Service Cloud case ID: 01885651, 01875383, 00788548, 00823729, 01776437, 01793759) You can use the View ALL scheduled activity option to view all the schedules in the system. You can use the View ALL scheduled activity from my Folders option to view all scheduled activities for the bot folders to which users have access. Feature permissions for a role
Audit log events for secure recording Audit log entries are logged when you configure the following Secure recording options: Enable or disable the option to preview image in the Bot editor. Change the role-based access control (RBAC) configuration on secure recording. Audit events list
Enhanced workload management capacity and performance You can process more number of queues and work items in workload management automations than previously. With this enhancement, you can improve your automation goals with optimum utilization of resources. Capacity and performance planning
Simplified notifications categories The in-app notification panel displays all the notifications as a single list without categorizing them by severity. You can use the Attention needed filter to view the high-risk and cautionary event notifications which require immediate action. Otherwise, all the notifications are visible as a simple list of events. Notifications filter
Optimized audit log entries for automated code analysis The audit event logs generated for automated background code analysis scanning are optimized to include the following two audit events when code analysis runs automatically: Automated code analysis started Automated code analysis completed The audit log entries contain consolidated information about the code analysis events. The audit entry also contains information for any change made to the existing policy.
Upload workitems to a queue API (Service Cloud Case ID: 01945087) The /queues/id/workitems/upload API was changed to the /queues/id/file API because the previous version of the API was reporting a status of N/A. You can continue to add workitems to your workload management (WLM) queue using the /queues/id/file API. Workload Management API
More visibility of variable types Now the currentValue and current Key variables of all types are displayed in the variable picker. Previously these variables had to be of string type to be visible.
Enhancement to Bot Scanner utility We have enhanced the Bot Scanner utility and it now includes the option to scan bots that contain any of the Email package actions and Triggers that use the EWS option. Note: Microsoft has deprecated EWS API for Exchange Online and has recommended that users move to Graph API. We recommend that you update the impacted bots by replacing each email-related action with the equivalent new action in the Microsoft 365 Outlook package (based on Graph API). Microsoft 365 Outlook package updates \| Microsoft 365 Outlook package Scan bots for Basic authentication
Notification on package update in On-Premises Control Room If you have disabled the automatic update option for packages (Administration > Settings > Packages > Package update > Disable), a notification icon is displayed for these packages installed in your Control Room when a more recent version is available. Automatic package updates for On-Premises Control Room

Fixes

Build 18361: This build includes the following fixes (along with fixes from the previous builds):


The purchase details for Control Room license is now displayed correctly on the Licenses page when the Citizen Developer feature is not purchased in the file license. Previously, purchase details was incorrectly displayed. Service Cloud case ID: 01994512
In WLM automation, the queue processing times retain the metadata during the entire automation lifecycle. Previously, after the first deployment of the automation, the metadata was lost. Service Cloud case ID: 01995713, 01997546, 01986247, 02004378, 02004171
After you update to Automation 360 v.29, the bot check-in no longer fails when you have cloned bots from other users and add a new directory for the dependency. Additionally, it shows accurate folder structure and dependencies for the cloned bots from its public bots. Previously, from the older version of Automation 360 v.29, when you checked in a bot with cloned bots from other users and added a new directory for its dependency, it failed with an error message. Service Cloud case ID: 01991263, 01991795, 01993056, 01993801, 01993825, 01992732, 01993655, 01994102, 01994336, 01993388, 01994525, 01994710, 01994569, 01994217, 01994263, 01994843, 01995026, 01994542, 01994223, 01994971, 01995404, 01995479, 1993255, 01995591, 01994528, 01996025, 01994710.
You can now run the v1/audit/messages/list API in Control Room swagger successfully. Previously, when the v1/audit/messages/list API was executed in Control Room swagger, the following error message was displayed: Please correct the following validation errors and try again. propKeyfilterErrorValue must be a string. PropKeypageerrorValue must be a string. Service Cloud case ID: 01988096

Build 18324: This build includes the following fixes:


You no longer see audit log entries for the Run bot pre processing failed event type for users and devices that are not active in the Control Room. Previously, such entries were displayed in the audit logs. Service Cloud case ID: 01983909
For users (excluding the users who are assigned the AAE_Admin role) who do not have any license assigned to them (Bot Creator, UnattendedBot Runner, Attended Bot Runner, or Citizen Developer), the Audit log page no longer displays unsuccessful entries related to the Default device set event for any activity performed by the users on the Control Room. Previously, multiple unsuccessful entries were displayed for such users. Service Cloud case ID: 01969726, 01970583, 01970990, 01971435, 01971171, 01970869, 01971854, 01970915, 01970523, 01971411, 01971788, 01971827, 01971482, 01971736, 01970333, 01972128, 01970497, 01972025, 01971459, 01971561, 01971068, 01972148, 01975216, 01975980, 01977479, 02001122
After you update Automation 360 to v.28, the Control Room no longer shows the `Out of Memory` error message and blocks the device connection. Previously, in such cases, you were not able to access the Control Room and bot deployments were stopped when device was disconnected. Service Cloud Case ID: 01976841, 01976847
Bot deployments no longer fail or no Control Room slow down issue due to Control Room notifications. Previously, Control Room performance was impacted due to notifications storage leading to bot deployment issues. Service Cloud case ID: 01978739, 01978768, 01978794, 01978812, 01978787, 01978826, 01978840, 01978851, 01978849, 01978816, 01978764, 01978782, 01978124, 01978837, 01978833, 01978820, 01978854, 01978780, 01978859, 01978790, 01978679, 01978831, 01978108, 1979121, 1979174, 1979190, 1979191, 1978957, 1977677, 01977677
When you sort the schedules data on the Scheduled activity page by the Next occurrence column, the schedules are sorted correctly. Previously, the schedules on each page were sorted individually instead of sorting all the schedules collectively. As a result, schedules were sorted and displayed incorrectly. Service Cloud case ID: 01936672, 01948336
The BotInsight API- Get Task Log Data will retrieve automation execution information for all automations in public folders, irrespective of whether they pre-existed in a private folder or not. Additionally, the API expected an automation name and returned data only for that automation. Previously, the GetTaskLogData API retrieved information only for the following: If a bot pre-existed in a private folder and will not work for bots directly uploaded to the public folder. When the bot name (optional parameter) is specified in the request. Service Cloud case ID: 01805000, 01965480, 01804312, 01854057, 01861154, 01905063, 01901693, 01932388, 01943438, 01911251, 1946327
You can renew and install licenses using your Control Room GUID without encountering an error. Previously, an error occurred in such a case. Service Cloud case ID: 01958580
After you update Windows Server 12 with Update for Universal C Runtime in Windows patch, the Automation Anywhere Control Room Discovery Bot ML Service no longer fails during Automation 360 installation.
When you uninstall the Bot Agent, it no longer affects the Enterprise 11 Google Chrome plugin. Previously, in such cases, Google Chrome plugin was uninstalled when you uninstall the Bot Agent. As a result, you had to install the Enterprise 11 Google Chrome plugin again to proceed with Enterprise 11 bot execution. Service Cloud case ID: 01967916
An active directory user can export roles without encountering failure. Previously, such a user was unable to export roles. Service Cloud case ID: 01954961
When you create or edit a locker, you can add multiple roles when updating the Consumers option. Previously, you were unable to add multiple roles. Service Cloud case ID: 01946827
You can use the User authentication setting when enabling SSO authentication without encountering an error. Previously, an error was displayed when you clicked the Edit button for the User authentication settings. Service Cloud case ID: 01946770, 01958619, 01984261, 01977599, 01962097, 01980940, 01964711, 01966644, 01971461
On the In progress activity page, the details page of an activity displays the Last modified date consistently. Previously, this date was displayed inconsistently. Service Cloud case ID: 01943780
In an Oracle Database environment, when you update from Automation 360 v.26 to later versions, the new package versions that are shipped though the installer are now enabled and set as the default version. Previously, you must have enabled each updated or new package manually and set it as default version.
WLM automations cannot be paused from any of the options on the Activity page (row or table level). This behavior is now consistent, and an appropriate error message is displayed when you try to pause the automation. Previously, the behavior between row and table level actions on the Activity page was inconsistent. Service Cloud case ID: 01941227
With the bot.dependency.timeout = <value in seconds> property, network connections no longer stuck. Also, a scheduled bot no longer remains in the Pending execution status. As a result, Bot Agent can download the dependencies and thebot executes successfully. Previously, during dependency download phase, the downloads were stuck due to unreliable network. As a result, Bot Agent could not download the dependencies and the bot did not execute. Service Cloud case ID: 00951927, 01822836, 01801869, 01874596
You can edit and save device credentials on the My Settings page without encountering errors. Previously, you were unable to save the device credentials. Service Cloud case ID: 01941151, 01943701, 01958822, 01858205, 01867974, 01862001, 01867845, 01921703, 01905028
Audit log details page displays complete text for all fields. Previously, text that was displayed for some of the fields were truncated. Service Cloud case ID: 01908673
On the Historical page, the activities details page displays the correct status for bots that are stopped from executing. Previously, the status for such bots was displayed as failed. Service Cloud case ID: 01835612, 01962900
When an AAE_Admin tries to delete a user, a prompt is displayed with the list of resources that the user is associated with. This list includes resources such as licenses, schedules, pools, lockers, queues, and credentials. This information helps the administrator to disassociate the user from the resources before deleting the user. Previously, a generic message was displayed before a user was deleted. Service Cloud case ID: 01255043, 01761442, 01764557, 01800227, 01807149, 01927012, 01804960, 01949491, 01970079
Bot Agent can now successfully download the packages to device during bot deployment even if the repository path is a Distributed File System (DFS) path. Previously, if the repository path was set to a DFS path, Bot Agent was not able to download the packages to device and bot deployment failed. Service Cloud case ID: 01940976
When Bot validation feature is enabled and if you pass a File type variable from the parent to child bot, you no longer encounter the preprocessing error during runtime. As a result, you can run the bot successfully. Previously, a File sub-type was handled incorrectly and validated against string rule during bot validation. As a result, you were unable to run the bot when file variable was used in the Task Bot. Service Cloud case ID: 01969744
When you update the cloned bots by replacing older dependencies with the new ones and check in these bots to the public workspace, the update is retained when another user checks out this updated bot. Previously, when another user checked out this updated cloned bot, the older dependency remained along with the new one. Service Cloud case ID: 01948590
When you restore your bots and their dependent files from Git to your server repository, the version information is retained in the correct order. When the Git restoration process is complete, the bots and files contain the same version as the source. Previously, version information was not restored in the correct order. The bot restored was not of the same version as its source. Service Cloud case ID: 01924034
When you update to Automation 360 v.24 or later and the Control Room server repository is on a user network file path, if you import bots that contain a large number of bot or non-bot file dependencies, the bot now imports successfully. Previously, the bot import failed with an error. Service Cloud case ID: 01807824, 1815889, 01831729
When a large number of users perform concurrent bot check-in operations and if the bot contains multiple dependencies, the concurrent check-ins are completed without delay. Previously, the check-in operation was slow, affecting other repository actions and the Control Room performance. Service Cloud case ID: 01944887, 01964122
When you update to Automation 360 v.29, code analysis rules are now retained for configured policies. Previously, code analysis rules were not retained in the active policy after the update.
When you update to Automation 360 v.29, you can now seamlessly view and execute bots without encountering any issues. Previously, there was a delay and error in displaying the view and run bot functionality due to an inconsistency in the global database configuration. Service Cloud case ID: 01978351, 01978355, 01978359, 01978371, 01978389, 01978376, 01978393
When you update to Automation 360 v.29, bot check-in works properly without any issue even when Git has an older configuration. Previously, bot check-in failed displaying an error with older version of Git because of the missing auth_type record in the database. Service Cloud case ID: 01983953
On the Audit log page, when you select the source type as Event type or Source, the corresponding drop-down values are sorted in alphabetical order. Previously, the order was random for these source types. Service Cloud case ID: 00805794, 01908670, 01766369
The Automation 360 installer shows an appropriate warning message when Elasticsearch service is not running. Previously, the warning message was not clarifying the issue. Service Cloud case ID: 01967255
On the Create Active Directory role mappings page, the Active Directory domain option lists domain names as NetBIOS names. Previously, domain names were displayed as fully qualified domain names (FQDN).
API Task is designed for Automation 360 cloud deployments only and is not available for On-Premises deployments. Previously, during the beta release, API Task was made available in the On-Premises deployments for a brief period.
You no longer encounter issues when you create a bot and disable any action (the disabled action has no data or contains errors) in the code. Previously when you executed such bots, it failed with an error. Service Cloud case ID: 01952661
If Auto update is enabled for Bot Agent in the Control Room, the registered devices running Windows10 Enterprise no longer restart after the Bot Agent update. Service Cloud Case ID: 01950021
After a successful installation of the Bot Agent on a device, the Bot Agent service is registered correctly and is displayed on the Windows Services page. Service Cloud Case ID: 01797914
After updating to this release, you can delete a registered device from the Control Room without any issues. Service Cloud Case ID: 01903472, 01914698
Security vulnerability issue fixed in the crutils.jar file. Service Cloud case ID: 01955093
Automation Co-Pilot end points include the HTTP Strict Transport Security (HSTS) response headers. Previously, the response headers were missing in the Automation Co-Pilot end points. Service Cloud case ID: 01926041
In a form with a text field that has a max character limit, when a value from a previous task is inherited an error will display. This was fixed in Cloud build 17557 and On-Prem build 17571. Service Cloud case ID: 01969999
After you update to Automation 360 v.29, no error messages are shown as separated characters. Previously, when you update to Automation 360 v.29 and system language was set as non-English language, for example Japanese, error messages were shown as separate characters. Service Cloud case ID: 01986699, 01988909
The format of date data passed from bot to form now transfers accurately. Previously, the date format was changed during transfer.
You can now manually enter any time value between 00:00 to 00:45 when entering time (24-hour format) in forms. Previously, the values entered defaulted to the nearest 15-minute interval. Service Cloud case ID: 01963769
In the Bot editor, the Create a request action in the Process Composer package now supports table variables. This allows you to pass the data of a table to the initial form during run time in Automation Co-Pilot.
If an error is present in a mandatory field the submit button is disabled. Previously, when using forms in build 16667 the button remained enabled during first attempts. Service Cloud case ID: 01949368
Check box values render as expected in web forms. Previously, an inconsistency occurred from designing the form, causing the rendered check box value to be inaccurate. Service Cloud case ID: 01951738
When you navigate though page numbers on the Average time to spent to create a Task Bot tab, the dashboard sorts and shows the bots list correctly. Previously, when you navigate through page numbers, the dashboard showed inconsistent data even if the same page was clicked. Service Cloud case ID: 01820655
Build 18345:This build includes the following fix. When a user clicks the cancel button of a form, in a Cancel Human task action, the form validation is ignored and the process moves to the endpoint to cancel the task. Previously, when a user clicked the button the form validation was considered and mandatory fields or errors could cause the form to not be submitted.
On On-Premises deployments, the heap size of the Ignite services no longer causes the Control Room to be unresponsive. Previously, the Control Room used to become unresponsive in such a scenario. Service Cloud case ID: 02002563

Limitations


For a queue in draft mode, when you edit the general settings such as Max auto retry attempt, you cannot save the changes. Additionally, it generates an error message.
For users with more than 1000 schedules (active or inactive), the Scheduled activity page might not load properly. At times, you might encounter an error message while browsing the schedules across pages. Workaround: To view the list of schedules, you can filter and sort the schedules by status.
Process Discovery (Discovery Bot) has been removed from the Community Edition, but there is a non-functional link to Process Discovery (Discovery Bot) on the home page that needs to be ignored. Workaround: Ignore the non-functional link in the Community Edition.
There might be a mismatch in the Bot Agent update required data in device dashboard with that of the Devices page. This mismatch is because the Devices page shows the data about only online devices whereas the device dashboard shows the data about all devices (online and offline).
When you export or promote bots or files that are checked in before January 2021, you might encounter an export or bot promotion error. Workaround: Check out the bot. Check in the bot without making any changes to it. A new version of the bot is created. Export or promote the bot.
After you update to Automation 360 v.29, the bot check-in fails with an error message. To fix this issue, perform one of the following steps: Delete all the cloned bot copies (if multiple users cloned the bot, delete them from all users) and check in the bot. Create the same folder structure under other users who cloned this bot and does not have the new folder structure (that has been modified during the check out).
Trigger listeners is not supported when you use an auto login that is configured from an external key vault.
Importing bots and packages from the Bot Store does not work in Automation 360 v.29 for all users. The Bot Store import action fails, and the import remains either in IN_PROGRESS or in FAILED status in the Bot Store downloads page. Workaround: See A360.29 \| Importing bots and packages from Bot Store does not work (A-people login required). Service Cloud case ID: 02001442, 02002465, 02000881


Limitations from previous releases
While running a bot in debug mode, the bot will fail if the variable size gets greater than 3 MB. An error message appears showing that a variable has exceeded the 3 MB limit.
After you update Automation 360 to v.28, when you cancel the update process after removing all the services, the rollback of the services does not happen. As a result, you will encounter an error message, when you attempt Automation 360 update.
Bots that are in the Queued status do not appear automatically on the In progress activity page. Workaround: Click the Refresh table button on the top-right corner of the activity table to view the queued bots.

Feature deprecations

Review features and capabilities (from Automation Anywhere or other third-party vendors) that are deprecated or nearing deprecation to understand how they impact your automation.


The user interface for the Automation 360 product will no longer support Italian, Russian, and Simplified Chinese languages. In addition, updated release documentation will no longer be available in these three languages though English documentation will be accessible. For a complete list of deprecations, see Upcoming feature deprecations.
Microsoft has deprecated EWS API for Exchange Online and has recommended that users move to Graph API. See Upcoming API Deprecations in Exchange Web Services for Exchange Online. Note: We recommend that you update the impacted bots by replacing each email-related action with the equivalent new action in the Microsoft 365 Outlook package (based on Graph API). Microsoft 365 Outlook package updates \| Microsoft 365 Outlook package

Updates to the interface

Review the updates to the interface in this release.

See the following video for the updates in the interface for Automation 360 v.29 release:

<span>updates to the user interface in <span class="ph">Automation Workspace</span> for v.29 release</span>


The External Key Vault Integration page is simplified to easily select and configure key vaults when installing the Control Room. Integrate HashiCorp Vault to retrieve credentials
The Licenses page is simplified to segregate the licensing information. View license drill down for users and Control Rooms
The Attention needed filter is added in the notification panel to simplify the notification categories. Simplified notifications categories
The Time filter field is added to search, view, and customize the historical activities based on the selected time duration. Time filter for historical activities
The Edit option is added for in-use queues to update the queue details and process queues faster. Ability to edit workload management automations
Move bots across environment easily with bot promotion. Move bots across environments
The icon for a process has been updated in the Bot editor.
Variables for currentValue and currenKey are now visible in the variable picker, regardless of variable type. More visibility for variables