Automation 360 v.23 Release Notes

Release date: 30 December 2021

Review what's new and changed, and the fixes and limitations in the Automation 360 v.23 (Build 11513) release. Build 11513 replaces Builds 11499 and 11486.

Important:

This build includes the Apache Log4j2 library version 2.17.1 to address the exposure to CVE-2021-44832, CVE-2021-45105, CVE-2021-44228, and CVE-2021-45046 vulnerabilities.
Though the command packages are not upgraded to Apache Log4j2 library version 2.17.1, the Bot Agent is upgraded to Apache Log4j2 library version 2.17.1. At runtime, the packages will use Apache Log4j2 library version 2.17.1 through the Bot Agent and hence will not be exposed. As an additional security measure, the Automation 360 v.23 Bot Agent installer also disables the Apache Log4j2 library look-up feature by default.
Third-party security scans might find traces of earlier versions of the Apache Log4j2 library. However, with the upgrade to Automation 360 v.23 and the mitigation in place, there will be no exposure to vulnerabilities. For more information, see FAQs related to Automation Anywhere Releases regarding zero-day vulnerabilities (CVE-2021-44228, CVE-2021-45046) (A-People login required).
This build also includes fixes for the following issues:
- When you update from Automation 360 v.22 to v.23, background jobs related to cloud license server sync-ups were deleted because of incorrect license job name.
- When you install or update to Automation 360 v.23 for On-Premises deployments, log files were not updated for a few additional services.
- If you did not have the View Package permission, bot deployments failed when you scheduled or ran a bot.

Migration
11.x and 10.x | 11.x only
RPA Workspace
What's new | What's changed | Fixes | Security fixes | Limitations
AARI
What's new | What's changed | Fixes | Limitations
Discovery Bot
What's new | Fixes | Limitations
IQ Bot
What's new | What's changed | Fixes | Limitations
Bot Insight
What's changed | Fixes | Limitations

Updating to this release

The updated Build 11513 for Automation 360 v.23 includes Log4j2 library version 2.17.1 and fixes. If you are on the previous v.23 Build 11499 (with Log4j2 library version 2.17.0) or Build 11486 (with Log4j2 library version 2.16.0), update to Build 11513 for the updated Log4j2 library version and the fixes.

You can also update to Automation 360 v.23 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.22 (Build 10526)
v.21 (Builds 9664, 9642, 9595)
v.20 (Build 8815)

You can directly update to v.23 from any of these builds (see Update to latest Automation 360 version). If you are not on an n−3 release, update Automation 360 to one of the three certified releases (listed previously) before updating to this release.

If you are directly updating to this release from Automation 360 On-Premises v.20 or v.21, remove the following Bot Agent files and folders:

C:\Windows\System32\config\systemprofile\AppData\Local\AutomationAnywhere\AA-DB.mv.db
C:\ProgramData\AutomationAnywhere\GlobalCache\embedded-resources

Bot agent update: To use the new features in v.23 (including updates to Recorder packages) and for the Log4j2 vulnerability fix, update the Bot Agent for this release. Note that the Bot Agent update from the previous release is not required if you want to run your existing bots as Bot Runners.

For information on updating to this release, see these resources:

For the latest updates to the Automation 360 extensions for Google Chrome, Microsoft Edge, and Mozilla Firefox, see Enhancements to browser extensions.

Migration features


Enterprise 11 and Enterprise 10 features
MetaBots containing linked objects Migrate MetaBots that contain a text play type linked object that is linked with the object play mode object, an image play type linked object linked with the image play type object, and a coordinate play type linked object linked with the coordinate play type object.
Migrate bots with the following attributes: Bots with variables that contain data larger than 64 KB ( Service Cloud case ID: 00716311,00756449,00819149) The migration process stores the data in a text file. The text file is uploaded to the Cloud Control Room and is used in the migrated bot. MetaBots with DLLs that return list and array type values with any delimiters combination and store these values in the clipboard You can now migrate MetaBots with image play mode that use the action GetVisibility You can now migrate bots with the GetSelectedIndex and GetSelectedText actions for the UI Automation technology used in the Object Cloning command and MetaBot screens. You can now migrate bots which automate applications with Java technology Type using the Object Cloning command with the action GetDataofAllchildren.
Bots with different variable casing When you migrate a bot that has passed a variable from a TaskBot to a MetaBot Logic or from a MetaBot Logic to a TaskBot and if the casing of the variable name is modified in the MetaBot Logic, the migration process updates the variable name with the same casing as that of the bot corresponding to the migrated MetaBot Logic in the parent TaskBot.
Migrate bots with locator image (Service Cloud case ID: 00754508, 00776192) You can now migrate bots that contain images that are captured using the Object Cloning command.
MetaBots as dependencies are not downloaded The migration process does not download MetaBots that are available as dependencies. This restriction is to avoid downloading MetaBots and creating multiple copies of the same MetaBots because they are already available in the Control Room repository.
New action in Legacy Automation package for migration (Service Cloud case ID: 00797140, 00849161) Use the Get keystrokes delay action to match the duration of delay defined in Enterprise 11 bots for the Insert keystrokes command and simulate the same value in Automation 360 for the Simulate keystrokes action.
Notification about bots with issues in Bot Scanner report The Bot Scanner report now flags Enterprise 11 or Enterprise 10 bots that have issues and therefore require action or review. For example, bots that have security issues or bots that refer to non-existent variables are flagged with an icon in the action or review message.
Improved validation of migrated bots Additional compile time validations are now available to validate a bot at run-time. For example, if a parent bot calls a child bot and the child bot has compilation errors, these errors are displayed when you try to run the parent bot. This ensures that an error does not occur in the middle of an automation or make it an incomplete automation. This feature enables you to proactively identify all migrated bots that have compilation errors. Migrated bots with compilation errors are shown in Successful with Review section of the Migration Report and ensures that you can get a list of bots that require your attention. To enable the bot validation feature, navigate to Administration > Settings > Bots > Bot validation and set it to On. See Settings. The Bot Migration Wizard now displays validation error details for each bot in the bot migration results. Details about the errors help you to review and take action on the migrated bots, thereby saving time. Migrate Enterprise bots
Enhanced bot migration assistant The migration assistant is now merged with the error assistant to provide a comprehensive view of all the lines in a bot that require review or action by you, or which have errors in these and therefore require you to address them. This feature helps you to quickly identify the areas of bots that require your attention.
Support for 32-bit driver to connect database (Service Cloud case ID: 00757466) To enable migration of Enterprise 11 bots with VBScript, 32-bit drivers are now supported in Automation 360 to connect the database.


Enterprise 11 only features
Migrate bots with the following attributes: Bots that include images that are captured using the Object Cloning command, OCR > Capture area command, App Integration > Capture area command, and Mouse click action. Bots that contain an HTML email body with local image references if the referenced images are available on the Bot Runner machine (Service cloud case ID: 00780065, 00790657, 00827527, 00822092, 00928116, 01181845) Bots that contain Microsoft Excel commands with file extensions such as .ods, .htm, .html, .mht, .mhtml, .slk, and .pdf to open an Excel file (Service Cloud case ID: 00799071) MetaBots that use the credential variable of non-string type to pass a numeric value as an input to a DLL function

RPA Workspace


What's new
Enhanced administrator capabilitiesProperly licensed Automation Anywhere Control Room administrators can now create valid RPA users based on authentication with username and password and select not to require live authentication via email response. This feature enables administrators to resend "Welcome" authentication emails without having to reset the credentials assigned to RPA users.
Microsoft Edge (Chromium) supported for Control Room and Bot Agent You can now perform Control Room operations, and install and register your Bot Agent device using the Microsoft Edge based on Chromium browser. RPA Workspace 的浏览器要求
Support for Azure Key Vault Automation 360 now supports Azure Key Vault, and you can now retrieve the following from the external key vault: Active Directory (AD), services account, and SMTP credentials Auto-login credentials Credentials by automations
Bot Validation Bot validation check happens for new bots and when you run a bot. Control Room administrators can now turn the Bot Validation feature on or off. By default, this feature is turned off for every Control Room. Migrate Enterprise bots
Credential Vault variable supported in Run function action of the DLL package As a Bot Creator, you can now use the Credential Vault variable or credential type variable for the `Number` data type and pass it as an input parameter in the DLL function. Using the Run function action
File ID supported in Check permission action of Google Drive package (Service Cloud case ID: 00777716) The Check permission action of the Google Drive package now supports the File ID option to refer to files available in the Shared with me folder of Google Drive. By providing the File ID, you can now verify the Read, Write, or Delete access granted to you in the Shared with me folder of the Google Drive files. Google Drive package
New Credential package You can now use the Assign action in the Credential package to assign an insecure string or a variable directly to the credential variable. Credential package
Web Services security supported in SOAP Web Service package (Service Cloud case ID: 00481836) As a Bot Creator, you can now provide credential variables in the raw data of the SOAP Web service action. You can create a credential variable, map the credential with a reference name in the credential mapper, and use the reference name in the raw data. Because this ensures that all security-related data can be defined in the Credential Vault and the credentials can be used in bots, you can safely deploy tasks without compromising security. Example of using the SOAP web service action
New option in SOAP Web Service package Use the Build Xpath option in the SOAP Web Service package to extract values from the SOAP response. You can now specify the Xpath expression or select the appropriate node from the response body and store the output in a variable.
Outlook server supported in Change status, Save email, and Delete actions (Service Cloud case ID: 00544534, 00557623, 00642506, 00659724, 00763565, 00680801, 00803975, 00818304, 00819362) In the Email package, to automate a task you can now establish a connection with the Outlook server for the Change status, Save email, and Delete actions.
Read email from shared mailbox in Microsoft Outlook (Service Cloud case ID: 00728579, 00831622) To automate email-related tasks, you can now select a shared account in Microsoft Outlook so that email messages can be read from the shared mailbox.
New encoding types supported in the Write to file action of Data Table package (Service Cloud case ID: 00767158) When you use the Write to file action to write data from a Table type variable to a CSV or TXT file, you can now use the following encoding types from the encoding list: UTF-8: Works as UTF-8 without BOM UTF-8 with BOM (called UTF-8 previously) UTF-16LE Shift-JIS (Japanese encoding)
Auto-save functionality in Bot editor In the Bot editor, when you use actions to build an automation, when a bot is not manually saved, an auto-save is performed and the bot now automatically saves the changes for specific events. Note: The auto-save functionality is currently available only for specific events. Some of the events that support auto-save functionality are as follows: Recorder: When you create a bot with certain actions and click Recorder, the event is saved, and when the recording is complete, the event is automatically saved. Variable manager: When you create or edit a variable to insert it in an action, the changes are saved. Note: The auto-save functionality is not supported when you delete a variable or insert it by pressing F2 to open the variable list. Actions menu (vertical ellipsis): When you select any action from this menu, for example Packages, the event is saved automatically. When you make any change to the Packages page and return to the Bot editor, the event is saved. Find a file: When you click the Find a file icon, the bot is saved if it is not manually saved. Also, after you click the Add option, the bot is automatically saved. Dialog boxes: When a dialog box is opened, it is automatically saved if any changes are made. Note: Auto-save is triggered only for top-level dialog boxes and not for nested dialog boxes. Deleting variables: When you delete unused variables, the event is saved. Bot name change: If you edit the name of a bot, the event is saved.
New option in FTP / SFTP package (Service Cloud case ID: 00792346) Use the Credential option when you connect with the Secure FTP server type to automate a task. You can now use username and password for authentication. Using Connect action for FTP/SFTP
Enhancement to AISense Recorder AISense Recorder now supports automation of applications that use Brazilian-Portuguese and a combination of Brazilian-Portuguese and English interfaces. AISense for recording tasks from remote applications
Support for Capture anchor in AISense Recorder The AISense Recorder now supports the Capture Anchor option. When you run a bot to search for an object in an application in which the anchor changes frequently, you can use Capture anchor to override the default anchor and manually select an anchor to detect the object. Edit a task recorded using AISense
Enhanced support when selecting Object property in Recorder package After you capture an object using the Recorder > Capture action, you can now select a particular object property name from the list of available properties in order to retrieve the value of the object property using the Get property action. The list includes suggested property names from the search criteria in the Object Properties table. Recorder package
Enhancements to Number package In the Random action of the Number package, you can now specify and limit the number of decimal digits required in the random number generated in the output. The existing Save the outcome to a number variable field is now renamed as Save the outcome to a variable. Number package
Enhancements to Wait package Use the new Capture region feature in the Wait for screen change action of the Wait package to capture a specific region on an application by drawing a rectangle around it so that the bot automatically captures the coordinates of this region. You can perform the following actions: Capture a specific region on a Windows application. Preview the captured image in the Preview window. Recapture a region if the image in the Preview window is not per user requirement. The coordinates are renamed as follows: Left is now X Top is now Y Right is now Width Bottom is now Height Using Wait for screen change action
Enhancement to String package In the Extract text action of the String package, you can now extract a substring from a specified source string that occurs more than 1000 times in a file and up to a maximum limit of 999999.
Enhancement to File conditions in If package You can now use the new File extension condition from the Condition list in the If package to check the extensions of files and then execute actions based on the results.
Support for cross-domain IFrames in Google Chrome and Microsoft Edge Chromium browsers (Service Cloud case ID: 00825656) You can now capture and automate objects inside a cross-domain IFrame in Google Chrome and Microsoft Edge Chromium browsers by using Recorder > Capture or the Start recording option. After you capture an object inside a cross-domain IFrame, the path to the frame is stored in the FrameDOMXPath property, by default. The new FrameDOMXPath property identifies the path to the frame in which the object is located. You must select this property to run the bot successfully to capture objects on a cross-domain IFrame. Note: This feature is available for the bots you create using the 2.4.0-20211016-070100 version of the Recorder package starting from this release. Recorder package
Support to automate Microsoft Edge Chromium with Internet Explorer compatibility mode (Service Cloud case ID: 00767502, 00787186) You can now automate web applications running on Microsoft Edge Chromium, by enabling the Internet Explorer compatibility mode, using the Universal Recorder where the objects are captured using HTML technology. Record a task with the Universal Recorder
Global session support for loop iterator based on Excel advanced You can now use the Global session option when you loop through each row in an Excel advanced worksheet. Use the Global session option to share a Microsoft Excel session across multiple bots so that you can use the same Excel worksheet across these bots. Using the Open action for Excel advanced
Enhancement to Excel advanced package (Service Cloud case ID: 00799071) Use the Open action of the Excel advanced package to open files with .ods, .htm, .html, .mht, .mhtml, .slk, and .pdf extensions. Excel advanced package
Check out a specific version of a bot To edit a bot in the Control Room Automation page, when you check out a bot from the Public to a Private workspace, you can now choose a specific version of the bot along with its dependencies by using the new Advanced options. Check out a bot
New APIs for devices You can now allocate default devices by using the new APIs introduced in the v1/Devices section. Choose to set or not set a specific device as the default deployment device for a specified user by using the following APIs respectively: `/runasusers/default` `/runasusers/default/unset`
Configurable API-key validity (Service Cloud case ID: 00763420) You can now configure the validity of the API-key using the API-Key Duration feature available in the Administration > Setting > Security Configuration in Automation 360. You can set validity minimum of 1 minute or maximum of 45 days.
Bot version comparison You can now compare various versions of the bots in your public workspace. You can use the Compare versions option to select two versions of a bot and compare them for differences, and any modifications in your work flow are highlighted for your reference. You can also view the differences in the actions, packages, triggers, and variables between the versions. Compare bot versions
Production label support in bot development work flow You can now assign a Production label to a particular version of a bot. After you assign a label, you can run or export bots with a bot version of your choice. You can select the version associated with a production label to schedule, run, queue, and trigger bot development work flows. Assign label to a bot
Access to Automation Anywhere RPA Training & Certification A direct link to Automation Anywhere RPA Training & Certification is now added in the Automation 360 Help Center. Automation Anywhere University: RPA Training and Certification (A-People login required)


What's changed
Bot Scanner recommendation The Bot Scanner now recommends to proceed with migration (with or without review or action) when 95% or more than 95% of your bots can be migrated.
Assign credential variable to non-credential type variables for migrated bots For migrated bots, Automation 360 no longer restricts you from assigning the credential variable to a non-credential type variable in an insecure (non-secure) way. So you can now successfully run migrated bots that use the Run Logic command to pass the credential variable to a non-credential type variable in an insecure manner.
Enhancement to Recorder package The search algorithm for the Recorder package is now enhanced so that when you run a bot an object is captured only if its properties match the exact search criterion that you selected in the Object properties table. If the properties of the object do not match the search criterion exactly, then the bot fails with an error message. However, if the search criterion includes a wildcard character, then the bot captures the first object that matches the criterion. For example, to capture a text box from an application that has three text boxes named firstname1, firstname2, and firstname3, if you select HTML name as the search criterion, enter the value `firstname` in the HTML name field, and run the bot, then the bot fails with an error message because a text box with the HTML name `firstname` does not exist. However, in the HTML name field, if you enter `firstname*`, and run the bot, then the bot captures the first text box that matches the criterion. Previously, if there were no objects whose properties matched the search criterion exactly, instead of failing, the bot captured the first object whose properties matched the search criterion partially. For instance, in the previous example, if you selected HTML name as the search criterion, entered the value `firstname` in the HTML name field, and ran the bot, then instead of failing, the bot captured the first text box that matched the criterion partially. Note: This enhancement is available for the bots you create using the 2.4.0-20211016-070100 version of the Recorder package starting from this release. To use this functionality in the bots created using a previous version of the package, you must recapture the objects.
Enhancement to File package (Service Cloud case ID: 00755631, 00780237) In the Copy Control Room file action of the File package, the new Dynamic file path option in the Control Room file field now enables you to use variables in the file path to copy a file from the Control Room repository where the file path is dynamic. Some actions and properties in the File package are now updated, as follows: The Copy action is now renamed Copy Desktop file. The Download CR file action is now renamed Copy Control Room file. In the Copy Control Room file action, the following fields are renamed: The Select a Control Room file field is now renamed Control Room file. The Save CR file to location field is now renamed Target file path. In the Copy Control Room file action, the Control Room file field now has two new options: Static file path and Dynamic file path. The Static file path option is an existing feature in the Control Room file field that enables you to browse the Control Room repository and select the file. When you browse the repository using Static file path, files with .bot extension are no longer displayed. Note: The renaming of actions within the File package does not impact existing bots that use these actions. File package
Changes to Connect action in FTP / SFTP package (Service Cloud Case ID: 00792346) The following changes are made to the Connect action: SSH FTP server type is now renamed Secure FTP. When you select the server type FTP Secure, the User credentials authentication type is now renamed Username & Password. Note: From this release, if you use the Secure FTP credentials in FTP Secure, the bot will fail. Instead, we recommend you to use the Credential option available in Secure FTP to connect with the Secure FTP server. Change in Connect action: If you created bots using the Connect action using Automation 360 v.22 and earlier releases and you update to v.23, the bots display some of the Connect action settings as deprecated due to changes in the interface. However, your existing bots will continue to run successfully. For new bots, we recommend that you create them using the Connect action available from this release.
Support for copying one or more variables (Service Cloud case ID: 00549368, 00751052, 01260498) You can now copy one or more variables from one bot and then paste them in another bot. Previously, the copy operation also copied the actions along with the variables.
Support for reserved characters in Distinguished Names (DN) for Active Directory Control Room (Service Cloud case ID: 01133364, 00952301) You can now use reserved characters, such as the comma (,), in the DN or the username of a Control Room configured for Active Directory users.

The following table lists the fixes and the builds in which they were fixed. Build 11513 is the latest build and includes fixes from the previous builds.


Fixes
Build	Service Cloud case ID	Description
11513	00797196, 00818347	Updates to the Private workspace API ( `/v2/repository/workspaces/{workspaceType}/files/list`): Only private workspace authorized users can list the bots from the private workspace. Admin cannot list the private workspace bots. Only public workspace authorized users cannot list the private bots. One private workspace authorized user cannot list another user private workspace files.
11513	00808478, 00814198, 01260666	If you are a Control Room administrator, when you change the viewing permissions of some bot folders so that they can be viewed only by specific users, the change is now correctly applied. Previously, changes made to the viewing permissions of bot folders were not applied correctly.
11513		When you update from Automation 360 v.22 to v.23, background jobs related to cloud license server sync-ups are no longer deleted because of incorrect license job name.
11513	01753484, 01754939	You can now deploy (both schedule and run) bots from the Control Room without any issue if you have the View Package permission. Note: The View Package permission is required to deploy (both schedule and run) bots from the Control Room.
11513	--	When you install or update to Automation 360 v.23 for On-Premises deployments, the log files are now updated for all the services without any issue. Previously, the log files for a few additional services were not updated with any information or time stamp of the activities.
11486	00793800	When you migrate to this release, issues related to JRE while installing the Control Room on machines using Microsoft Hyper-V servers are now fixed. The following error no longer occurs: `Unknown Failure. Please check the database login credentials and check if this machine has a network connection to the database server.`
11486	00815340	User folder names given similar leading portions or naming conventions no longer display folders that share naming conventions but not the assigned or specific user permissions.
11486	00836898, 01259938	The Cloud Migration Utility now includes enhanced logic to enable you to successfully upload data even when the network is connected through a proxy server.
11486	00817173	You can now perform a Run DLL function when both the input and output parameters are set to a String value, and the Date and Time value is now passed as a String parameter successfully. Previously, the Date and Time value was converted and not displayed as expected.
11486	00754305, 00769128	The configuration tagging works properly now, based on the settings configured in the nodemanager-logging.xml file. Previously, the node manager and bot launcher logs were purged either after two days or if the log count was increased by specific amounts due to tagging issues with tags such as the following: "IfLastModified age" and "DirectWriteRolloverStrategy"
11486		When you decide to select or deselect all the bots and dependencies, you can now select or clear the Select All check box without any issues. Previously, after selecting the Select All check box, when you cleared the check box, it did not work as expected, and you had to deselect the bots and dependencies individually.
11486	00798037, 00814184	The Manage and Administration labels in the navigation pane are now updated to ensure that roles and permissions are distinct in the following languages: Simplified Chinese, Traditional Chinese, Japanese, and Korean.
11486	01218053	You can now import parent and child bots with dependencies even if you do not have permissions to all folders. Previously, if a user with no folder permissions imported parent and child bots with dependencies, the dependency between them was lost.
11486	01046249	When you migrate from Enterprise 11 to Automation 360, duplicate entries are no longer created for any of the existing commands.
11486	--	You can now migrate an Enterprise 11 bot that uses the Run Task command successfully even if the Upon error, continue with next repeat option is not selected. Previously, the parent bot stopped running if the child bot encountered an error. Now, when this option is not selected, an error handler ensures migration is successful even if the child bot encounters an error.
11486	--	If you used the Go to cell action from the Excel advanced package in an Enterprise 11 bot, the setting is now retained when you migrate it to Automation 360.
11486	00779016	You can now use the XML package to open any xml files without any issue after migrating to Automation 360.
11486	00794202	You can now migrate Enterprise 11 bots with If command to Automation 360 without any issues.
11486	00790245	You can now use the SOAP Web Service action of the SOAP Web Service package without any issues after migrating to Automation 360.
11486	00795518, 00832462	If you used the Delete cells action from the Excel advanced package in an Enterprise 11 bot, correct cell addresses are now displayed when you migrate it to Automation 360.
11486	00808601	Migrated bots that include Extract and Substring actions of the String Operation no longer encounter an error if the input string is empty.
11486	00807945, 01258127	When you migrate Enterprise 11 bots using the Error Handling command, an error no longer occurs if the file path value in the variable is missing the file extension from the Snapshot and the Log to file. After migration, the Snapshot file now saves files with .png extension and Log to file with .txt extension.
11486	00777395, 00807705, 00814087	The migration process now adds the Window > Set title action for all the ElseIf-window exists conditions. This setting enables you to make the window title dynamic, eliminating the need for you to recapture the window title when it changes.
11486	00820094, 01019195	After you migrate to Automation 360 from Enterprise 11 or Enterprise 10, the Error Handler snapshot error is now logged to the Snapshot image path. If the snapshot image path is provided as a variable, then the snapshot error is logged to the default application path.
11486	00810389	You can now migrate bots with variables whose names start with or contain arrayRows. You no longer encounter a stack overflow error and the bots are successfully migrated.
11486	00795347	The DLL Run action now successfully copies your data from one Excel sheet to another even if the .Net DLL uses the OLE mechanism (for example, clipboard) to copy data. Previously, when data was copied from one Excel sheet to another, a threading-related exception occurred.
11486	00787562	After migration to Automation 360, an Enterprise 11 large bot (with 2000 or more commands) no longer encounters the `Code too Large for try statement` preprocessing error when the bot is used in Automation 360. However, if the migrated bot includes a Loop or Trigger Loop command with Continue or Break as a child command, a preprocessing error might still occur when the bot is run.
11486	00782594, 00786968	When you migrate to Automation 360, an Enterprise 11 bot with large array sizes no longer encounters Java heap errors. If the total size of the arrays in one bot exceeds the threshold value of the array size, then the arrays variables are migrated as is till it breaches the threshold value. However, the remaining array variables are migrated as table variables with no default value using the Database > table action.
11486	00792346	If your Enterprise 11 bot was configured with Secure FTP without Key File Authentication, the migration process now appropriately configures the bot with the Secure FTP server type in Automation 360. Previously, the migration process incorrectly configured the bot with the FTP secure server type.
11486	--	Users with the AAE_Bot Migration Admin role no longer encounter an issue when they migrate bots using the Bot Migration Wizard.
11486	--	The Bot Migration Wizard now displays the correct number of MetaBots on the Select bots to migrate screen.
11486	--	Enterprise 11 bots that are migrated no longer encounter an error when a variable that is mapped between the parent bot and a child bot is not available in either of the bots.
11486	00729719, 00959356	You can now add or update SAP automation using the Capture action of the Recorder package when the SAP scripting is disabled in the Enterprise 11 bot.
11486	00639940, 00770561	If the migration process fails, the All migration screen now shows the status as `unsuccessful`. Previously, when the migration process failed because of invalid device credentials, the screen showed that the migration process is in progress but the Audit log displayed the correct status.
11486	00840456	The migration process no longer encounters an error when you migrate a MetaBot that contains a logic that has an extra space character at the end of its name.
11486	00786646, 00808600, 00822029	Migrated bot no longer encounter an error when they contain commands that perform an action on a pop-up window of a browser.
11486	00777467	Migrated bots no longer encounter an error when they are checked out in Automation 360 and they contain an invalid expression that is added by the migration process.
11486	00786002	You can now delete .atmx and .mbot files from the Control Room if you have all the required permissions.
11486	00796725	The Bot Scanner no longer encounters an error when it scans a bot in which the window title is specified using a variable within brackets.
11486	00790861, 00836849	Migrated Enterprise 11 or Enterprise 10 bots no longer encounter an error when they use the Run Logic command to run a MetaBot logic and the location of the logic is specified up to the folder that contains that logic. For example, consider that you have a MetaBot named Finance1 and you want to run Logic1 that is available in the MetaBot at the Metabots\Logics\Finance location. Previously if you specified only Metabots\Logics\Finance instead of the complete path (Metabots\Logics\Finance\Logic1) of the logic, an error occurred.
11486	00804550	You can now import bots from an Enterprise 11 production environment to an Automation 360 development environment even if these bots include the user ID of the user who had checked out the bot in Enterprise 11.
11486	--	When you search for bots with the following characters, the bots are now displayed in the search results: r$@1&#klu%)((}{,'!~`$^&()_-+=[]
11486	00729393	After you migrate from Enterprise 11 to this release, you can now view the bot subfolders in your Control Room Public workspace on the Automation page.
11486	--	After you migrate from Enterprise 11 to this release, you can now check in bots to the Control Room Public workspace from a folder for which you have the Check in permission using the Repository Manager API. The API response code no longer shows the following: `"upload": false`.
11486	01032367, 01066099	An issue with the bot deployment progress window is now fixed. Previously, even after the bot completed the run, the window was displayed for a long time (for example, for more than 10 seconds in some cases).
11486	00826923, 01081380, 01259907	After you migrate from Enterprise 11 to this release, you can now add work items to queues using the Workload API through AWS Lambda. A StackOverflow error no longer occurs in the Control Room logs.
11486	00801810	When you update Automation 360 On-Premises to this release, Bot Agent devices now remain in connected state. WebSocket errors are no longer generated in the C:\ProgramData\AutomationAnywhere\BotRunner\Logs\Node_manager.log file. Previously, when you updated from Automation 360 v.19 (Build 8147) to Automation 360 v.21 (Build 9664), some issues were reported where the Bot Agent devices remained in disconnected state and WebSocket errors were generated even without any proxy configuration changes.
11486	00831028, 00830336, 00827031, 00832413, 00833089, 00833436, 00832850, 00839997, 00849904, 00857296, 00831062, 00833436, 01140913, 01145306, 01252819, 01127960, 01256324, 01257414, 01258281, 01263606	When you update your Control Room that is configured with Active Directory to this release, you can now use the log in with Windows option and the following error no longer occurs: `java.lang.NoSuchMethodError`.
11486	00719407	For On-Premises deployments, when you configure multiple IP addresses for Control Room nodes in a cluster, the primary IP address is now automatically configured. You no longer have to manually configure the primary IP addresses in the cluster.properties file.
11486		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 wizard returns you to the previous Setup type window so that you can cancel the Bot Agent installation. Previously, when you clicked OK on the Out of disk space window, the wizard displayed multiple windows.
11486	--	When the Bot Agent is updated automatically from a previous release to this release, you can perform various operations simultaneously, such as running bots, configuring device settings in the Control Room, and updating the Control Room. You no longer have to restart the Bot Agent service from the Task Manager.
11486	00781135	After you install the Bot Agent on a user device, when you restart the Bot Agent, the global cache folder (C:\ProgramData\AutomationAnywhere\GlobalCache\) is no longer deleted.
11486	00709309, 00766163	You can now upgrade the Control Room installed on Linux to this release and the Elasticsearch service now starts successfully. Previously, the upgrade failed because the service did not start and the following message was displayed: `Elasticsearch service fail to start during certificate retrieval process.`
11486	00742074	License allocation for users configured to use multi-user devices is now honored for concurrent bot deployments on unattended Bot Runners.
11486	00822176	On multi-user devices, you can now create an RDP session that uses a custom port. Previously, if you configured a multi-user device to use a custom port for RDP-based deployments, the deployments failed.
11486	00806583, 00805381	When you perform RDP-based deployments on a device, FreeRDP no longer fails when connecting to a Windows server for per-device RDS licensing.
11486	--	If you deploy bots using event triggers and install the Bot Agent on a device as a non-admin user for yourself or a local admin user, the Bot Agent is now updated automatically. The device is no longer shown as disconnected in the Control Room.
11486	00803434	Issues with the change in Jetty HTTP client behavior on load balancers with custom rule for host headers to route a request are now resolved. Device registration now does not fail and the port numbers are added to the host when default ports are used.
11486	00815334	Performance issues related to logging in to the Control Room and editing and running bots in the Cloud Control Room are now fixed.
11486	00543141, 00674098, 00714238, 00744991, 00750325	With Splunk integration and enhancements to syslog, you can now forward audit logs to remote Splunk servers and view audit logs on Splunk dashboards.
11486	00776569	When a bot you run encounters an error, an appropriate preprocessing or runtime error message is now shown. Previously, a preprocessing or runtime error message was shown even if the bot did not contain an error or if the bot was empty.
11486	00781638, 00805371, 00804784	Issues with a checked-out bot and its clone are now resolved. When one user checks out a bot, makes changes to it, and checks in the bot, the clone of the bot in another user's Private workspace is now updated with the changes.
11486	00784252	If you do not have Control Room admin privileges and you check in bots to the Cloud Control Room Public workspace in subfolders, the bot folders no longer take time to load in the Control Room.
11486	00786716, 00801631, 01189873	An error no longer occurs when you use the Download action in the Browser package to download a file from a web URL. Previously, if a web URL had a backslash at the end or space characters at the beginning or end, the bot failed to download the file.
11486	00783197, 00818698, 00820666	When you use the Assign action of the Number package to assign decimals to an existing number variable, an error no longer occurs irrespective of the device locale settings on the machine.
11486	00778496	You can now successfully import the bot archive into the public workspace even if the archive creates a folder named System in the Bots folder.
11486	00774026	You no longer encounter an issue when you use the CSV/TXT > Open action and the Task Bot > Run action to search for a file or a bot with a name that contains Japanese characters.
11486	00761035, 00786113	You can now use the Recorder > Capture action to capture an object on a window that has a tree view and also retrieve the Item name property of that object by using the Get property action. Previously, when you ran a bot, the recorder captured the object on the window successfully but failed to retrieve the item name of that object in the output.
11486	00763925	An error no longer occurs when you use the Split action of the String package to split a source string that has any combination of Unicode characters.
11486	00767074	In Internet Explorer, when you use the Browser > Open action to open a new window or tab, the new window or tab is now displayed in front of the other, non-admin open windows.
11486	00819664	You can now create bots using the SOAP Web Service action. XML calls no longer return corrupted data when the SOAP response has an XML document as an inner element.
11486	00748494, 00829735, 01018622	You no longer encounter any issues when you deploy a bot containing email triggers. Now, each time an email message is sent, the bot is triggered and runs successfully. Previously, the email trigger worked only for the first time an email message was sent, and for subsequent email messages, the bot was not triggered and did not run.
11486	--	The Task bots runs metric on the Home dashboard page of the Control Room now displays the correct count. Previously, the Task bots runs metric displayed the count as zero even if you have run bots from the same Control Room.
11486	00824309	In the Run stored procedure action of the Database package, when you click Add parameter to provide an input or output parameter, the label for the parameter type field now displays as Parameter type. Previously, the label for the parameter type field was not displayed correctly.
11486	00810212	When you use the Run action of the Task Bot package and select the Multiple variables option in the Save outcome to a variable field, the variable name is now displayed in the correct case. Previously, the variable name was displayed in lowercase even if the variable name was created using uppercase.
11486	00796913, 00836389	You can now use the Move all action from the Email package to move multiple email messages from Inbox to another folder. Previously, the Move all action was not able to process a large number of email messages because disk storage ran out of space.
11486	00798673, 00815700	An error no longer occurs when you use the Database Connect action, enter the connection string that uses Windows authentication, and run the Run stored procedure action that has an input parameter value of more than 36 characters. Previously, an error was displayed when the length of the input parameter value exceeded 36 characters.
11486	00799450	When an excel spreadsheet is opened in the SAP editor and simultaneously you use Open action of the Excel advanced package to open an excel file, any error no longer occurs when the bot is run and the Excel file is opened successfully. Previously, an Excel file opened in the SAP editor was considered the default window and therefore when you ran the bot, an error was displayed stating that the Excel file could not be opened.
11486	00794102	In the REST Web Service package, the description below the Assign the output to a variable field is now translated correctly for the following languages. Japanese French Italian Portuguese (Brazil) Simplified Chinese Previously, the description was not correctly translated for these languages.
11486	00788920, 00796452	In the Email package, when you use Connect action to connect to the Outlook or IMAP server, you can now successfully download the email attachment in .eml file format. Previously, if you had email attachments in .xlsx and .eml file formats, only .xlsx files were downloaded.
11486	--	If you create a `Dictionary` variable with the `Any` subtype and select Datetime as the default value, when you click the time icon, you can now see the time values displayed in the drop-down list. Previously, when you clicked the time icon to select the time from the drop-down list, the values were not displayed.
11486	00746630	You can now create a new task using Excel advanced with Loop and you select the For each row in worksheet (Office 365 Excel) option from the Iterator list, create a `Record` type variable, and run the bot. An error no longer occurs when you edit the same bot and select the For each row in worksheet (Excel basic or Excel advanced) option from the Iterator list. Previously, a preprocessing error was displayed on bot execution.
11486	00762978	If you use the Windows > Close action and select Currently active as the window title to close active windows, when you run the bot, the Shut Down Windows pop-up is no longer activated even if there are no active windows on the machine.
11486	00805654	The Split action of the String package now allows you to select the Any variable type to hold the output values. Previously, you could select only the list variable.
11486	00761189, 00764563, 00785751, 00794273, 00835194	Performance issues related to the Run macro action in the Excel advanced package are now fixed.
11486	00796120	When you use the Data table > Sort action to sort a column, if the column does not contain any value, the bot now runs as expected and does not get stuck. Previously, you had to stop the bot manually.
11486	00830011	In the Excel advanced package, when you perform the Go to next empty cell action on an Excel sheet, the system no longer runs out of memory.
11486	00765210, 00790641	An error no longer occurs when you use the Excel advanced > Open action to open an Excel file that contains a pivot table.
11486	00776021	When you use the Open action of the Excel advanced package to open an Excel workbook, even if the workbook has invalid links, the bots now run as expected.
11486	00692220, 00785965, 00798035	Performance issues related to the Write from data table action of the Excel advanced package are now fixed, and the action now performs better on Excel sheets with large amounts of data.
11486	00808137	The format of Start date and End date under the Date condition is now updated to MM/dd/YY for the following actions of the File and Folder packages, where dd now correctly shows the date: File package Copy Desktop files action Delete action Print action Print multiple files action Rename action Folder package Copy action Delete action Rename action Previously, the format of Start date and End date was MM/DD/YY, where DD gave the day count of the year instead of date.
11486	--	When you run a bot with the following sequence of actions, the file is now successfully deleted at the end of the sequence: CSV/TXT > Open action to open a .csv file A loop action within another loop action to retrieve values from the .csv file CSV/TXT > Close action to close the file Here, all the actions are using the same, default session. File > Delete action to delete the file Previously, the file was not deleted because the bot failed to close the default session.
11486	01164436, 01209626, 00975390, 01080879, 01254846, 01256132, 01255004, 01263774,01253240	An error no longer occurs when you use the 2.4.0-20211118-080716 version of the Recorder package to capture a control using HTML technology in the Google Chrome or Microsoft Edge Chromium browser and run the bot. Previously, when you used the 2.3.0-20210806-215200 version of the Recorder package, the bot failed with the following error message:`Unable to find control. Search Criteria did not match`
11486	00818990	The capture anchor option in the Recorder package is now supported for the Citrix XenApp application. You can now select an anchor to search for an object in a user interface during bot run and execute actions based on it.
11486	00782962	An error no longer occurs when you loop through multiple Excel sheets and use keystrokes inside the loop to copy and paste the retrieved values into another Excel sheet. Previously, when you opened and closed multiple Excel sheets within a loop, the bot did not identify the correct Excel sheet for performing the keystroke action.
11486	--	You can now use the String > Import string from text file action to read values from a text file when a bot runs if the text file encoding was set to any of the following encodings: UTF-16BE UTF-8 ANSI Window-1251 UTF-16LE Shift-JIS
11486	--	When you update the Control Room on Linux from any earlier version to Automation 360 v.21, the Control Room now displays the updated interface. Previously, when you updated to Automation 360 v.21, the Control Room continued to display the old interface from the previous version.
11486	00816941	You can now run bots with a queue based on the sorting order that was selected for the work item column in the work item template. Previously, the bots were deployed based on the sequence in which work items were inserted into the queue.
11486	00804330, 00822092	After a bot is deployed on a user device, the Run History page (Manage > Scheduled) now shows the correct details about the run history of the bot.
11486	--	When you pause and resume a workload automation after using the run bot with queue in the Control Room, the audit entries are now captured on the Audit logs page.
11486	00803717	In the Control Room Historical activity page, the Modified by column now shows the name of the user (Bot Creator or Bot Runner) who scheduled a bot on a user device. Previously, the column displayed the username of the latest bot user.
11486	--	When you deploy workload bots from the Control Room, you can now run workload automation with elevated privileges by using the Run as administrator option.
11486	00780635, 00791587, 00795559, 00795632, 00797130, 00797113, 00791783, 00765770, 00826805, 01859661	When you update from a previous release, schedules no longer disappear from a Control Room configured on a single-node or multi-node environment. Also, previously deactivated schedules no longer disappear and become reactivated automatically after the update.
11486	00974353	You can now deploy workload bots on Bot Runner devices because the bots associated with a queue cannot be deleted. Previously, user had permission to delete the workload bots while running with queue.
11486	00830546, 01181402	When work items are inserted for workload automations, an Apache Ignite StackOverflow error no longer occurs, and the Control Room server no longer stops running.
11486	01021889	When you schedule or deploy a bot from the Control Room, if a bot fails to run, an email notification is now sent. Previously, even if the Control Room administrator enabled the A Task Bot stops running because it is unsuccessful setting in the Control Room, an email notification was not sent.
11486	00949288	Scheduled bots are no longer stuck in the pending execution status intermittently on the Activity page, and subsequent bots scheduled for execution are not stuck in queue.
11486	01253045, 01256337	Each scheduled bot is now deployed on Bot Runner device one time in a day. Previously, some scheduled bots were deployed twice on Bot Runner device.
11486	00750399	You can now capture objects from Microsoft Internet Explorer running as XenApp on a Citrix Server that has multiple Citrix applications installed.

The following table lists the limitations identified in the current release:


Limitations in this release
When you migrate a bot that was using the Manage Window Controls action, the last digit of the height value is not available after migration. However, the bot will execute successfully. (Service Cloud Case ID: 01756996)
When an Excel session is active in SAP, a corresponding Excel process starts in the background. In such a scenario, Automation 360 uses the same Excel process that SAP started. When you run a bot to automate spreadsheet data, Automation 360 processes the first request successfully. However, during execution, if the Excel is closed and a subsequent request is sent for automating the spreadsheet data, Automation 360 does not process the request because the Excel process is still being accessed by SAP. Therefore, the correct window is not activated for automating the spreadsheet data. (Service Cloud Case ID: 00815159)
When you run the bot, the Task bots run metric on the Home dashboard page of the Control Room does not display the correct count. For example, the task bot run count shows 39 on the Home dashboard page, but when you run the bot, the count is displayed as 42 instead of 40.
(Service Cloud case ID: 01753337 ) In the "In progress" table, the column sort function cannot be used to list items in ascending or descending order.
After migration, when you run a parent-child bot that share a session and use different DLL package versions, the bot fails with a run-time error message.
Nested IFrames are not supported in Google Chrome and Microsoft Edge Chromium browsers. After performing an action in an application or page, if a frame is added during run time to the application or page, and the frame is populated and page is not refreshed or reloaded, elements in the application frame or page cannot be captured or played until you manually refresh that page.
(Service Cloud case ID: 00988580, 01200161) After you migrate from Enterprise 11 to Automation 360, you might not be able to Check out some bots and dependencies to the Control Room Public workspace. Workaround: Check out the parent bots to the Control Room Public workspace. The dependencies are then automatically cloned. For more information, see Cannot Check Out With Child Dependencies Due To No Versions (A-People login required).
If you are directly updating from Automation 360 On-Premises v.20 or v.21 to this release, you might face issues updating your Bot Agent on some Bot Runner machines in the following scenarios: After a Control Room update, the device status keeps changing and the Bot Agent fails to update automatically. If the embedded resources file is missing, the Recorder does not recognize the user interface elements or does not capture a single object in the Google Chrome browser. Workaround: Before updating to this release, remove the following Bot Agent files and folders: C:\Windows\System32\config\systemprofile\AppData\Local\AutomationAnywhere\AA-DB.mv.db C:\ProgramData\AutomationAnywhere\GlobalCache\embedded-resources For more information, see Bot agent auto update fails post the Control Room Upgrade with 'device.connection.lost' (A-People login required) \| The recorder is not able to recognize the GUI elements in Google Chrome browser (A-People login required)
In some cases, if you Check in a bot to the Control Room Public workspace after filtering any dependency, when you export the bot, all the dependencies are displayed instead of the filtered data.
(Service Cloud case ID: 00773700) The migration process fails to migrate bots that contain more than 96 conditions in a single If command. Workaround: Split the If command into two If commands in Enterprise 11 and then migrate the updated bot.
If you create a bot that has invalid JSON tags with an Error Handling action (Try/Catch) in it, and if the Bot validation service is enabled (ON) in the Settings > Bots page, when you run the bot, the bot fails because of a preprocessing error. Workaround: In the Bot editor, open the bot that displays the error. Select and click any line of code, edit it, and save it. For example, if you have created a bot using the Comment action, select and click the Comment action, edit it by entering a space in the comment box, and then click Save. When you run the bot now, it no longer displays a preprocessing error.
In SOAP Web Service, selecting the Raw data parameter and using the Build Xpath option to extract values from SOAP response to store the XML output in a variable does not work. Workaround: Enter the Xpath expression manually instead of using the Build Xpath option in the selected response.
When you try to establish a secure SQL connection in the Linux environment by choosing the Enable option in the Database Configuration > Secure Connection field, the Linux installer fails to import the SSL certificate, and the connection fails. Workaround: Select the Disable option in the Database Configuration > Secure Connection field. The Linux installer successfully establishes a secure SQL database connection.
In Linux environment, the file upload functionality of AARI on the web fails with an access denied error. This error occurs because the filestorage directory is not automatically created to store the files. Workaround: Create the filestorage directory in the Automation 360 repository path and assign the appropriate permissions as outlined in the following steps: Navigate to the Automation 360repository path: /opt/automationanywhere/automation360/appdata/Server Files Enter the following commands in the Linux console: `sudo mkdir storageservice` `sudo chown -R crkernel:controlroom storageservice` `sudo chmod -R 775 storageservice`
When you upgrade the Control Room from the previous version, the Task bots runs metric on the Home dashboard page does not display the historical count of tasks bot that ran in the earlier version. It shows only the count of task bot runs from the upgraded Control Room.
When you use the Recorder to capture objects on applications running on Microsoft Edge Chromium with Internet Explorer mode, use Recorder conditions in the bot to check whether the element exists in the application, try to capture UI elements in the application based on the result of the condition, and run the bot, then the bot always goes to the next action because the Recorder condition is unable to locate the UI element in the application. Workaround: Use the Image Recognition condition instead to locate a UI element in an application.
Copying Form variables across bots by using the Copy to shared clipboard option is not supported.

The following table lists limitations from previous releases that are also applicable to this release:


Limitations from previous releases
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 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.
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: 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.


Security fixes
Service Cloud case ID	Description
00836486, 00942844, 01264029	Disabled the module for caching that was using credential authentication.

AARI (Automation Anywhere Robotic Interface)


What's new
New query filter in Query Requests and Query Tasks actions Use the new filter now available in the Query Requests and Query Tasks actions of the AARI Web package to filter query requests and tasks by team name in the AARI web interface.
Team name filter You can filter your tasks and requests by team name in the Task and Request pages in the web interface, respectively. Select the Team label from the filter and search by team name to view the teams assigned to a task or request. Filter and search for a request \| Filter and search for a task
Support for audit logs (Service Cloud case ID: 00801166) You can now view the audit logs and refer to events relating to requests, teams, scheduler, process setups, bot setups, human tasks, and bot tasks that you have created, deleted, updated, submitted, or recovered. Audit log
Enhancement to user task assignment in Human Task In the process editor, the Auto-assign this task option in Human Task provides the following alternatives: The user who created the request: The task is automatically assigned to the user creating the request in the web interface. The user who opens this task: The task is automatically assigned to the user who opens the task in the web interface. This feature helps to reduce conflicts in assigning a task to oneself, particularly in case of specialized users such as Validator for whom the action of opening a task is equivalent to assigning the task to oneself.
Enhancement to team setup You can now simultaneously add multiple users with similar roles (custom role) to the AARI team in the web interface. The custom role in the Control Room is now aligned with a team in the AARI web interface, and the enhanced team setup works as follows: The users added with the role are assigned a Member role in the team. The role cannot be changed to Owner or Admin. You cannot view these users in the Users tab of the Team page. If a user is both part of a role and added manually to the team, their role in the team will be the same as the role assigned to them manually. For example, if a user is a member, they will continue to have the Member role whereas if the user is an owner, they will be assigned the Owner role in the team. If the user is no longer part of a role, the user will also not be a part of the team. Also, the Team page is now enhanced with navigation options at the top so that you can navigate through the various tabs (General, Users, Roles, Processes, and Bots). Use the General, Users, and Roles tabs to create teams and add users to them. The Processes and Bots tabs display the processes and bots assigned to teams, respectively. Team management \| Create an AARI team and assign team roles to members
Bot setup support The AARI Admin can use the Bot Setup page to view the bots that are assigned to a team, assign teams to a bot, and edit bots to remove or reassign teams. Attended Bot Runners who can view all the bots that are checked in to the Public workspace can now view the bots that are assigned to teams in AARI Assistant. Bot setup
Enhancement to the form logo You can now use the Logos in footer field to select up to two separate logos that are displayed in the footer of the form during bot runtime.
Add rules to various form elements When you are creating or editing a form in the form builder, you can now add rules to the following form elements by using the Form rules tab: Checkbox Date Document Dropdown Label Number Password Radio Button Rich Text Editor Text Area Text Box Time For the Checkbox and Radio Button elements, the rules are triggered only if the corresponding presets are selected. For example, if a form has two mutually exclusive options, such as Yes and No, the rules associated with these options are triggered only when you select one of the two options. Add rules to form elements
Updates to triggers The following triggers are now available to run a bot: Process trigger: Starts a bot when the status of the specified process in Microsoft Windows meets one of the following preset conditions: Starts Stops Add a process trigger Service trigger: Starts a bot when the status of the specified service in Microsoft Windows meets one of the following preset conditions: Starts Stops Resumes Pauses Is running Has stopped Is paused Add a service trigger Window trigger: Starts a bot when the specified application window meets one of the following preset conditions: Opens Closes Add a window trigger


What's changed
Enhancement to Create a Request package In the Create a Request package, you can now browse and choose the public process for which you want to create a request. With this enhancement, you can choose the public process without having to contact the AARI admin for the URI of the public process and enter the URI manually. This feature also simplifies mapping process inputs for initial form fields. AARI Web package


Fixes
Service Cloud case ID	Description
00800192	You can now use an email trigger to start a bot without any issues, even when the email server is POP3.
00801428	You can now add an email trigger to a Gmail account to start a bot for new email messages.
00736309, 00765069, 00784362	For documents that are in the .csv, .xlsx, or .xls format, you can now use a file trigger to start a bot when a document is modified.
00796697	When you check in a bot, the associated private event trigger is now retained.
00802427	With the Bot Creator license, you can now view all the requests and tasks regardless of your role or other licenses assigned to you.
00829282	When you create a request in the web interface, your bot now runs properly and does not encounter any processing issues, such as an idle status that prevents progress on your bot.
--	When more than four text box elements of a form are populated in a process, the document is now displayed correctly on the document viewer irrespective of the state of the text box elements. Previously, the document was not displayed.
--	When you delete a request from the Request tab and it is sent to the recycle bin, the related task from the Task tab is now removed.
--	When you use the Date and Boolean type If/Else conditions, there is now parity in validating conditions between a bot and a process. Also, the String type If/Else condition now allows the target values to be empty. Previously, validation for Date and Boolean type conditions were not supported when used in a process and the target values could not be empty.
--	Issues with the Hyperlink element in the Human Task are now fixed. The Hyperlink element now works correctly with the following behaviors: If the hyperlink URL is empty, either at design time or when passed from the process, the hyperlink is now unavailable. Previously, the hyperlink was set to the Control Room domain. If the Hyperlink element is used in a Human Task that is read-only, data is now passed from the process editor to the form. Previously, the data from the process editor was ignored.
--	For Time element in forms, when the Use the local time when form is first displayed and Make field required options are selected, the time element now treats the system time as the default value and can be modified in the initial form.

The following table lists the limitations identified in the current release:


Limitations in this release
The web interface lacks the Set Warning action and the Set Error action for the Checkbox, Dropdown, Radio Button, and Rich Text Editor elements.
For the Date and Time elements, when the date and time are included in a rule, changes made to the rule format are not reflected in the rules section. As a result, when you try to process a rule that contains that date and time, bot execution fails. Workaround: Open the rules editor, expand the corresponding rules, and select a respective data value from the calendar before saving. Do not change the format after the date and time element are included as part of any rule. You can also delete older date and time elements.
When you use the Select File element in your forms and select the Make field uneditable option, the element can still be edited.
When you run a bot using the Team Members command from the AARI Web package, you will be prompted with an exception error.
In AARI on the web interface, if you create a variable by using the Form type in a bot, you cannot copy that variable to another bot even when you select the Keep or Overwrite option.
When a user is a member of a team by role (the user was added to a role in the Control Room then the role was synced to the team), the user will not be able to view updated information on the user interface of the request or task details. This is due to the Request page not automatically refreshing. Workaround: Refresh the Request page to view the updated request or task details.

The following table lists limitations from previous releases that are also applicable to this release:


Limitations from previous releases
In an SDS setup, when you create a request to upload a file, the upload fails and a `SecurityTokenInvalidException` error message is displayed.

Discovery Bot


What's new
Install Bot Agent seamlessly If you have not already installed the Bot Agent, you are now prompted to install the Bot Agent from the Processes tab. Follow the screen instructions to install the Bot Agent. After the installation, you are prompted to enable a Chrome plug-in in order to proceed with your recording tasks. Prerequisites for Discovery Bot
Enhancement to auto-generated opportunities You can now begin reviewing an auto-generated opportunity from the Opportunities tab when at least one process recording is submitted for review. Review the auto-generated opportunity and choose to create a custom opportunity from an auto-generated opportunity, as required. Review opportunities, convert to bot, and generate PDD
New recordings for review for custom opportunity You can now review new recordings submitted by a Discovery Bot user for a custom opportunity. You can choose to accept or dismiss the recording updates as part of the custom opportunity work flow. This option allows you to quickly and easily review new recordings in real time as the recordings are submitted by the user for that process. Review opportunities, convert to bot, and generate PDD
Enhancements to Opportunities page The opportunities page is now updated to include an opportunities evolution map, along with other graphs, to help you review and analyze data for a potential opportunity for automation. Use the opportunities evolution map to help guide you on which opportunities to automate first. 分析自动化机会
Download PDD document from the Recordings page You can now download and export a PDD document from the Recordings page. After you submit a recording for an analyst to review, the PDD begins processing in the background automatically. When the PDD is generated, the field changes from Processing PDD to Download. You can now choose to download the document in Word format, PDF, or both. An email notification to the business user is also sent to the email address on file. The Download PDD for Word or PDF document is also available for a custom opportunity from the Opportunities list table. Review opportunities, convert to bot, and generate PDD


Fixes
Service Cloud case ID	Description
--	You will now receive one email notification for a PDD generated in Automation 360 v.21. Previously, when you upgraded to Automation 360 v.22, you might have received multiple email notifications about the PDD generated in Automation 360 v.21.

The following table lists the limitations identified in the current release:


Limitations in this release
During upgrade the PDD documents are not getting generated intermittently, for both recordings and opportunities. Workaround: Edit the flowchart for the custom opportunity that displayed an error, and save. Or alternatively, create a new opportunity from the existing opportunity.
Depending on the memory available in your system, the PDD (in PDF or Microsoft Word format) can support up to 250 recorded steps captured in the document. If a process is recorded with more than 250 steps, the PDD generation periodically stops functioning. Workaround: Regenerate the PDD and click Download.
The PDD PDF document for business users and analysts does not display Unicode characters when entered in the opportunity name and step description fields.
Cloud users: For an auto-generated or custom opportunity, an error is displayed from the Recordings table intermittently. Workaround: Refresh the page to update the Recordings table.
After you save your changes, if you update a process workflow by adding or removing steps, the values from the Overview pane might not be updated to include the recent changes. Workaround: Refresh the page to update and include the recent changes made to the opportunity values in the Overview pane.
Cloud users: Creating a custom opportunity with more than 250 steps is not supported.
Linux users: The recording flowchart section is not displayed in the PDD.
For On-Premises deployments, when a self-signed or wildcard certificate is used for the Control Room setup, the Processes page fails to load. Workaround: Update or add the Control Room certificate to the Java Credential Store on all your Bot Runner machines for the Processes page to load. Add Control Room certificate to Windows certificate stores
For custom opportunities and recordings, there is an intermittent issue and error generating PDD message. You will not be able to access and download a PDD and instead see an Error generating PDD error message. Workaround: Only for custom opportunities, you can either create a new opportunity in your workflow using the Save As option OR edit the your workflow chart with any small change and save it. After doing this, the PDD generation will work properly.

IQ Bot


What's new
Document Automation released in Community Edition Community Edition now offers limited features from the Document Automation version. This version is integrated with the Community Control Room. When you create a learning instance, IQ Bot automatically creates RPA bots to extract and download the data and an AARI process to manage the end-to-end process. Validation now takes place in AARI tasks. Use IQ Bot Community Edition to extract data from invoices in English. Community Edition
IQ Bot standard forms enhancements IQ Bot now provides the following enhancements related to standard forms: You can now extract data from tables. You can now use container deployment. Using IQ Bot for standard forms
CyberArk support The On-Premises installation process now enables users to connect to CyberArk to store their custom keys for encrypting and decrypting IQ Bot data. Note: This feature is only available for new installations. Installing IQ Bot in Custom mode
Classifier enhancements You can now create custom document groups in a learning instance. This reduces the possibility of an OCR failing to detect fields in a document, which will cause the Classifier to create a document group unnecessarily or send the document to a wrong group. About the Classifier
View the number of pages purchased and uploaded The IQ Bot dashboard now shows the number of pages purchased and uploaded in the current license period. Review the dashboard


What's changed
(Service Cloud case ID: 00656822) Credential Vault integration is now available for passwords in IQ Bot.


Fixes
Service Cloud case ID	Description
00727633	When you import or export learning instances, duplicate classification entries no longer occur.
00768600, 00783773, 00815546, 00795424 , 00788180	When you import an existing IQ Bot archive (IQBA) file, you can now use the Overwrite option without any issues.
00770638, 00746545, 00827208, 00746545, 00827208	When you import the IQ Bot archive (IQBA) file, you will no longer see duplicate group entries.
00773631	(On-Premises) After you install, restart the IQ Bot services using a different Windows user. Prior to this release, IQ Bot services could not be run with a different account post-installation, resulting in an incompatible FilePath for Liquibase changesets.
--	You can now access IQ Bot > Explore IQ Bot with a refined user experience. Previously, a user could not navigate back to the Control Room landing page. Users can now access the landing page by clicking the back button.
00766454	The Manage your IQ Bots no longer displays the incorrect UI for trained bots currently in production. Previously, it displayed a link to create a bot.
00804476	When you update the classification report, you can now successfully classify the documents in IQ Bot. Previously, because the classification report field name was longer than 75 characters, document classification failed.
--	On the Learning Instance summary page, the number of unclassified documents and the number of documents uploaded are now accurately displayed.
00695159	An internal exception in the RemoveLines module that caused documents to remain unprocessed has now been fixed, and documents no longer remain unprocessed due to this error.
00806557	You can now successfully assign a group to a bot, and move the bot to production. Previously, in a few instances, the IQBA contained multiple bots for the same group, making the state of the bot inconsistent.
-	You can now download output files without any issues even if API requests are sent frequently to the database during download for any standard forms learning instance.
-	You can now use the IQ Bot Extraction action without any issues even if you selected the Only for me option when you installed the Bot Agent.
--	For bots associated with standard forms learning instances, you can now successfully upload a large number of documents.
00776423, 00829915, 00949561	You can now use a custom port (apart from port 1433) to run the Migration Assistant tool on the database server.
--	When documents with lengthy non-English (for example, Japanese) file names fail, the issue is now logged in the bot_launcher.log file.
00814577, 00812300, 00823120	An unexpected error that occurred due to large unnamed RabbitMQ message queues has been fixed and the user can now navigate to the Learning instances page.
--	The MLScheduler service is now disabled on IQ Bot Cloud, and the system no longer slows down or stops responding. Previously, the auto-correction and auto-suggestion features, which are part of the MLScheduler service, used extensive system resources and caused the system to slow down or stop responding.
--	The Process Document action in IQ Bot Extraction package now fetches the ABBYY pre-processing settings from the IQ Bot server and applies these settings to the classic side of processing during bot runtime.

The following table lists the limitations identified in the current release:


Limitations in this release
When a bot is moved to production, documents become unavailable in the validator output folder or the following error is displayed: `Project not found/No documents found.` Workaround: Ensure that the length of the filename does not exceed 100 characters.
In a cluster setup, sometimes, a specific document in production becomes unavailable. Also, an incorrect learning instance summary is displayed. Workaround: Upload again and reprocess documents that are not successfully processed.
In the Designer, some documents for the user-created group and their extraction results do not load. Workaround: Reload the Designer. To obtain extraction details on On-Premises, go to the Settings.txt file and increase the value for See extraction timeout.
On the learning instance details page, because of the 150-character limit, the group labels for user-created groups are not displayed completely.
When you create an IQ Bot administrator user, if you do not include the AAE_Basic role along with the AAE_IQ Bot Admin role, that administrator user cannot add a new group to a learning instance. Workaround: Ensure that you include the AAE_Basic role along with AAE_IQ Bot Admin role in the Control Room.
For a standard forms learning instance, if you upload a document that contains a table with an invalid field, that document is sent to the Failed folder.
For the Concatenate Images action in the IQ Bot Pre-processor package, no output is generated if a filename contains more than 256 characters. Workaround: Use English language characters and number convention.
When you use the IQ Bot Extraction package along with other OCR-based commands (such as IQ Bot Pre-processor, IQ Bot Classifier, AISense Recorder, and OCR) in a single bot, the bot fails. Workaround: Ensure that you create separate bots for IQ Bot Extraction, and do not run IQ Bot Extraction in conjunction with other packages that include the 12.2 Abbyy OCR.
From a learning instance of custom domain type with manual groups, when you export the IQBA file to another instance, the manual Group Label is not exported. Without a manual group label, it is difficult to differentiate between system-generated groups and manual groups in new learning instances.

The following table lists limitations from previous releases that are also applicable to this release:


Limitations from the previous releases
If you have a document with a large number of pages (> 100), an error message is displayed intermittently when you click See extraction results for an existing learning instance.

Bot Insight


What's changed
To change the language in Bot Insight, you must apply the language settings from either your browser or operating system that is configured to the language of your choice. Internationalization, localization, and language support


Fixes
Service Cloud case ID	Description
00799262, 00826862	An error no longer occurs when you run a bot that includes special characters in the name and the analyze command. Previously, bots with an ampersand (&) in the name and the analyze command included encountered an error.
	The calculation in the device dashboard is now corrected to show an accurate maximum of 100 percent for daily utilization. Previously, a calculation error caused the device dashboard to display over 100 percent.

The following table lists the limitations identified in the current release:


Limitations in this release
Bot Insight is not compatible with Microsoft Internet Explorer 11. For a list of alternative browsers, see RPA Workspace 的浏览器要求.

Important: For information about the packages supported with this release, see View package versions available in the Control Room.