Version 11.3.3 Release Notes

These release notes describe new features, changed features, fixed features, security fixes, deprecated features, and known limitations in Version 11.3.3 for Automation Anywhere Control Room, Enterprise Client, and Bot Insight.

New features

Control Room new features
Feature Description
Bot Store integration
Enhanced user interface to set the time value when scheduling a bot (Zendesk # 96099)

When scheduling a bot, you can set the Start and End time by selecting a time value from the drop-down list, which contains pre-defined time values in the 12-hour format at intervals of 15 minutes. This enables you to quickly select the time from the list, or manually set the time for the values that are not available. See Enterprise 11: Schedule a bot.
Filter work item results (Zendesk # 151417) The Work Item Results column is introduced in the Work Items view table on the Queues page to quickly filter the work item results. You can use this to take the necessary actions on the queue tables.

See Enterprise 11: Actions allowed on view queue page.
Filter the Start time and End time in the List work item API (Zendesk # 186813, 238660) To find specific information, you can now filter the Start time and End time columns when you use the List work item API.

See List all work items in a queue.

Automatically reinstall Control Room during repair or reinstall process

When repairing or reinstalling the Control Room, after the uninstallation completes, you do not have to manually run the setup file to reinstall the Control Room. The reinstallation process starts automatically using the previous settings. See Uninstall or repair Control Room installation.
Google Chrome support for MetaBot MetaBot capabilities are supported in Google Chrome. See Supported browsers.
Migrate version 10.x Historical activity to version 11.x

Introduced the option to Include Historical Activity when migrating bots using the Bots and Schedules option. This option enables you to retain the task run history of the bots that need to be migrated to version 11.x. See Select bots to migrate.

After the migration process completes, you can view the status of the historical activity migration (success or failure) in the History tab of the View Migration page. See Analyze migration status.
Google Cloud Platform support for Control Room cloud installation Install Control Room on a Google Cloud Platform instance running Microsoft Windows Server 2019, 2016, or 2012. See Enterprise 11: Installing Control Room on Google Cloud Platform.
Added TLS support for distributed caching and messaging communication across nodes in a cluster

Distributed caching and messaging communication across nodes is now over TLS.

Configurable properties enable you to selectively disable TLS in addition to disabling/enabling authentication.
Mapping Active Directory (AD) to roles in Control Room You can map Active Directory (AD) security groups to roles in Control Room. These roles provide access to Control Room objects, such as bots, folders, devices, credentials, and Credential Vault lockers. You can use this information to dynamically assign roles to users, depending on the AD groups that they belong to.

Maximum 200 Active Directory (AD) groups can be mapped to roles in the Control Room.

See Map Active Directory roles.
Enterprise Client new features
Feature Description
Uninstall Flex plug-in using Command line You can use the Control Panel or a command line interface to uninstall the Flex plug-in installed by the Automation Anywhere Enterprise Client. See Uninstall or reinstall plug-ins.
Interactively capture objects from SAP GUI application You can now interactively capture objects from the SAP GUI application using the GUI Automation command. This command enables you to capture objects with the click of a mouse.
Install Enterprise Client chrome plug-in without internet access. (Zendesk # 125883, 174341) You can use the command line interface to install the Enterprise Client Google Chrome plug-in, even when you do not have internet access. See Install plug-ins in offline mode.
Enable or disable ROI settings logs (Zendesk # 200865, 217246, 217939) You can use the Enable or Disable ROI Settings Logs to maintain the performance level of Bot Runners . Disable the logs from Tools > Options > ROI Settings if you notice performance degradation on the Bot Runner machines. See Using ROI Settings.
Bot Store integration
  • Create and store Digital Workers or bot packages in the default Bot Store folder.

    See Organizing Bot Store Digital Workers and bots.

  • This enables you to configure the required parameters and bot codes, which are not exposed for the protected bots. Vendor IP or the IP of the original author of the bot is now secured when viewing and playing the protected bots downloaded from the Bot Store. The source code of the protected bot or MetaBot is also not exposed. However, you can configure the value of the variables used in the protected bot or MetaBot. See Viewing and playing protected bots.
Enterprise Client and Remote Agent for Citrix are Citrix Ready certified Automation Anywhere Remote Agent is now Citrix Ready certified. This certification is a validation of our product meeting the requirements set by Citrix for its partners. As an added benefit of the certification, we are now listed on the Citrix Ready Marketplace - a vital source for Citrix customers.
Auto login in Citrix environment (Zendesk # 135938, 128709) You can use the auto login feature to log into a Citrix environment if it has locked out or logged off. See Citrix Automation pre-Version 11.3.2.
Create zip package for the Bot Store or Digital Worker from Enterprise Client You can now seamlessly create a zip package for the Bot Store bot or Digital Worker from the Enterprise Client instead of creating it manually from the File Explorer. The zip creation identifies all the required dependencies and creates a folder structure that is consistent with the Bot Store. You can now directly use the zip package and submit it to the Bot Store for the end users. See Creating a bot package.
Mozilla Firefox plug-in support (Zendesk # 53882, 55279, 55653, 70621, 77096, 78264, 89835, 93333, 93913, 103955) You can install the Mozilla Firefox plug-in that enables you to automate the HTML technology-based web applications that are launched using the Mozilla Firefox browser. See Install plug-ins using the command line.
Email Trigger to support POP3 with SSL (Zendesk # 205859) The Email Trigger action in the Trigger Manager now supports the POP3 protocol with the SSL connection. This support enhances the authentication for the Email trigger action.

Support for PowerBuilder platform 10.5 (Zendesk # 86557, 98160, 140835)

The Object Cloning command now supports the PowerBuilder platform 10.5. This enables you to capture and play the control actions for the applications built on the PowerBuilder 10.5. Some of the Object Cloning actions might not function as expected. See Troubleshooting PowerBuilder platform controls.
Select SOAP service URI for execution (Zendesk # 105937, 106452, 141496, 192347, 239224) Introduced the Default, Dynamic, and Static options to Select URI for execution in the SOAP Web Service command. These options enable you to select the SOAP service endpoint URI that is required to run a bot. See Using the SOAP Web Service Command.
Add Subject to Email Notification template (Zendesk # 98464) Introduced support to add a customized Subject to the error email notification from the Error Handling command. You can also use the System Variables and User-defined Variables to define the subject. See Error Handling command.
Google Cloud Platform support for Enterprise Client cloud installation Install Enterprise Client on a Google Cloud Platform instance running Microsoft Windows Server 2019, 2016, or 2012. See Installing the Enterprise Client.
Additional browser support for Object cloning and MetaBot

HTML technology is now supported for Object cloning using Mozilla Firefox.

MetaBot support for HTML and UIAutomation is also enabled for Google Chrome.
Bot Insight new features
Feature Description

Bot Lifecycle Management support

The Bot Lifecycle Management utility now supports both PostgreSQL and Oracle databases.

See Enterprise 11 Bot Lifecycle Management.

Bot Insight CoE Admin role Introduced the AAE_COE_Admin role. Use this role to view Default, Saved As, and Published CoE dashboards.

See Enterprise 11 roles.
Password encryption All the passwords that are stored in the Bot Insight property files locations are encrypted.
Bot Velocity dashboard feature enhancement The Bot Last Modified By column in the Home Bots Velocity dashboard provides information on the last user that modified the bot.
Service Insight Bot packaging The Service Insight bot is packaged along with the Automation Anywhere Enterprise client in the following location:

My Tasks > Service Insights

When you install the Automation Anywhere Enterprise client, the Service Insight bot is installed by default. This bot collects real-time information from the Control Room and provides best practices to increase the bot velocity.
Note: You can also download the Service Insight bot from the Bot Store.
Managing CoE dashboards across environments The Export and Import functions introduced in the CoE dashboard enable you to seamlessly move the business information and customized CoE dashboard configurations across different environments.

See Managing COE dashboards across environments.
New widgets in the Bots Dashboard The following widgets are added in the Bots Dashboard:
  • Bot Status
  • Top Failure Reasons
  • Upcoming Schedules
  • Home Bots Capacity Utilization
New widgets in the Devices Dashboard The following widgets are added in the Devices Dashboard:
  • Device Status
  • Device Schedules
  • Top Error Messages
ROI transaction count Data for failed and canceled transactions is logged in the CoE dashboard when the transaction count appears under Transaction Count.

See Configuring a COE dashboard.
Attended Bot runs transaction count The individual manual run count of the bot runners are logged under Transaction Count.

Changed features

Control Room changed features
Feature Description
Upgrade the Control Room with fewer inputs

You can upgrade the Control Room with fewer input as the setup enables you to continue using the previous configurations such as the mode of setup and database type. You are, however, allowed to update the password on the service credentials page and database port number.
View the In progress activity even when the run time window is hidden (Zendesk # 91292, 99402, 119115, 184415) You can view the In progress automations in the Activity > In Progress page even if the Run Time window on the Bot Runner machine is hidden. See Monitor in progress activity.
Add more columns to work item structure for viewing in Control Room(Zendesk # 186809) You can add a maximum of ten columns to a work item structure of the Control Room. In the previous versions, a maximum of five columns were allowed.

See Enterprise 11: Define work item structure.
Bot pool optimization in Workload Management (Zendesk # 118922, 127626, 128638, 131192, 174930, 199205, 226370, 228639, 239912, 184983) Unused Bot Runners are optimally utilized from a device pool when the work items are executed from multiple queues.

For example, two Bot Runners that have finished processing work items from Queue 1 are utilized to run work items from Queue 2 instead of waiting for Queue 1 to finish the deployment.
Ability to stop processing work items with Active status (Zendesk # 186806) You can stop the processing of work items from the Activity > In Progress page for the bots that have an Active status and are running/processing on the Bot Runner machines.

See Monitor in progress activity and Enterprise 11: View work items.
Increased the Queue work item data length to more than 500 characters (Zendesk # 155236, 158033, 158349, 1871641) A Work Item of a Queue can contain data having more than 500 characters.

See Enterprise 11: Define work item structure.
Local bot run activity captured in Historical Activity page The Historical Activity page captures the information on when a bot is run locally on Attended, Unattended Bot Runner or Bot Creator machines.

See Manage historical activity.
Enhanced help experience with an upgraded documentation portal (Zendesk # 146697, 134731) You can access the Control Room help from an upgraded documentation portal - https://docs.automationanywhere.com/.
Enterprise Client changed features
Feature Description
Flexibility to use any active port for Proxy Server Settings (Zendesk # 63470, 66971, 66990, 80179, 87506, 174323, 175312) You have the flexibility to use any active Port number within the 0 through 65535 range for setting up a Proxy Server.

Also, when you alter any settings under Options, the application does not validate the Port number in the Advanced Settings.

See Using Advanced Settings.
Save attachments containing a [TAB] in its name (Zendesk # 222561) You can save attachments with names that contain a TAB when using the Email Automation command.

See Email Automation command.
Options to specify technology of the captured object The Object Cloning command enables you to select an option to specify the technology of the object being captured.
Support for 3.0.21.0 version of SAP DLL (Zendesk # 113499, 119505, 120055, 169238, 228083) The 3.0.21.0 version of the SAP DLL is supported. This enables you to import and use the SAP BAPIs in the Enterprise Client.
Save Response header information in Array and Dictionary type variable (Zendesk # 52357, 77979, 81835, 95840, 130176,181871) You can now save the response header information in the REST Web Service command to an Array and a Dictionary type variable.

See Using the REST Web Service Command.
VT220 support in Terminal Emulator command (Zendesk # 49318, 191110) You can automate processes using a VT220 terminal when using the Terminal Emulator command.

See Terminal Emulator command.
Function key [Fn] support in Terminal Emulator command (Zendesk # 54251, 54989, 97573, 99677, 105183, 108375, 109619, 120176, 120235, 146934, 183638, 191110, 206109) Function key [Fn] support introduced to automate processes using ANSI and VT100 terminals with Advanced Technology in the Terminal Emulator command.

See Terminal Emulator command.
Support for array and dictionary variables (Zendesk # 75028, 141270, 229010) In MetaBot Logic, array variables are visible from the output variable drop-down menu.

When a command returns an array type variable, you can store it in the value type variable. In this condition, a separator must be used. The available separators are space (default value), comma, semicolon, hyphen, colon, and period.
Viewing MetaBot text without MetaBot Logic (Zendesk # 98669) You can now view the MetaBot text and parameters in the Workbench Editor without first opening the MetaBot Logic.
Monitoring mechanism to detect connectivity issues for Files and Folders Triggers (Zendesk # 115778, 135132, 192678, 196610) Connectivity to remote files and folders used in triggers can now be monitored along with ability to retry connection upon failure.
Credential Vault variable format updated (Zendesk # 98669) Credential Vault variables are formatted correctly when using the Run Logic command in a MetaBot, and when passing the variable as an input or output parameter. For example:
<InputParameters>
   <Parameter>
        <Name>$Vinputpara
lt;/Name>
        <Value>$Vmihirinput(Vinput)
lt;/Value>
        <Type>Value</Type>
   </Parameter>
</InputParameters>
Enhanced help experience with an upgraded documentation portal (Zendesk # 146697, 134731) You can access the Enterprise Client help from an upgraded documentation portal - https://docs.automationanywhere.com/.
Support for configuration in AASetting.xml file for the Excel command options (Zendesk #211964, 216478) To retain the legacy behavior of the Contains Header and the Excel Cell Row options of the Excel command when used in a loop, a new configuration is introduced in the AASettings.xml file of Automation Anywhere Enterprise Client, as follows:
<retainexcelcellrowlegacybehavior>
See Update Enterprise Client settings file for Excel command.
Share Excel sessions across parent and child Bots (Zendesk # 51562, 70452, 72932, 125147) The Excel command is now enhanced to share the session from a parent Task Bot or MetaBot to a child Task Bot or MetaBot using the Run Task command.
Bot Insight changed features
Feature Description
Transaction Status API The Bot Insight transaction status API retrieves the transaction status of each function:
  • In progress
  • Completed Successfully
  • Canceled
  • Failed
  • Timed Out

See Bot Insight task log data.
Transaction count display In the Business Information dashboard, the Units menu lists the transaction count and the transactions conducted per hour details by default.
Operations dashboard Role Based Access Control (RBAC) The USER_RBAC and DEVICE_RBAC files are modified to reflect the appropriate RBAC in the dashboards after you restart the Bot Insight services.

Fixed features

Control Room fixed features
Zendesk Ticket ID Description
198606, 205967 If you are granted the View my in progress activity, View my bot, and Run bot permissions, the insufficient permission message is not shown when you access the Historical activity details page.
164510, 207614 Credential variables are processed correctly with the Authentication API POST parameters when the request is run in a task.
203133 Work Load automations resume automatically when new work items are added to a queue. A queue is picked up in the next round or when the work items are picked up on a priority basis even after the work item consumption is manually stopped.
-- If you run the Control Room installer multiple times, it opens multiple installer instances, but you are allowed to install the Control Room using only one instance. If you try to install the setup using another instance, an error message appears.
182075, 194755, 00371867 The status of a Work Item does not remain Ready to Run and changes to Active automatically when you insert a Work Item using the Work Item API in a Queue. You also do not have to restart the Automation Anywhere Control Room Service to change the status from Ready to Run to Active so that the Queue can execute.
Enterprise Client fixed features
Zendesk Ticket ID Description
187611, 215676, 217196, 226990 You can now delete an XML file after closing the XML session using the End XML Session operation.
195881 When an automation task containing a Variable Operation command is saved as an XML file, the disabled status appears in the XML file.
184641 When an array variable is reinitiated using the Variable Operation command in an automation task after connecting to a database instance, and the result set is empty, array elements now work as intended and do not return an exception.
205919, 211431 A configuration option is provided to ensure that the characters are read correctly after using the PDF Integration command with the Extract Text option. The configuration option is to set the flag for ReadWithSystemEncoding to "False" in the AA.Settings.xml file.
185559 A configuration option is provided to ensure that the Email Automation command reads the email subject containing a combination of encoded and plain text accurately.

The configuration change is to include the following within the <player> tag in the AA.Settings.xml file:

<options><emailautomation> <decodeentiretext>True</decodeentiretext> </emailautomation></options>
213611, 225573 You can run a Task Bot that uses a VB script containing more than 4136 characters.
209052 In the Excel command for the Get cell option, when you reinitiate an Array type variable, the value in the variable is available and is not erratic when you run the Task Bot.
96847 The page orientation in a PDF file does not impact data extraction when you use the Extract Form Fields option in the PDF Integration command.
208710 XML is correctly exported for a Taskbot when the Error Handling, Loop, or If/Else conditional commands are deleted or disabled.
182168 After upgrading to the Automation Anywhere 11.x version, the Unzip File(s) option in the Error Handling command enables you to overwrite the existing files when it is used in the error handling block.
153088 A black screen is not shown when the Task Bots that are queued to run on a Bot Runner are deployed and run successfully using remote sessions.
136706

The Visual log file of the Report Designer now shows the correct From and To dates.
136833 Consider an automation task that uses more than one Credential Vault variable with the same name but a different combination of upper and lower case characters, and with one of the Credential Vault variables no longer existing and the command using it is disabled. Such a task now runs correctly on the local machine or if it is deployed or scheduled from the Control Room on a Bot Runner machine with or without the Autologin feature enabled.
188292, 209531 With the Advanced Technology option enabled in the Terminal Emulator command, you can now page up and page down correctly using the function keys KEY_PGUP and KEY_PGDOWN respectively for the TN3270 and TN5250 terminal types.
– The Terminal Emulator command now supports Japanese text when used with the Send Text option using DBCS encoding for the VT Series terminal types with Advanced Technology.
155093, 183664

The Insert Keystrokes command now works properly with the TN3270 Terminal Emulator using the Advanced Technology. The Send Text option sends all the specified text on the Terminal Emulator screen before the next command is executed.
194092 In the Database command, the Stored Procedure option without parameters enables you to execute the tasks without any object reference errors.
– The 'webcrsvc/clients/getall' API endpoint now enforces RBAC to restrict any unauthorized access to the Client's information that is registered with the Control Room.
205904 The MetaBot focus is not lost when task execution completes. You can now configure a property to enable or disable the setfocus API.
– In Oracle Java, fixed the issue when scrolling SelectItemByText from the drop-down menu.
137566, 197738 MetaBot screen capture for Oracle forms embedded in the Microsoft Internet Explore screen now captures the hidden objects after adding the capturehiddenobjects tag in the AA.Settings.xml file.
198505, 221432 The Object Cloning command does not display an error if you have specified 0 in the Wait for the object to exist field.
161504 Object Cloning works when you migrate bots created in version 10.7.0 to Version 11.3.3.
174893 The Image recognition command does not realign itself when you click the Quick Test option after capturing an image.
211752 You can use the .xlsb file with an array type variable to use the values available in that file as an input for the variable.
– In the Rest Web service command, a Bot Creator is now not allowed to append any other text or local or system variable to the Credential Variable.
– The To and From email fields for the MetaBot Logic are now populated when Tools > Options > Email Settings > MetaBot Logic tab is enabled and saved.
195836 For a MetaBot, when using an Oracle Java application, an error message is not shown when an invalid index name or an invalid item number is entered in the fields.
– The mouse down action now gets the correct status when capturing an object in Citrix Virtual Apps.
– If you run the Enterprise Client installer multiple times, it opens multiple installer instances, but you are allowed to install the Enterprise Client using only one instance. If you try to install the setup using another instance, an error message appears.
3228 The Task Bot log now captures the Timeout and Last Run Time data when the Task Bot times out during execution. You can view the data using the View Log option from the Properties tab.
3418

When you edit a Task Bot that is recorded using the Web Recorder with Pattern-based data to extract the data, the Append to an already existing csv file option is not selected again by default if it was disabled during recording.
161012, 190195, 219504

You cannot perform automation on the Automation Anywhere application window. With this change in behavior, the run time window now does not interfere with the automation of applications that use the Object Cloning command when a Task Bot is executed.
Bot Insight fixed features
Zendesk Ticket ID Description

198111

Bot Insight now supports apostrophes in dashboard titles.
-

Transaction count display

In the Business Information dashboard, the Units menu lists the transaction count and transactions conducted per hour details by default.

Security fixes

There are no security fixes listed for Enterprise Client in this version.

Control Room security fixes
Zendesk Ticket ID Description

130121, 145734, 150481, 162605, 169866 198766, 205937

Updated the underlying Elasticsearch version to 6.4.3.
129996, 138976 Implemented the referrer policy configuration for Control Room.
Bot Insight security fixes
Zendesk Ticket ID Description and Fix
All the passwords that are stored in the following locations are encrypted:
  • Bot Insight property files

  • Bot Insight database
155901, 179991, 188647 Passwords are now encrypted in the Bot Insight configuration files. The Zoomdata.property file contains the encrypted password for SQL database.

Deprecated features

Control Room deprecated features
Feature Description
Device time-out parameter from Work Load Management properties file (Zendesk # 186808) The Device time-out parameter is deprecated from the Work Load Management properties file that was globally applicable. This was not the optimal option because the processing time of automations varies for different queues.
Enterprise Client deprecated features
Feature Description
User interface language selection French language is deprecated for the Enterprise Client user interface. Now, you cannot select French in the setup file when you install the application.

Known limitations

Control Room known limitations
  • The connection to an Apache Ignite server of a Control Room cluster is automatically restored after the network is disrupted; however, the connection to the other server nodes is not restored and the servers appear disconnected.

    To ensure all the nodes are in sync, manually restart the Automation Anywhere Elastic Search Service from the Task Manager Services window.

  • It is recommended to delete a repository from the Visual SVN Server instead of deleting the default folder of the SVN repository in the Control Room that is enabled for version control.
  • Bot Store integration -
    • The application creates a Bot Store sub-folder under My Task folder in the Control Room repository after installation. When you upgrade to the current version and if the Bot Store sub-folder already exists, the installation fails as duplicate folders are not supported. To overcome this issue, you can follow these steps:
      1. Before you upgrade, run a database query:Update AAFILE set name='Bot Store_11_3_3', path = 'Automation Anywhere\My Tasks\Bot Store_11_3_3' where path = 'Automation Anywhere\My Tasks\Bot Store' and is_deleted = 0
      2. Upgrade Control Room to Version 11.3.3 using the setup file.
      3. Run the database query on the upgraded Control Room database:Update AAFILE set is_deleted=1 where path = 'Automation Anywhere\My Tasks\Bot Store' and is_deleted = 0 Update AAFILE set name='Bot Store', path = 'Automation Anywhere\My Tasks\Bot Store', created_by=0 where path = 'Automation Anywhere\My Tasks\Bot Store_11_3_3' and is_deleted = 0
    • Dependent files from the My Docs, My Exe, and My Script folders are not included as manual dependencies in the bots that are accessible from the Bot Store. This means that the Manual Dependency API is also not supported.

      To include the dependent files for bot deployment, add the files in the Bot Store folder when you create a bot that is to be uploaded to the Bot Store.

    • Pagination is not available in the My Downloads page in the Bot Store tab.
  • When you migrate a custom role to Version 11.3.3, and this role is granted permission to the My Tasks folder, the permissions are not applied to the Bot Store folder.
  • When you refresh the Download to my bots page, the name of the bot you are downloading disappears and the Download to my bots option is disabled.
  • If you have set a production version to a parent bot and did not set the production version on the child bot, the protection type status of the child bot and the bots within the child bot is not displayed even if they are protected.
  • The progress status for a Repeat scheduled event is intermittently captured on the In Progress Activity screen. As a workaround, you can refresh the page.
  • If you delete any bot, the historical data associated with that bot is removed.
  • The Folders on the Bots permission page need to be collapsed and expanded manually when you are in the process of creating a role to ensure newly uploaded child level folders that are added concurrently by other users can be viewed under the parent folder and included when assigning the Bot level permissions.
  • To export the migration details to a csv file, use the Export details... button given at the row level for single migration record from the main Migration page instead of the Export details... button on the View migration page.
  • Maximum 200 Active Directory (AD) groups can be mapped to user roles in the Control Room in this version. Also, you can search for the AD groups that are present in the user Organizational Unit (OU) only and not in other OUs.
  • You cannot install a bot directly in the Control Room if the bot was created in a version earlier than Enterprise Client Version 11.3.3 and was downloaded from the Bot Store. To install the bot, download and install the MSI file on the Bot Creator machine and then upload it to the Control Room.

Enterprise Client known limitations

  • Bot Store integration - Dependent files that are either not referenced from the correct folder or missing from the physical location show the Protection Type as follows when you upload to or download from the Control Room:
    • Protection Type column is displayed.

      If you are uploading or downloading a task that has dependencies and is available within the Bot Store folder.

    • Protection Type column is not displayed.

      If you are uploading or downloading a task that has dependencies and is available outside the Bot Store folder.

  • You cannot capture objects based on Flex, Java, and Silverlight technologies from Google Chrome.
  • Terminal Emulator command -
    • For the ANSI or VT Series terminal type with Advanced Technology, when you use the [Enter] key, the bot execution moves to the next command before the next screen appears. It is recommended that you split the text and key in two separate Send Text commands in your Task Bot.
    • For ANSI terminal type, an additional row is displayed with Advanced Technology as compared to the Legacy technology.
  • If the 'Object reference not set to an Instance of an Object' error message appears when you open the Workbench for the Enterprise Client that is installed on the Google Cloud Platform, you must reinstall the same Enterprise Client after uninstalling it to fix this issue.
  • GUI Automation command -
    • You cannot use wildcard characters to specify the title of the SAP window from which you want to capture an object.
    • After capturing an object from the SAP window, the focus does not shift back to the Enterprise Client. Click the Enterprise Client icon on the task bar to navigate back to the Enterprise Client.
  • In the Rest Web Service command, you might not be able to add the local variables and text with the other local variables in Request > Header using F2 after you have used the Credential Variable. In that case, clear the textbox that has the Credential Variable and then try to add any local variable.
  • Third party integration commands, such as SAP, Zip-unzip, PGP, Terminal Emulator, and Send Email in Automation Anywhere do not work optimally on a machine or a newly configured Virtual Machine (VM) that does not have the required Primary Interop Assemblies (PIA) redistributables. Typically, the PIA redistributables are automatically installed; however, they need to be separately installed if you did not install the Microsoft .NET Framework package before you installed Microsoft Office.
  • As a work around, copy the stdole.dll file to either of the following paths: 
    <your drive>:\Windows\assembly\GAC
    <Automation Anywhere installation path>\Client
    Tip: Copy the file from an existing <your drive>:\Windows\assembly\GAC of a VM or machine where Microsoft Office is installed. See https://docs.microsoft.com/en-us/visualstudio/vsto/how-to-install-office-primary-interop-assemblies?view=vs-2019.
  • The key reference in the dictionary variable removes round brackets ( and ) when inserting a new key value using the F2 key option, because of which an error message appears during the runtime. As a workaround, manually add the round bracket to the key reference after using the F2 key option.
  • The values of List variables in a Task Bot do not reinitialize when used within a loop with Repeat option of the Run Task command. To overcome this issue, add the child Task Bots multiple times in the parent Task Bot to reinitialize the values of the List variable instead of using the Repeat option. (Zendesk # 222885)

Bot Insight known limitations

  • The following widgets are not supported in the Bots Dashboard:

    • Bot Heartbeat
    • MVP Bots

  • The following widgets are not supported in the Devices Dashboard:

    • CPU Utilization
    • Memory Utilization
    • HDD Utilization
    • Upcoming Device Utilization
    • Failure Analysis
  • Use the following default port configuration to ensure that Bot Insight communicates seamlessly with Zoomdata:
    • Port 8118- Elasticsearch
    • Port 8291 - EDC (MSSQL/Oracle)

    See Configuring ports for Zoomdata.