Version 11.3.5 Release Notes

Review the new features, changed features, fixed features, security fixes, and known limitations in Version 11.3.5 for Automation Anywhere Control Room, Enterprise Client, and Bot Insight.

New features

Control Room
Export or import roles and users

Service Cloud case ID: 00353413

For roles management, you can export or import custom roles and users associated with the roles. You can use the already created roles and users in your Control Room without manually creating them.

Export or import roles and users

New columns for devices and device pools details

Zendesk ID: 223185

Use the columns to perform these actions:

  • View the work item ID and queue name that is currently processed by the device from the Devices table in the My Devices page.
  • View the work item ID, queue name, automation name, and bot name that is currently processed by the device from the Bot runners table in the View device pool page.
Edit Active Directory role mappings

Admin users can edit role mappings in the Control Room. You can only edit the mapping name and roles (add or remove roles).

Edit Active Directory role mappings

View history of deleted bots

View the history of bots from the Historical activity page even if the bots and the folder containing the bots are deleted. However, you cannot run the deleted bot from the Historical activity landing page and the View historical activity page. Additionally, the historical data of the deleted bot is exported in the CSV file.

Bot Insight
Retrieve information from the Bot Insight API, and generate and visualize data analytics on Microsoft Power BI

The Automation Anywhere custom connector enables you to establish a secure connection to Microsoft Power BI, and generate and visualize data analytics. You can select the Bot Insight APIs in Microsoft Power BI and apply specific parameters for each of the APIs. The custom connector transforms the Bot Insight API responses to data model visualizations in Microsoft Power BI.

Enterprise 11 data connector for Power BI

Enhanced deletetasklogdata API

The deletetasklogdata API enables you to delete bot data based on the RunId of the bot.

Bot Insight API details

Analyze and customize bot operational parameters

The customizable Operation dashboard provides analytical information about the performance of your Digital Workforce. You can analyze the performance of a bot, status of tasks, past and upcoming schedules of tasks, audit information, usage of various resources, workload status, and health of the machine on which the automation tasks are executed. The various data sources and visualization widgets enable you to customize the dashboard.

Operation dashboard

Visualize and analyze bot utilization information

The Bot Utilization Heat Map widget in the Devices dashboard provides information about the usage analysis of deployed on different Bot Runner machines.

Devices dashboard

Changed features

Control Room
Configure session timeout in the configuration settings

Zendesk ID: 189400

You can now configure the inactivity time in the range of 10-60 minutes in the Control Room configuration settings. The default value is 20 minutes. Depending on the time set, the user will be timed out after the specified minutes of inactivity.

Configuration settings

Run auto discovery as a cron job

Zendesk ID: 194840

You can now run auto discovery as a cron job in the Control Room to detect live domain controllers and update the LDAP URLs accordingly.

Run auto discovery as a cron job

New GUID created for bots with duplicate GUIDs

Zendesk ID: 159359

Duplicate GUID instances cause a data conflict in the Bot Insight dashboard. To avoid such conflicts, the Control Room now creates a new GUID for a copied bot when it is uploaded to the Control Room. Duplicate GUIDs are generated when Windows Explorer is used to copy and paste a bot.

New credential screen in Control Room installer for Elasticsearch

When you install Control Room in Express or Custom mode, a credential screen is now displayed for Elasticsearch authentication. This is to secure access to Elasticsearch data store in Control Room.

Configure Elasticsearch credentials | Enterprise 11: Installing Control Room using Express mode |Installing Control Room using scripts

High availability enhancement

Starting from this release, configure the required minimum three nodes in a Control Room data center cluster for high availability deployment.

Enterprise 11: High Availability deployment model

Enterprise Client
Define closebrowserbyhandle value in the AA.Settings.xml file for Close Browser command

Service Cloud case ID: 00480927

Define the closebrowserbyhandle value to True/true in the AA.Settings.xml file to support the Close Browser command. This setting is required in a scenario where the Open Browser command is used in a child task and commands such as Keystrokes and MWC are followed by Close Browser in the parent task.

Web Recorder command

Connect to EWS server with OAuth authentication

Service Cloud Case ID: 00350930

Microsoft has introduced a new authentication for Exchange Web Services (EWS) protocol with OAuth. You can use the EWS protocol with OAuth authentication for the following:

Configure retrycount or enableadvancedlegaldisclaimerbypass values for Auto Login to function properly

Zendesk ID: 205572

Perform one of these actions to support the Auto Login process:

  • Define the retrycount value as 3 in the AA.Settings.xml file
  • Define the enableadvancedlegaldisclaimerbypass value as True in the Automation.Autologin.Settings.xml file

Auto Login

Bot Insight

The row limit for data sources in the Bot Insight Operations dashboards is increased to 100000. Ensure that the row limit of the data viewer application can support the number of rows in the exported records.

Fixed features

Note: Typically no user action is required for fixed features. If an action is required, it will be included in the description.
Control Room
Zendesk ticket ID/Service Cloud Case ID Description
00453518 Devices that are unassigned from any schedule are now available in the device list on the Create device pool page. Users now have a proper list of devices to create device pools.
00354649 You can now successfully run the selected production version of bots using the Run bot with queue option.

00469758

The scheduler now automatically corrects (auto-corrects) the state of the Quartz table, preventing the scheduler from stopping work. As a result, schedules no longer disappear and the scheduler properly triggers the schedules based on the next occurrence.
00447964, 00481888 The ampersand (&) special character is now supported for Windows and SQL Server authentication password. Previously, an installation failure message was displayed on the database screen during Control Room installation if ampersand was used in the password.
When the required signing option is enabled and the LDAP password for a Control Room user expires, users can now reset their password without appending the FQDN. Previously, users had to enter their domain name and the FQDN along with the username as a one-time activity to reset the LDAP password.
00634620 When you restart the Automation Anywhere Control Room Caching service and add new Work Items in the queue, newly added Work Items are now executed properly. Previously, the execution was not working.
Enterprise Client
Zendesk ticket ID/Service Cloud Case ID Description
00493296 The AAProxyServer.exe now does not crash when the AAPlayer is closed. In case the AAProxyServer application is not running, the AAPlayer starts the AAProxyServer service and the bot execution is not affected.
00473373 ABBYY FineReader Engine in the OCR command can now capture the entire text from any image file. Previously, only the last identified text was stored and the ABBYY FineReader Engine only captured a small portion of the text from the image file.
-- When you save a task in XML file format, the task is now exported line by line, and an unhandled exception error does not appear.
00388097 When the Terminal Emulator command is executed using Wait till screen contains text, the command now works properly in all terminal environments and does not time out if text is present on the screen.
00473752 When bots are exported in Enterprise Client, special characters are also exported without any error in the XML file format.
-- When Error Handling uses the Send Email command for MetaBot logic, the command now displays the default subject in the mail as Automation Anywhere finished executing the metabot logic even when you remove the subject from AA.Setting.xml file. Previously, the default subject was not displayed properly for MetaBot logic.