Automation 360 v.22 Release Notes

Release date: 21 September 2021

Review what's new and changed, and the fixes and limitations in the Automation 360 v.22 release. Build 10535 is for Cloud and Build 10526 is for On-Premises. For Automation 360 IQ Bot, Cloud is on Build 10535 and On-Premises is on Build 10520.

Important: We have updated the Automation 360 Cloud build to include additional fixes for the Apache Log4j2 component vulnerability. The build includes the new Log4j2 library version 2.16.0.

Updating to this release

You can update the Automation 360 v.22 release from the previous three releases (that is, from n−3 releases, where n refers to the latest release).

The following previous releases are certified for update to this release:

  • v.21 (Builds 9664, 9642, 9595)
  • v.20 (Build 8815)
  • v.19 (Builds 8147, 8145, 8122, 8098)

You can directly update to v.22 from any of these builds. For details on how to update, see Update Automation 360 to latest version.

Recommendation: If you are not on an n−3 release, update Automation 360 to one of the three certified releases before updating to this release.
Important: This release includes a required update to your Bot Agent. Ensure that you complete the update to continue with your automation activities when upgrading from a previous release to this release.

Automatically update the Bot Agent | Manually update the Bot Agent

To verify which Bot Agent version is compatible with this release, see Compatibility with release builds.

For information about the latest updates to the Automation 360 extensions for Google Chrome, Microsoft Edge, and Mozilla Firefox, see Browser extensions for Automation 360.

Migration features

Enterprise 11 and Enterprise 10 features
Migrate bots that use Credential variables (Service Cloud case ID: 00705937, 00761271, 00776189)

You can now migrate bots that use Credential variables that are not available in the Cloud Control Room. However, you must create the required credentials after migration in the Credential Vault and use them in the migrated bots to run these bots successfully.
Migration support for Browser, Java, and Java Applet applications for App Integration command

You can now migrate bots that contain the App Integration command with application types such as Browser, Java Applet, and Java applications.
New Action Required tab in Bot Scanner report

In the Bot Scanner report, we have introduced the Action Required tab within the Bots that can be migrated now section to provide advance notification about bots that require manual intervention after migration so that they can run successfully in Automation 360. View messages associated with the bot that requires action to understand the cause and the specific action you must perform in Automation 360.

Analyze Bot Scanner report for migration

Action required, Review required, and Error messages for migration
Migration messages are now classified into the following categories: Action required, Review required, and Error messages:
  • Action required and Review required messages are displayed for bots that contain unsupported commands but which you can still migrate and run after migration by performing specific actions. The messages provide specific actions you have to perform or information that you have to review to ensure that these bots run successfully after migration to Automation 360.
  • Error messages are displayed when a specific bot is not migrated successfully. The messages also include the cause for the failure.

Migration messages

Enterprise 11 only features
Migrate bots with the following attributes:
  • Bots with timeout specified in their property
  • Bots that contain the GUI Automation command with the Restore Window or the Execute Script option selected
  • Bots that open a session for Terminal Emulator and Microsoft Excel in the parent bot and close that session in the child bot
  • Bots that automate email-related tasks on Microsoft Exchange 2013
  • Bots that use SAP BAPI standard and custom workflows to automate tasks on SAP applications
  • Bots that contain the Window command with the Close All Open Windows selected to close all multiple active windows (Service cloud case ID: 00773227)

Automation Workspace

What's new
Save bandwidth on devices through preloaded offline bot packages

Customized or most commonly used bot packages in a bot are now saved offline on a user device to the following new folder: AAPreloadedPackages. When a bot is deployed on a user's device, the packages are used from this AAPreloadedPackages folder instead of downloading them from the Control Room.

When a specific version of the package is available, you can download it from the Control Room repository to save the time required to download the package during bot execution.

Preload packages | Devices

Introducing Text file package

A new Text file package is now available and includes the Get text action. Use this action to extract text from files that have Japanese characters with Shift-JIS encoding and then save the content in the files to a string variable.

Text file package

New actions in Window package
  • Use the Close all action to close all windows or programs running on the system, except the windows added in the Add window field.
  • Use the Restore action to restore the size of a maximized or a minimized window or application running on the system.

Window package

Share session across bots

Share a DLL, Excel, and Terminal Emulator session across multiple bots using the Global session option. You can also share a session with specific child bots using the Variable option and share a session with only the current bot using the Local session option.

Sharing sessions across bots

Enhancements to Excel advanced package
  • Open files with .xml and .txt extensions using the Open action.
  • Use the wildcard character (*) in the Open action for file names to search based on the wildcard pattern.
  • When you use the Run macro action and specify an argument that has a blank value, this blank value can now be passed to the macro.
New option in Database: Disconnect action

In the Database: Disconnect action, you can now use the Keep database schema in cache until bot finishes running option to enable the Loop action to iterate the dataset by using cached schema after disconnecting from the database.
TNS name supported for Oracle Database connection

TNS (Transparent Network Substrate) name is now supported in the Oracle Database. You can connect to the Oracle Database by specifying the TNS name and path of the tnsnames.ora configuration file.
New Exchange version supported in Email package

In the Email package, when you choose an EWS server to establish a connection, you can now use the Exchange2013 option in the Exchange Version field.
Enhancement to AISense Recorder

AISense Recorder now enables automation of applications that use Russian and a combination of Russian and English interfaces.

AISense for recording tasks from remote applications

Enhancements to recorder conditions for packages
  • Use the new Object does not exist condition from the Condition list of any package to verify whether a specific object in a window exists and then execute actions based on the result.

    This condition works with SAP technology as well.

  • The existing Object condition is now renamed as Object exists.

Loop package

Enhanced support for SOAP Web Service URI (Service Cloud case ID: 00759811)

In the SOAP Web Service package, if the input to the Address location field is empty, the bot now retrieves the address location from the WSDL file.
New option in SOAP Web Service package

Use the Build SOAP request option in the SOAP Web Service package to retrieve SOAP request details from the SOAP URI or the WSDL file. You can now select any operations from the list of services and ports available in the SOAP Request to automatically populate data in the fields of the SOAP Web Service action.

Example of using the SOAP web service action

New option in REST Web Service (Service Cloud case ID: 00764198, 00800287)

In the REST Web Service package, you can now use the Allow insecure connection when using https option to skip SSL certificate validation and to allow non-secure connections.
Relative click and occurrence supported in packages (Service Cloud case ID: 0055643,00754173)

When you capture a target image using the Image Recognition package, you can now use the Preview option to select a specific captured occurrence and position your click location relative to the image.

The feature is supported in the following packages and actions:
  • Image Recognition > Find image in window
  • Image Recognition > Find window in window
  • If > Image Recognition condition
  • Loop > While > Image Recognition condition
  • Wait for condition action > Image Recognition condition

Using Find image in window action|Using the Find window in window action

Wait time option in Google Sheets package (Service Cloud case ID: 00738249, 00817449, 00814775)

When you use the Connect in the action in the Google Sheets package to establish a connection with the Google server, you can now set a wait time in the Wait for actions to complete field when performing actions such as Get, Set, or Delete. For example, if you have a large file that takes a long time to open, you can now set the wait time for the file to open before the system executes the next set of actions.

New option for Put action in Dictionary package

You can now assign a static value to a key for a dictionary variable by using the Static value option in the Put action in the Dictionary package.

Dictionary package

Java applications supported in App integration package

The App integration package now supports Java applications that are based on the Standard Widget Toolkit and Abstract Window Toolkit, which can draw text using Windows text-drawing APIs.
Use regular expressions in File > Open action (Service Cloud case ID: 00737614)

Use regular expressions (regex) in the Open action of the File package to support pattern-based search.
Specify timeout for bots (Service Cloud case ID: 00667049, 00690892, 00699158, 00706491, 00739420, 00739415, 00741590, 00769795)

You can now specify the amount of time by which the execution of a bot must be completed. The system stops the bot execution if it is not completed within the time you specified.

Configure timeout for bot execution

New option to search text within bot content in Bot editor (Service Cloud case ID: 00735685, 00736201, 00739122, 00740481, 00733885, 00748970, 00746459, 00738181,00756441,00759037,00761453,00764478)

In the Bot editor, use the search box in the Flow, List, or Dual view to search for text, variables, or actions in the entire bot content such as package name, action name, string name, or variable name. This feature helps you to view or edit a bot with long code lines to determine where the searched text, such as variables, strings, or actions, is used and in which line.

Actions to build automations

Enhancements to the bot structure

We have enhanced the overall readability of the bot structure and updated the node labels of the bot to show selected properties and parameters of each action in detail in the Flow, List, and Dual views. You no longer have to expand each action to view these details.

The Flow, List, and Dual views display the following properties of actions:

  • The value you enter for actions such as Set text for all supported technologies
  • Names of objects on which actions such as Set text, Click, Left click, Get property, and Select item by index are performed
  • Name of the object property mentioned in the action
  • Name of the return variable if some value is assigned to a variable
  • List of properties for the Get property action
Enhanced network security control

As a Control Room administrator, you can now configure and audit specific, permitted URLs for more granular control of the network access points.

Set callback URLs

Enhanced proxy support

Connections to the internet are often run through proxy servers. Automation 360 provides enhanced support for proxy configuration for packages, such as REST and SOAP packages, for building and running bots.

Connect Bot Agent to a device with a proxy

Connect to Azure DevOps (Cloud) Git from Control Room

You can now connect to Azure DevOps (Cloud) Git through the Control Room to check in a bot and its dependent files to the remote Azure DevOps (Cloud) Git repository.

Connect to Azure DevOps Git from Control Room

Work item ID and time filters for workload automations

Combine the work item ID and start time of a queue to search for specific work items and monitor the progress of these work items. The start time filters the list of all work items that start between specified start date and start time.

Actions allowed on view queue page

Enhancements to execution type key in AATaskExecutor variable
  • When you schedule a bot to run, the Execution_Type key in the AATaskExecutor variable now returns information about the execution type with schedule type (frequency) such as Run as schedule Daily, Run as schedule Weekly, or Run as schedule Monthly.
  • When you use a trigger in a bot, the Execution_Type key can be accessed through the trigger data. The Execution_Type key returns the Run through Trigger as a string for triggers.
Language support for variable names

Variable names now support Greek and Japanese languages. You can now create variable names using the following characters:

  • Greek uppercase and lowercase characters
  • Japanese Katakana full-width and half-width characters.
ML services support in Linux package installer

The python package in the Linux installer package is now updated to support ML services. When you download and install Control Room on Linux, ML services are up and running as part of the installation process.

Installing Control Room on Linux | Stop and start Control Room services on Linux

Direct download support in Bot Store

Users who cannot connect their Control Room to the internet can now directly download Automation 360 bots and packages locally from Bot Store and then import them to their Control Room.

Download locally and import bots and packages from Bot Store to Control Room

MS-SQL database management enhancement

Administrators are no longer required to re-install Automation 360 to have the ability to change MS-SQL configuration related settings. The editable settings include username, password, database server name, database server IP and port numbers.
What's changed
Changes to Runtime Window

The title on the Runtime Window is now changed to Bot running from the previous Automation Anywhere.

If any issue occurs in your automation due to this title change, see this article on how to resolve it: A360.22 | Runtime Window: Minimize Command Fails Due to Title Change (A-People login required)

Changes to Run DLL package
  • The Run function (Legacy) action is no longer available in the Run DLL package. We recommend that you use the Run Function action from the Run DLL package because this action is an improved version of the Run function (Legacy) action.

    Note that existing bots that use the Run function (Legacy) will continue to run successfully without any issues.

  • The Set session variable action is no longer available in the Run DLL package. Instead, we recommend that you create a new DLL session using the Variable option in the Open action of the Run DLL package.

    Note that existing bots that use the Set session variable action will continue to run successfully without any issues.
Messages for migrated bots for which referenced MetaBot logic is not available

Bot Scanner and Migration Assistant now display action required messages for Enterprise 11 or Enterprise 10 bots for which the referenced MetaBot logic is not available.
Migration of bots with missing variable is blocked

The migration process does not migrate Enterprise 11 bots that use a variable which is no longer available and that variable is used in the If, Loop, Variable Operation, or Clipboard command. Previously, these bots were successfully migrated but an error occurred when the bots were run.
Update to MetaBots that use same DLL in multiple logic (Service Cloud case ID: 00684185, 00730248, 00742840, 00742840, 00779629, 00779788, 00727977, 00743986, 00764872)

Migrated bots that use the same DLL in multiple MetaBot logic now work as expected without any modification. Previously, you had to update the migrated bots to run them successfully.

Migrated bots run successfully when mapped variables are not available (Service Cloud case ID: 00746651, 00785703)

Migrated bots now run successfully when mapped variables are not available in the child bot or the parent bot.
Enhancements to Bot Agent device settings
To easily access local and remote devices, a user can now change the Bot Agent device settings from the My Settings page in the Control Room pane below your username. You can perform the following actions:
  • Update device credentials
  • Change the default Bot Runner device
  • View local device name, status, and Bot Agent version

Set user device credentials | View and update Bot Agent device settings

Enhancement to auto discovery for multiple domains

You can now configure the maximum number of sites that can be discovered across the domain in the um.properties file for a Control Room set up for auto discovery across multiple domains in different locations.

Configure Control Room for Active Directory: auto mode

Enhancement to OpenDistro for Elasticsearch

As part of enhanced security, OpenDistro (cron-utils) is now upgraded to v.1.13.2 for Elasticsearch v.7.10.2

Update to Printer package

In the Remove and Set default actions of the Printer package, you can now select a specific printer from the list of available printers.

Printer package

Insert recorded actions in the middle of a bot

You can now insert any recorded actions that are newly captured at a specified location in an existing bot. Previously, recorded actions were added to the existing bot at the end by default and users had to drag the action to the specified location.

Universal Recorder for object-based automation

Migration: system variable behavior outside a loop (Service Cloud case ID: 00761281)

When you migrate bots that use system variables outside a Loop package, the variables are now converted to record type or string type user-defined variables as applicable and assigned to a record action. As a result, when bots that contain these variables are run, data from the last row is displayed. Previously, an empty value was displayed after migration.

The following system variables are converted to record type variables:

  • $Filedata Column$
  • $Excel Column$
  • $Dataset Column$
  • $Table Column$

The system variable $XML Data Node$ is converted to a string type variable.

Variable mapping for migration

Support removed for Redirect URI attribute in Google Sheets package (Service Cloud case ID: 00777287)

The Redirect URI attribute in the Connect action of the Google Sheets package is now removed. After updating to this release from previous Automation 360 releases, you can continue to successfully execute your bots by entering the fixed redirect URL in Google Cloud Platform: http://localhost:8888/Callback

Updates to device credentials recorded in audit log (Service Cloud case ID: 00691511)

You can now view audit log entries if your device credential is updated either manually through the Bot Agent device or through the Control Room API. Activity details such as the user name updating the device credentials and the time of the update are logged.
Enhancement to Image Recognition package

When secure recording is enabled, the target image that is captured using the actions in the Image Recognition package is now hidden after the initial capture to enhance security. Previously, the user was able to view the target image even when secure recording was enabled.

Image Recognition package

Enhancement to File and Folder package

Users with a valid role permission can now create a shortcut to a selected source file at a specified location using the Create shortcut action in the File and Folder package.
Support for HTTP method HEAD (Service Cloud case ID: 00754096)

The HTTP method HEAD is now supported as an API call to connect to the load balancer of a Control Room configured for high availability.
Update to Linux installation and log path
  • Installation files
    • If you are on a version earlier than Automation 360 v.22 or if you have updated from an earlier version to v.22, the installation files are now stored in this path /opt/automationanywhere/enterprise
    • If you perform a new installation of v.22, the files are stored in this path: /opt/automationanywhere/automation360
  • Log files
    • If you are on a version earlier to v.22 or if have updated to v.22 from an earlier version, the log files are stored in this path: /var/log/automationanywhere/enterprise
    • If you perform a new installation of v.22, the log files are stored in this path: /var/log/automationanywhere/automation360
Check out a Task Bot with specific version

If a bot has multiple versions, you can now select and check out the specific version of the bot. As a Bot Creator, this enables you to roll back to an earlier version of the bot.
Signed DLLs for bots and packages

Automation 360 now signs all DLLs, including third-party DLLs, for bots and packages.

The following are exceptions:
  • The IQ Bot Pre-processor package does not have a new version in this Automation 360 v.22 release. The v.21 package version is copied to v.22 without modification, including a few unsigned DLLs.
  • The Process Discovery package in this v.22 release does not have the signing applied.
  • Automation Anywhere
  • Azul Systems (Java JRE in Bot Agent)
  • TeamDev Ltd. (third-party library)
Fixes
Service Cloud case ID Description
00712808, 00765752 In previous releases, Automation Anywhere related files were sometimes generated in C:\Windows\Temp. This issue is now fixed.
00800392 An error no longer occurs when you migrate from a Enterprise 11 version where a database is stored on Google Cloud Platform.
00811887 The Cloud Migration Utility no longer encounters an error when you use a custom port number to connect to the Enterprise 11 database.
00815097 Enterprise 11 bots that are checked out by a user are now successfully migrated to Automation 360 Cloud.
00802360 You can now update the value of Enterprise 11 credential attributes after they are migrated to Automation 360 Cloud. Previously, the system encountered an error when you updated the value of a credential attribute that was added or updated by a user in Enterprise 11 and that user was no longer available when Enterprise 11 data was migrated to Automation 360 Cloud.
-- When you migrate from Enterprise 11 to Automation 360 Cloud, an error no longer occurs when a locker is deleted in Enterprise 11 but its related permissions are still used in other entities.
-- An error no longer occurs when you update from Version 11.3.5.2 to any Enterprise 11 version and then migrate from that Enterprise 11 version to Automation 360 Cloud.
-- The Refresh and Back options are now available on the Summary screen of the Cloud Migration Utility when enough disk space is not available to store the backup of Enterprise 11 Control Room data.
00787240, 00781349 Migrated bots no longer encounter an error when a parent bot and its child bot are opened through Internet Explorer and the child bot extracts a table from Internet Explorer.
-- There is no limitation now on the number of ActiveMQ connections that are allowed when running an automation that is looped 5 times, with each loop running over 20 bots. In previous releases, the automation sometimes failed after the fourth loop.
0074312 You can now successfully migrate bots that contain Trim operation of the String and the output is assigned to an Array variable.
00760963 Migrated bots that contain the Go To Cell command now work properly in Automation 360 after migration.
-- Bot Scanner now loads the modified cache.properties file from the conf folder. Previously, you had to place the modified cache.properties file in the executable file location of the Bot Scanner for the file to be loaded.
00754003 Bots that contain the SOAP Web Service command now successfully run after migration without encountering any error. Previously, an unexpected error occurred when the SOAP Web Service with WSDLs defined with external dependencies were not invoked.
00790360 In the Terminal Emulator package, when you send any key to the terminal with the Send text or Send key action, if the terminal is in a busy state or the keyboard is in a locked state, these actions now wait for 5 seconds for the terminal to return to a normal state. After 5 seconds, the system moves to execute the next action without any exception.
00742000 Migrated bots that contain the Prompt > For value command with the Don't write in any windows option selected now work as expected in Automation 360 after migration and no text is written in the file if any window is open. Previously, even if this option was selected, if any text file window was open, the text was written in the file.
00781072 When bots are migrated using the Bot Migration Wizard, migration no longer fails if the bot name includes a special character. Previously, an internal error occurred when the bot name included an apostrophe (') character.
00780713, 00778164 A migrated bot is no longer unresponsive when that bot uses the App Integration package to capture text from a target application and the target application becomes unresponsive.
-- Migrated Enterprise 11 bots that use the Terminal Emulator command to clear the terminal screen of the VT and ANSI type terminals no longer encounter an error when they are executed.
00748647 Migrated Enterprise 11 bots that use two-dimensional array and the Variable Operation command no longer encounter an error. Previously, the migration process used to set the number of rows and columns for the two-dimensional array to 1x1 irrespective of the values set in Enterprise 11.
-- The migration process continues to migrate bots if the connection between the Control Room and the Bot Agent is lost and then reestablished. Previously, the migration process failed when the connection between the Control Room and the Bot Agent was lost.
00764441 In the Excel: Get single cell action of the Excel advanced package, you can now access the value of a specific cell defined in the cell address. Previously, migrated bots encountered a Must match pattern error when a Japanese character was entered in the Cell address field.
00757713, 00764985, 00820376 The Excel advanced package now enables you to read from a protected sheet. Previously, migrated bots encountered an error when you retrieved a cell from a protected sheet using the Excel advanced: Open action.
00761911 You can now migrate bots using the Excel column system variable where the key is the column name; an error is no longer encountered.
00769321 Migrated bots no longer encounter an error when the Run Excel Macro command is included in the bots. Migrated bots now run properly using the Run macro action of the Excel advanced package.
00790858 You can now migrate a bot when there is a variable mismatch and the respective command is disabled. Previously, when the bot was assigned a certain variable type and the Variable Operation command in that variable was disabled, Bot Scanner displayed an error for the variable when the type was later changed.
00744318, 00744326, 00745318 You can now download an exported bot file with Japanese characters in the filename through email. Previously, when an exported file with a Japanese name was downloaded using the email link, an error occurred or the characters in the exported zip filename were garbled and .zip was appended to the filename.
00762975 After you migrate Enterprise 11 bots that use the Error handling command with the Send email function and the Attach variable and Attach snapshot option, the bots now correctly send error emails with attachments containing a snapshot or variable text file.
00731577, 00746226, 00760649, 00759973, 00767618, 00789545, 00821824 The includePackages parameter of the Export API now works as expected. If you set the value of the parameter as True the packages are included in the exported file, and if the value is set to False the packages are not included in the exported file.
-- You can now migrate bots with variable names that include full-width and lowercase characters. Previously, migration of bots with a variable name that included full-width and uppercase characters was not supported because the variable was mistakenly converted to a half-width character.
00759189 Migrated bots now use the date format specified in the AADefaultDateFormat global value for email-related automation. You must create the AADefaultDateFormat global value before migrating the bots and specify the date format you want to use in the migrated bots.

Recommended: Specify the same date format in the AADefaultDateFormat global value that is used in Enterprise 11.
00784001 Enterprise 11 bots that are migrated now contain all the properties of an object captured from a SAP application.
00786362, 00802274 Enterprise 11 bots that are migrated no longer encounter an error when the child bot and parent bot use different versions of the If package.
00807986 Enterprise 11 bots that are migrated no longer encounter an error when a variable that is mapped between a child bot and the parent bot is not available in the child bot.
00808026 Enterprise 11 bots that are migrated no longer encounter an error when they use a shared session for Terminal Emulator related tasks when a session is shared between nested child bots and an intermediate child bot does not contain any Terminal Emulator actions.

For example, consider that you have three bots: Bot1, Bot2, and Bot3, where Bot1 calls Bot2 and Bot2 calls Bot3. Bot1 and Bot3 share a session for Terminal Emulator related tasks; however, Bot2 does not contain any actions from the Terminal Emulator package. When you share a session between Bot1 and Bot3, an error is no longer encountered.

00762368 Previously, when bots were migrated using Oracle database processes with passwords containing the symbol, an issue occurred. The issue is now fixed and passwords using the “@” symbol are now supported.
00768466, 00769099 An error no longer occurs when you migrate MetaBots that contain logic that are available within a folder.
00772885 The system now retrieves all rows in a table in a SAP application when the last page of the table contains a single row.
00801733 An increase in CPU usage no longer occurs when the Control Room is in an idle state.
00774821 An error no longer occurs when you run migrated bots that contain a Loop action within another Loop action.
00786732 For Enterprise 11 bots that use the Extract Table command along with other commands within the Error Handling command and only the Extract Table command is disabled, only the equivalent action for the Extract Table command is disabled after migration. Previously, all the actions within the Error Handling action were disabled in the migrated bot.
00743892 An error no longer occurs when you run migrated bots that use DLLs that return a value of user-defined type. Such values are converted to the string type in the migrated bots.
-- Enterprise 11 bots that use variable operations to re-initialize an array type variable to contain more than 160,000 cells (for example, 400 rows and 400 columns, or 800 rows and 200 columns) no longer encounter an error when they are executed after migration.
00737025 Enterprise 11 bots that pass system variables such as Month, Year, and Day as an input variable to a MetaBot no longer encounter an issue after they are migrated.
00773407 Previously, historical activity reports exported to CSV did not display the Last Modified information correctly because some of the Modified On and Modified By information was not accurately processed. The error is now fixed and historical activity reports can now be correctly exported to CSV files.
00767597 The Last Modified (date) value displayed in the historical activity and bot page reporting was previously not translated correctly when the Control Room language was changed from English to non-English, and then back to English. This error is now fixed, and the data is preserved when the language is changed in the Control Room.
00762975 Japanese language text is now updated in the interface for recent user experience (UX) changes. Previously, there were some errors in the translated text in the interface, which are now fixed.
00763228, 00776154 Database constraints, such as foreign key constraint violations, previously prevented users from deleting bots after migration. This limitation is now fixed and users can delete migrated bots (.atmx files) without any issue.
00749375,00763262 After migration, if text file encoding was set to UNICODE or UTF8, you can now use the String: Import string from text file key to read values from the text file during bot runtime.
00739268 You can now migrate bots that have large html data associated with the Object Cloning command without any issues.
00674147, 00682390 The Stop service action of the Service package now enables you to stop all child and dependent services of a selected window or application. Previously, the dependent service did not stop automatically when a user tried to stop any window or application service.
00754835 Temporary devices are now automatically deleted if the auto-delete option is enabled for device settings in the Control Room.
00751058, 00761099 When you use the Database Connect action for workload automation, work items from the second iteration are now executed for automation. Previously, only the first work item in the workload automation was executed.
00771098 After you edit a schedule from the Scheduled activity page and save the schedule, the correct page (Scheduled activity) is now opened instead of the In progress activity page.
00733614, 00741358 You can now use the Extract image action of the PDF package to convert a PDF file that contains JPX images to any other image format. Previously, the action failed to extract image from the PDF file because the JPX image reader was not supported.
00765851 Recorder actions now work properly and do not cause any delay when the Set text value contains brackets or [] (which enables you to run a migrated bot without delay). Previously, it took a longer time to run the bot when Set text contained [] (brackets).
00771197 In the Open action of the Browser package, the description below the Time out after (seconds) (optional) field is now translated correctly as Min= 9 seconds in the Japanese language. Previously, the description was translated as Max= 9 seconds.
00761395 In the Database package, when you connect with the Oracle Database and use the Read from action option in a loop to retrieve records from the database, the bot is now executed successfully. Previously, bot execution failed with an error.
00727530 The Move all action in the Email package now works properly and does not encounter any issue.
00739978 An error no longer occurs when you choose the Manual input option to open a VB Script file.
00728180 The issue with event triggers when creating folders in bulk is now resolved. If you configure an event trigger to start a bot whenever a folder is created and then create folders in bulk, the bot is now deployed for every folder that you create. Previously, the bot was not deployed for all the folders created.
00711134, 00750164, 00847916 If you configure multiple triggers to start bots based on file events and if all the files reside in the same folder, the bots associated with all the triggers are now deployed. Previously, only some bots were deployed.
00719612 When you log in to the Control Room as an unattended Bot Runner, you can now execute bots using the Run as self option. Previously, an unattended Bot Runner could not run the bot with the Run as self option even when the device was set as the default device.
00745095 In the Database package, when you connect to the Microsoft Access database using the JDBC connection, the select query now extracts the file name for the Attachment data type. Previously, an error was displayed.
00772194 Data from any database type is now exported correctly in CSV format. Previously, if the data had special characters such as double quotation marks, the output was displayed in a new line.

00773961

 When you create a new worksheet by name in the Google Sheets package, an error no longer occurs when you execute the bot.
00762029 An error no longer occurs when you execute a bot using the Google Calendar package. Previously, when the Disconnect action was used to terminate the connection, the email address attribute was stored in the session name instead of the user session name attribute. As a result, bot execution failed with an error.
00758333 If all versions of a particular package are disabled, then the package is no longer listed in the Actions palette of the Bot editor.

Previously, when a package was disabled, the Bot Creator still displayed it in the Actions palette and users were able to use the package when creating a bot. However, these bots failed on execution because the package was disabled.
00780221 A bot created using the Run function action in the Run DLL package now executes without any issues. Previously, an error was displayed on bot execution due to the unavailability of some embedded resources such as satellite assembly.
-- An error no longer occurs when you create a bot using the Send text action of the Terminal Emulator package and pass a variable with an empty value. Previously, the bot failed to execute when any variable options (Credential, Variable, Insecure String) that had no value was selected.
00776430 When you connect to the Terminal type TN3270E in the Terminal Emulator package, select any of the Terminal model options from the list, and execute the bot, the correct screen resolution is now displayed. Previously, a wrong value was sent for each Terminal model and a screen with incorrect resolution was displayed.
00773415, 00781487 When you open a spreadsheet in the Google Sheets package and select the Beginning of the row option in the Go to cell action, the output is now displayed correctly. Previously, the output was displayed at the column level.
00773415, 00781493 An error no longer occurs when you open a new or blank spreadsheet in the Google Sheets package and you select an action such as Go to cell or Set cell to perform an operation. Previously, bot execution failed with an error.
00779561 In the System package, when you use the Get environment variable action in view mode, the environment variables are now always displayed in the list. Use the refresh option to retrieve all the environment variables in the list. Previously, the environment variables were sometimes not displayed in the list.
00775073 In the Excel advanced package Get worksheet as data table > Read option, the description for the Read cell value option now reads correctly as 50% will be read as 50 when it is translated to the Japanese language. Previously, the description was translated as 50% will be read as 50%.
00767246 The SOAP Web Service package now works for URIs, where the service endpoint can be passed as a URI parameter. Previously, an error was displayed for such requests.
00734463, 00754570, 00766456 When the Connect action of the Database package is used to establish a connection with the Microsoft SQL Server using Windows authentication, the bot now executes successfully even when the parent and child bots use different versions of the Database package.

Previously, the bot failed if the parent and child bots used different versions of the Database package.
00780921 An error no longer occurs when you use the PDF extract text action to extract text from a PDF file. Previously, when structured text was extracted from a PDF file, an error was displayed because the index exceeded the 1000 range.
-- In the Excel advanced package, when you use the same session name to open multiple Excel spreadsheets, the bot now displays an error on execution. Previously, if the same session name was used in multiple spreadsheets, the bot overwrote the existing open session when the second Open action was executed.
00785198 In the Data Table package, when you now use the Write to file action to extract data from a table with large records, 1000 rows of data are read in batches and written to a CSV file.

Previously, a Java heap space error was displayed because the configured Java heap memory ran out of space. As a result, data could not be retrieved from a table with large data and written to a CSV file.
00757593 In a Cloud deployment, child bots can now be migrated using the Migrate Bot action from the Bot Migration package. Previously, child bots were not migrated but a migration successful message was displayed.
00731012, 00747385, 00746320 If you install the Control Room in the default location in C:\ and configure the logs directory in another location (for example, E:\), WebCr logs are now generated dynamically in the custom location.
00768318, 00760835 An error no longer occurs when you try to capture objects using AISense Recorder on any version of Windows that does not have the default media feature pack. Previously, the AISense Recorder did not highlight the objects on a page.
00737710 In the Capture action of the Recorder package, when you select the Set Text action and enter a string variable with a delay set for each keystroke, the output is now displayed correctly on a new line for all Microsoft applications. Previously, on bot execution, the output was shown on one line when a delay was set in the Keystroke.
-- If you deploy bots using event triggers and you install the Bot Agent on a device as a non-admin user for self or a local admin user, the Bot Agent is now updated automatically. The device is no longer shown as disconnected in the Control Room.
00782596 You can now migrate workload automation bots from Enterprise 11 to this release. A client protocol exception message is no longer displayed.
00743810, 00785703 You can now map variables with different letter cases between parent and child bots when you run bots after migrating them from Enterprise 11 to this release. For example, if the variable name in Enterprise 11 is Var1 and the variable name is changed to var1 after migration, you can map the variables and continue to run the bots.
-- Bot deployments on Bot Agent devices no longer fail when you close a terminal window using the close Window action from the Window package or manually close the Terminal Emulator window.
00767587 You can now run bots from the In progress activity page. Previously, bots were stuck in the Pending execution state and as a result other bots did not run. You had to manually move the bots stuck in this state to the Historical activity page to run the other queued bots.
00789682, 00798933 You can now delete, reset, or place on hold workload automations because work items are no longer stuck in the ready to run status. Also, the following message is no longer displayed: Work item cannot be deleted in this state.
00720471 An error no longer occurs when you use the Recorder package to capture an object and perform the click action on the capture coordinates. Previously, when you captured the object properties and if the download bar in Google Chrome was open, object properties in the browser could not be captured.
00754651 In the If action of the If package, when you select any condition from the Condition list, and drag any other action inside the If action, the condition is no longer deleted from the Condition list and the action no longer disappears from the List and Flow view.
00768354 An error no longer occurs when you use the AISense Recorder in child bots when running them in a loop. Previously, when the AISense Recorder was used in a child bot and the bot was executed, external processes were not terminated, causing the system to run out of memory.
-- Previously, when bot migration was performed, the process sent various, occasionally multiple, email notifications to all existing Control Room users, even if the administrator had disabled email notifications. An option is now added to enable the administrator to disable email notifications when Credential Vault data is created during bot migration.
00762368 Previously, when bots were migrated using Oracle Database processes with passwords containing the “@” symbol, an issue occurred. The issue is now fixed and passwords using the “@” symbol are now supported.
-- Previously, during migration, a parent bot was successfully processed even if associated child bots did not exist. This created errors during runtime. In this release, if associated child bots do not exist for the parent bot, a message notifies the user of the required action before migration can continue.
00762975 Bots that used the Error Handling action to capture screenshots were incorrectly modified and appended as .PNG files. Migrated bots are no longer modified and appended in this manner.
00751496 Attended Bot Runner devices now show an improved time performance when running bots on Microsoft Edge browser.
00753673 When you run a migrated bot that contains the Excel Advanced > Delete cell > Specific cell option with comma-separated input cell values such as A1, B1, the migrated bot now runs successfully and displays the output correctly.
00736473 Fixed an issue where a migrated bot containing the Excel Advanced > Open action did not load the Excel add-ins even when the Load Add-ins check box was selected. Now, the Excel add-ins are loaded successfully.
00767917 You can now run bots with a queue on single user devices that were previously configured for multiple users.
00712719 An error no longer occurs when you run bots that contain actions from the Terminal Emulator package on your device. Previously, bots could not be run due to a synchronization issue with the terminal.
00753121 An error no longer occurs when you use the Convert excel to PDF action of the Excel advanced package to save a converted PDF to a shared network drive.
00763746, 00773924 When you select the Keystrokes action in the Simulate keystrokes package and enter a variable or static text containing half-width Japanese characters, the output now displays the correct Japanese characters. Previously, on bot execution, the output displayed incorrect characters.
00774872, 00807106, 00824486 When you use the Close action of the Browser package to close the last Chrome browser window, the last tab of a Chrome browser window, or all Chrome browsers, the bot no longer encounters an error. Previously, when the Close action was used to close the last Chrome browser window, the last tab of a Chrome browser window, or all Chrome browsers, bot execution failed because the Chrome communication channel was shut down.
00762178 When you deploy bots using RDP on unattended user devices configured for multiple users, a black screenshot is no longer captured.
00800573, 00796393, 00804854 When you select a run-as user to deploy a bot, you can add a Bot Runner user back from the list of Selected Bot Runners to the list of available Bot Runners on the Run bot now page.
00744929 When incorrect Git credentials are entered, the credentials are now hidden and not recorded in the WebCR_Commons.log file. Previously, incorrect Git login credentials were recorded and not hidden in the log file.
00751304 The error model in Swagger docs is now updated to display all the fields appearing in the API response body. Previously, there was a mismatch between the fields displayed in the API response body and the error model in Swagger docs.
00763398 An error no longer occurs when multiple Excel files are opened and you use the Run macro action in the Excel advanced package. Previously, an error was displayed when a macro was run with multiple sessions.
00759183 The Open action of the File package now opens any file using the default application set by the user. For example, if Microsoft Paint is set as the default application for all .jpg files, the action now opens these files without any error. Previously, bot execution failed with an error.
00750185 An error no longer occurs when you run a migrated Enterprise 11 bot containing the Object Cloning command even if it contains some Unicode 8964 characters in some of its properties. The bot now captures objects after migration without any error. Previously, the bot failed to capture objects after migration if it contained Unicode characters in its properties.
00774091 All object properties of the Object Cloning command are now migrated without any errors. Previously, bot execution failed with an error because the HTML ID and HTML name properties were changed after migration.
00796322, 00823082 When you insert a variable as a parameter in any action of a package, add additional text to this variable, save the bot, and then edit the name of the variable from the variable list, the additional characters added to the variable are no longer deleted.
00731066 The Capture action in the Recorder package now works properly, and you no longer encounter any delay when creating and running new bots to extract any data from a DataGridView control in certain UI automation applications.
00784177 A bot deployment error is no longer displayed when you edit and run a bot using Run bot now from the Bot editor of a Cloud Control Room.
00782307, 00787807, 00811404, 00788178 Bot deployments are no longer stuck in a queue and now display the error Picked at runtime after Automation 360 On-Premises is updated from the previous release to this release.
00786786, 00806775 You can now capture a single object using a recorder from Google Chrome browser, and the following message is no longer displayed: Error performing single capture.
00780202, 00798826, 00808779 When you deploy bots using RDP on unattended user devices configured for multiple users and you set the RDP screen resolution to 1366x768, the resolution no longer changes to 1368x768 during bot execution.
00769647, 00767674, 00773115, 00777239, 00778972, 00777752, 00792839, 00804603, 00806606, 00815687, 00829496 The View historical activity page now shows the correct run details of start date and time for bots that fail during execution.
Limitations
If you configure an external key vault in External Key Vault Integration and select the SQL authentication mode for database authentication in the Windows installer Database Server page to install Control Room (On-Premises), the installation fails, and the following error message is shown: Control Room database tables fail to create.

Workaround: Add the database credentials in the external key vault and use those credentials for database configuration.
The Task bots runs metric on the Home dashboard page of the Control Room displays the count as zero even if you have run bots from the same Control Room.
(Service Cloud case ID: 00837271) If you are migrating from Enterprise 11 with a database that has a large amount of repository data, the installation might fail. This issue occurs because Liquibase update for a few SQL queries is not completed during migration.

Workaround: Contact Automation Anywhere Support.
When you are installing the Bot Agent, if you run out of disk space and click OK on the Out of disk space window, the Bot Agent installation wizard might display the previous installer windows.

Workaround: In the Setup type window, click Cancel and relaunch the Bot Agent installation wizard.
(Service Cloud Case ID: 01021889) In this release, when you schedule or deploy a bot from the Control Room, you will not receive an email notification if the bot fails to run.
(Service Cloud Case ID: 00780635, 00791587, 00795559, 00795632, 00797130, 00797113, 00791783, 00765770, 00826805, 01859661) When you update from the previous release, schedules disappear from Control Room instances configured on a single-node or multi-node environment. In some cases, after the update, previously deactivated schedules disappear and are reactivated automatically.

Workaround: Divide large schedules into smaller schedules or reduce the schedule frequency.

  • Divide large scheduled automations into smaller schedules of two hours each. For example, divide an automation schedule that runs for a 12-hour period, such as 9 AM to 9 PM daily, into two-hour intervals, such as 9 AM to 10:59 AM, 11:00 AM to 12:59 PM, and 1:00 PM to 2:59 PM.
  • Reduce the schedule frequency to 10 minutes.
Migration of Enterprise 10 MetaBots with the password type variable with null value is not yet supported. To migrate successfully, provide a default value to the password variable when creating MetaBots in Enterprise 10.

When you attempt to log in to the Control Room configured with Active Directory, using the Log in with Windows option is not currently supported in this release. Selecting this option can generate a java.lang.NoSuchMethodError error.

Recommended: Enter the domain credentials directly.

(Service Cloud case ID: 00831886) As a Bot Creator, you cannot run bot tasks through the Automation Co-Pilot process. Although human tasks appear fine, the Activity page displays the In Progress state and seems stuck on the Waiting for user and/or device action.

Workaround: Remove the process discovery license - recorder from the Automation Co-Pilot Bot Creator user. Please refer to Automation Co-Pilot process discovery license assignment for more information.
You cannot use the Global session option to share a Microsoft Excel session using the Excel advanced package with the Loop package.

Alternate solution: Use the Get multiple cells action and save the data into a datatable variable. Then, use the Loop package with the Data Table option selected.
The migration process successfully migrates bots that contain brackets or [] but the process fails when you migrate the same bots again to migrate the delta changes even when the overwrite option is selected.

Workaround: Delete existing bots from Automation 360 that contain brackets or [] before migrating them again.
Users with the AAE_Bot Migration Admin role are not able to run migrated bots because the Run my bots and Create folders permissions are not available in this role. As a result, these users can start the migration process, convert the bots but cannot run the migrated bots.

Workaround: Create a custom role with the Run my bots and Create folders permissions and assign this role to the users with the AAE_Bot Migration Admin role.
When Enterprise 11 MetaBots that use a DLL that returns a two-dimensional array of type single as output and stores the value to a file using the Log To File command are migrated as Task Bots to Automation 360, these Task Bots encounter an error when they are executed.
Migrated bots that are used to automate tasks using RDP encounter an error when the DPI of the remote device is different from the current device.
Newly created Control Room users on Windows for On-Premises Google Cloud Platform VMs cannot change their password. The security questions option is not available on the Change password screen and as a result the Control Room displays an error when they try to save the password.

Workaround: Refresh the page and change the password again.

(Service Cloud case ID: 00770816) When you connect to an Exchange Web Services server, multi-factor authentication (MFA) must be disabled, including in all organizational level security policies where multi-factor authentication might be enabled. If multi-factor authentication is not disabled completely, users might encounter connection and or authorization errors.
Automation 360 does not support the Kibana version in Elasticsearch for which a privilege escalation error is shown in the Black Duck report.
The Bot Agent is not updated automatically from a previous release to this release when you perform different operations simultaneously such as running bots, configuring device settings in the Control Room, and updating the Control Room.

Workaround: Restart the Bot Agent from the Task Manager.
A file is not deleted when you execute the bot with the following sequence of actions:
  1. You use the CSV/TXT > Open action to open a .csv file.
  2. You use a loop action within another loop action to retrieve values from the .csv file.
  3. You use the CSV/TXT > Close action to close the file.

    Here, all the actions are using the same Default session.

  4. You use the File > Delete action to delete the file.

The issue (file is not deleted) occurs because the bot fails to close the Default session.
Bot execution can fail with an error when you execute the bot with the following sequence of actions inside a loop:
  1. You use the Browser > Open action to open a window.
  2. You use the Recorder > Capture action to capture required objects on the window.
  3. You use the Browser > Close action to close the window.

Workaround: Use the Window > Close action to close the window instead.
If you update the device information from the Administration > Settings > Devices page, only the first update is captured in the Audit Log page. Subsequent updates to the device are not captured.
When you register a new Bot Agent user device from the bot editor after creating and running a bot, the following message is intermittently displayed: Device is either disconnected or it needs to be upgraded.

Workaround: Click Run to deploy the bot on the new Bot Agent user device.
When you use the Universal Recorder to record multiple tabs in a SAP application, the Set text action in the Client control of SAP does not work because it is currently not supported.
When multiple users check in their bots simultaneously, some of the check-ins fail although Git is not corrupted and no data is lost.
When you use the 2.3.0-20210806-215200 version of the Recorder package to capture any control using HTML technology in Google Chrome or Microsoft Edge Chromium browser and run the bot, the bot might fail with the following error message: Unable to find control. Search Criteria did not match

Workaround: Use the 2.2.0-20210722-211132 version of the Recorder package instead.
When you try to automate any process in a Java application that is using version 11.0.8 of AdoptOpenJDK, the Recorder might not be able to capture the drop-down elements on the application.

Automation Co-Pilot (Automation Co-Pilot for Business Users)

What's new
Output variables support in Process Editor

The Output variables section in the process editor enables you to create a user-defined variable that can be set as an output to any process. This helps you pass the output from the child (sub) process, which was called in the Process Task, to the parent (main) process.

Display child process automation output

Select File element input supported for Create a Request action

The Create a Request action in the Process Composer package now supports passing input in the request creation forms for the Select File element. You can now use bots to create a request and upload or download files as input with the Select File element. These input files are uploaded to the storage service to be available for further processing in the request.

Detail view in Tasks page

The new Detail view option in the Tasks page provides better insight into individual tasks for better task management. The detail view previews each task in its respective request view page without opening another page, which helps organize and correspond your tasks with the available requests. Users can interact with their tasks as well.

Additional support for interface triggers on Google Chrome

You can use the following additional actions for interface triggers on the Google Chrome browser during bot runtime:

  • Hyperlink element: Click, Set focus, or Lost focus actions
  • Checkbox element: Select, cleared, Set focus, Lost focus, or Selection changed actions
  • Radio Button element: Select, deselect, Set focus, Lost focus, or Selection changed actions

Add an interface trigger

What's changed
Font size retained during bot runtime

When you create a form, the font size that you selected in the Formatting > Font size drop-down menu is retained on the form during bot runtime.
Cancel option in the process and team setup page

When a user edits a process or team in the Process setup and Process setup pages, the Cancel option replaces the previous X option to provide better clarity for the user to cancel the current page.
Fixes
Service Cloud case ID Description
00781358 You can now add bots with table variables that do not have a default value to a process without encountering any errors.
00791703 When you the use the desktop tray icon to open Automation Co-Pilot Desktop Assistant, dependent files are no longer displayed along with the application.
-- In the process editor, the Go To option now shows the Filter Task and Process Task options.
-- When you enter data in a form of your process that contains a hyperlink, the process data is no longer ignored and now works correctly.
-- When you use Process Task in the process editor, you can now use the Public folder option in the Select process file field.
-- In Bot Task and Human Task, when you select a box, the input is now accurately selected.
-- The Requests page is now correctly updated with the latest request events (such as completion of tasks) for users with an Attended license.
-- When you update to this release, a built-in scheduler now periodically checks for any disconnected or temporary devices and clears these entries.
-- When you open a form in the public folder, it cannot now be edited by changing the term View to Edit in the URL.
-- When a user logs in to Automation Co-Pilot Desktop Assistant, all the triggers associated with that user name are now available.
Limitations

Users cannot edit a form or process in a public workspace, they must check out a form or process in order to edit in a private workspace. However, when users attempt to edit a form or process in a private workspace, they receive an Access denied error message due to the cache not being refreshed.

Workaround: Navigate to the your private workspace, refresh the page to clear the cache, then edit your form or process.
An Automation Co-Pilot user with the AAE_Robotic Interface User license who is not apart of an assigned team can view all requests and tasks from other teams in the web interface. However, when the user attempts to access a request or task, they are prompted with an error message.
When a form is opened during bot runtime, the automated focus on the first form element is lost. For example, consider that Form A has various elements, and a Text Box element called Name is the first one. When Form A is opened during bot runtime, the focus is lost from the Name element and you cannot enter any values.

Workaround: When a form is opened during bot runtime, click the form element to enter or change the value.
When you log in to the web interface as an administrator, for certain languages, the translated text on the left navigation pane is truncated (not displayed completely).

Workaround: Hover over the menu item to view the tooltip, which displays the completely translated text.
In the Google Cloud Platform instance of the Automation Co-Pilot on the web interface, when you open a request that contains previously uploaded files, you might intermittently experience an error while downloading the files.

Workaround: Retry downloading the file.

If a form has a table element and you use the Set action from the Interactive forms package during bot runtime, values are not applied to the table element.
If you selected the action trigger as Changed value for a Dropdown element within a trigger loop, any associated event is triggered during bot runtime even when there is a Reset action.
In an SDS setup, when you create a request to upload a file, the upload fails and a SecurityTokenInvalidException error message is displayed.
The Override output variable option in the End Process endpoint is not currently functional for users to override a variable definition.

Discovery Bot

What's new
View Groups of steps

When reviewing a process view, you can now use the group option or icon to display groups of steps that belong to the primary level action and secondary level action (and subgroup level actions) used during the recording session.

Use the group icon to help you decide what groups of steps to select for a task you want to automate. For example, a primary level action displays Microsoft Outlook, a secondary level action displays Outlook mail notification, and subgroup level actions display terms such as Email -Add To, Email – Add Subject.

Create a process view with branches and opportunities

Use Dynamic option for system-generated views

You can now use the Dynamic option from the Model options to view recordings where groups of steps display a set of repeating patterns that belong to the same application or same primary level action used during the recording session.

Use this option to decide the context of the process or the task you want to automate. Groups of steps that are labeled belong to supported applications such as Microsoft (Excel, Outlook, and Notepad), Notepad++, text editors, most windows use cases, and Chrome browser functionality.

Create a process view with branches and opportunities

Enhancements to PDD Word document

The PDD Word document now includes a process recording flow chart and the time on each individual step in hours, minutes, and seconds.

Review opportunities and convert to bot

Fixes
Service Cloud case ID Description
-- The Control Room installer for Red Hat Enterprise Linux (version 7.7 or 7.9) now includes the Discovery Bot package. Previously, you had to log in to the Control Room as admin, select Manage > Package > Upload, and upload the Discovery Bot package.
Limitations
In a Linux environment, when you record a process using the Discovery Bot recorder, the recorder window opens for 4 seconds and then disappears. The error occurs because the ProcessDiscovery folder is missing in the following directory: /var/automationanywhere/enterprise/appdata/Server Files/.
Workaround: Perform the following steps to create an empty ProcessDiscovery folder manually and provide write access to the folder:
  1. Navigate to the following path in the Control Room directory:
    1. If you have updated from an earlier version to v.22, navigate to /opt/automationanywhere/enterprise/appdata/Server Files
    2. If you perform a new installation of v.22, navigate to /opt/automationanywhere/automation360/appdata/Server Files
  2. Run the sudo mkdir ProcessDiscovery command to create an empty folder for ProcessDiscovery in the specified Control Room directory.
  3. Run the following command to provide the required read and write permission for the newly created ProcessDiscovery folder:
    1. sudo chown -R crkernel:controlroom ProcessDiscovery/
    2. sudo chmod -R 775 ProcessDiscovery/

When you upgrade to A360 v.22, you might receive multiple email notifications about the PDD generated in A360 v.21.

When you add branches to the left and right sides of the main branch, the Recording flow chart section of the PDD might not capture the entire process work flow, including all the branches.

IQ Bot

What's new
IQ Bot standard forms integration with IQ Bot Extraction

You can now use the IQ Bot Extraction package for data extraction from standard forms documents.

Using IQ Bot Process documents action

Confidence threshold applicable on standard forms learning instance

For a standard forms learning instance, if the Confidence threshold value that you have set does not match any field, the document is moved to the Validator and a notification icon is displayed. This update now enables you to validate the document for the learning instance and also save the document.

Additional OCR engines for IQ Bot Extraction package

In addition to the existing OCR engines, IQ Bot Extraction package now supports the following OCR engines:

  • Microsoft Azure 2.0
  • Google Vision API

IQ Bot Extraction package

Export IQ Bot dashboard data
A user with the AAE_IQ Bot Admin role can now export the following data from the dashboard to a CSV file using the Export icon:
  • Documents processed
  • Pages uploaded
  • Straight-Through Processing
  • Accuracy

The CSV file is saved to the local Downloads folder.
IQ Bot support for self-signed certificates

You can create a self-signed certificate with Subject Alternative Name (SAN) to use an SSL certificate for multiple domains.

Creating a self-signed certificate with Subject Alternative Name

What's changed
IQ Bot package supports external proxy server settings (Service Cloud case ID: 00727414, 00725235, 00757568, 00753560, 00753560, 00786609)

The Download all documents and Upload Document actions in the IQ Bot package now support external proxy server settings.
IQ Bot Python library upgrade (Service Cloud case ID: 00756943, 00791511)

IQ Bot now uses Python version 3.9.5 for data extraction.
What's deprecated
IQ Bot [Local Device] package

The IQ Bot IQ Bot [Local Device] package is deprecated from this Automation 360 v.22 (Build 10526). Instead, use the IQ Bot Extraction package, which provides the same capabilities as the IQ Bot [Local Device] package, along with additional improvements.

IQ Bot [Local Device] package replaced by IQ Bot Extraction package (A-People login required)
Note: Before using the IQ Bot Extraction package, update the bots associated with the IQ Bot [Local Device] package and restructure the output folders.

IQ Bot Extraction package

Fixes
Service Cloud case ID Description
-- If you delete a .csv file from the Success folder, you can now download the remaining files from that folder.
-- When you use the IQ Bot Extraction package for processing a large set of documents, you no longer encounter any document processing issues with Bot Agent.
-- If an incorrect value was used in the providerVersion field when you uploaded standard forms configurations to IQ Bot, an error notification is now displayed when you select this configuration when creating a standard forms learning instance.
00806805 You can now import a learning instance using the Migration Utility feature as the Invalid Group error message is now resolved.
-- When you creating a learning instance using standard forms, all the available pre-trained models are now listed in the Select Model drop-down menu.
00703856 IQ Bot now correctly extracts table rows with numeric values even when they are within parenthesis.
-- The File Download API now returns a correctly formatted JSON response with a colon (:) separating the key-value pairs.
00694656 IQ Bot now successfully extracts values from the documents that have new table fields added after training.
00636887 An error notification is now displayed if you upload documents with file names longer than 150 Asian language characters in the staging environment.
Note: This is not applicable to a production environment.
-- IQ Bot cloud data query is now optimized to prevent overloading of the Amazon Relational Database Service.
00782994 When you use the Migration Utility to move a learning instance between environments, unclassified data is no longer exported.
00747137 You can now import learning instances using the Migration Utility feature without any issues.
Limitations

The value displayed in the My totals > Accuracy field sometimes does not match the value in the My learning instances > Field accuracy for the available learning instances.
If you try to import a learning instance into an IQ Bot environment that has a deleted learning instance with the same name, the following message is displayed even though the learning instance is not imported: Import process initiated
If you access IQ Bot without the correct permissions, they are redirected to an Access denied page, where the back button does not work.

Workaround: Close the current tab and open the Control Room.
When you select Other domain in the learning instance creation page, the tooltips for the table and form fields state that these fields are optional. However, these fields are required to create a learning instance.
IQ Bot installation sometimes fails and the following message is displayed: Failed to upgrade the DB: -1. When this issue occurs, retry the installation.
(Service Cloud case ID: 01016516, 00757943, 00787404, 00788421, 00807528, 00822941, 01018972) If you add multiple ABBY OCR based commands (such as IQ Bot Pre-processor, Document Classifier, AISense Recorder, OCR) in a single bot, an error message is displayed when you run the bot.

Workaround: Ensure that you do not add multiple commands in a single bot.
(Service Cloud case ID: 01063054)You cannot import a learning instance with a long name (>50 characters) because IQ Bot only supports up to 50 characters in the Label field.
If you use the Process documents action from IQ Bot Extraction package to upload documents, the validation rules from the default the validation group that you set are not applied. As a result, the failed documents are not classified into any of the existing groups and are moved to Validator.
In the IQ Bot Community Edition, when you use a Cloud OCR to create a learning instance, if you use the IQ Bot Process document action from the IQ Bot Extraction package, the values from the uploaded invoices or documents are not processed successfully.

Workaround: If you use the Cloud OCR to create a learning instance, use the IQ Bot Upload Document action from the IQ Bot package.
After you train a bot and click Save and go to next group, the system fails to load the next group. Instead, it reloads the same group.
Workaround: Perform the following steps:
  1. Refresh the page.
  2. Navigate to Learning Instances and click Bots to edit the Learning Instances.

System identified regions are not generated when a non-English filename is uploaded using the Invoice domain and processed with the AutoExtract command.

Workaround: To process the document, convert the non-English filename to English characters.

Bot Insight

Fixes
Service Cloud case ID Description
00788583 In the Profile tab, when you edit, save and generate a business dashboard and the dashboard is not saved, the error message description is now translated correctly in the Chinese language. Previously, if an error occurred when you saved the edits in the Profile tab of the Business dashboard, the error message description displayed garbled text.
00729920 When you migrate a task from a source (UAT) to a target (production) environment, a Published dashboard copy is no longer deleted from the source environment.
00742260 You can now export data from operational or custom dashboards after applying a non-metric variable in the filter. Previously, the data was not exported when you toggled between different chart types.
00738228 Multiple dashboards are no longer created for a Task Bot when you update and execute a bot that is checked out from the public workspace. Previously, when a bot was executed after an update, multiple dashboards were created.
00757992 A user with the Bot Creator license can now access all the Bot Insight dashboards (Operations and Business tabs) irrespective of their assigned role. Previously, if the user had the Bot Creator license with the AAE_Robotic Interface Admin role, they were not able to access these dashboards.
Limitations
(Service Cloud case ID: 00733555, 01912503) In a dashboard, the data labels in the pie chart overlap if it contains many slices. As a result, the labels in pie chart are not clear and shown only when you hover over the slices.
Workaround: To view the data labels in a pie chart in clear and readable format, export the dashboard data to Excel file.
Note: Due to a limitation within the third-party recharts library, you might observe labels overlapping issue with data in downloaded PDF as well.
Important: For information about the packages supported with this release, see Packages available in Automation 360.