Enterprise A2019.20 Release Notes
- Updated: 2023/03/08
Enterprise A2019.20 Release Notes
Release date: 20 April 2021
Review what's new and changed, and the fixes and limitations in the Enterprise A2019.20 release. Build 8846 is for Cloud and Build 8815 is for On-Premises. IQ Bot A2019 is on Build 8815.
- Migrated bots failing to execute due to preprocessing error (Service Cloud case ID 00760877, 00761211)
- Unable to deploy bots because the resource path exceeds the maximum length supported by Microsoft (Service Cloud case ID 00764731, 00763373, 00765172, 763334)
- Migration
- Enterprise A2019
- Automation Co-Pilot
- Discovery Bot
- IQ Bot
- Bot Insight
Updating to this release
You can update to this release from the previous three releases (that is, from n−3 releases, where n refers to the latest release). The following builds are certified for update to this release:- Build 8147 (v.19)
- Build 7560 (v.18)
- Build 7103 (v.17)
For details on how to update, see Update Automation 360 to latest version.
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.
Migration features
| Enterprise 11 and Enterprise 10 features |
|---|
|
Select folders for migration (Service Cloud case ID:
00689307) In the Bot Migration Wizard, you can now select folders that contain bots (Task Bots and MetaBots) that you want to migrate to Enterprise A2019. As a result, you no longer have to migrate individual bots from that folder. |
|
Migrate MetaBots with screens
Migrate MetaBots that contain screens as assets. You can migrate screens based on HTML, MSAA, Java, .Net technologies and use credential variables. |
Migrate bots with the following
attributes
|
| Enterprise 11 only features |
|---|
|
Migrate bots that use SAP BAPI to automate
SAP-related tasks
Migrate bots that use SAP BAPI to automate the SAP-related tasks. The SAP commands are migrated to equivalent actions of the SAP BAPI package, and the username, password, and hostname attributes used to connect to the SAP server in the Enterprise 11 bots are migrated as credential variables in Enterprise A2019. |
|
Retain legacy behavior of $Excel Cell Row$ system
variable
Use the Use "Excel Cell Row" legacy behavior option in the Bot Migration Wizard to retain the legacy behavior of the $Excel Cell Row$ system variable used in bots created in versions earlier than Version 11.3.1 after they are migrated to Enterprise A2019. |
Migrate bots with the following
attributes:
|
Enterprise A2019
| What's new |
|---|
|
Support for IPv6
addresses
You can install Enterprise A2019 in distributed load balancer cluster mode in an IPv6 network to comply with your organization's infrastructure and information security requirements. The following are not supported:
|
|
Switch device registration between
Control Room
instances
You can now switch your device registration between multiple instances of the Control Room without reinstalling the Bot Agent. This setting is applicable to single user devices installed at the system or user level. Switch device registration between Control Room instances | Switch Bot Agent to a different Control Room |
|
New permission to attest device user name (Service
Cloud case ID:
00576058) Use the new permission to assign a default device to a user name to bypass credential validation when you deploy a bot on unattended Bot Runners. The permission is applicable to default device users with an unlocked and active user session. |
|
Resource threshold settings to optimize bot deployments
Configure resource threshold settings in the Control Room so that the system deploys the next bot only when the system resources on the device are within the specified thresholds. Specify the settings at the Control Room level for all devices, and customize these settings at each device level. |
|
Reduce bot startup
time
You can now reduce the bot startup time using settings in the Control Room to preload the most frequently used packages in the automation on all user devices when they connect to the Control Room. |
|
Express queue in workload
automation
You can now quickly create workload automation queues with default parameters in the Control Room by using the Create express queue option in the Queues page. |
|
Group filters for Active Directory
users
You can provide additional filters for the Users directory as part of the um.properties file. As a result, you can filter the security groups that are in the Users directory for role mapping in the Control Room. |
|
Automate SAP-related tasks using SAP BAPI
Use the actions available in the SAP BAPI package to automate SAP-related tasks using SAP BAPI. |
|
Default names for output
variables
When you configure an output variable for the following packages, the Control Room shows a descriptive default variable name. If you create several output variables, subsequent variable names are appended with a -1, -2, -3, and so on to avoid duplication.
|
|
PDF split with blank pages supports
scanned image documents (Service Cloud case ID:
00683923) Use the PDF Split action to separate a blank page from pages with scanned images. With pixel-based split, you can now use Split document to split a PDF with blank page separators for scanned (image-based) documents. |
|
SMTP port range expanded to include ports 1 through
65535
The Email package now supports ports in the range of 1 through 65535 for the SMTP server. You can use the Send email action by configuring the SMTP port in this range. |
New actions in the Active Directory
package
|
|
Enhancement to Create user action in Active Directory
package
You can now use the Create user action to create an Active Directory user with password. |
|
Universal Recorder expanded support and new
features
Use the Universal Recorder to perform the following:
|
|
Support for new
languages in variable names
You can now use Czech, Danish, Dutch, Finnish, French, German, Hungarian, Italian, Norwegian, Polish, Portuguese, Romanian, Spanish, and Swedish characters in variable names. |
|
Search and add child bot in the parent bot
Search for a child bot in the public and private workspaces so that you can add it in the parent bot. You can search for the child bot from the Bot editor and the Run action of the Task Bot package. |
|
Obtain information
about user that deployed the bot
Use the AATaskInvoker system variable to return the username, first name, last name, and email of the user that ran or scheduled the bot. If the bot is deployed to an attended Bot Runner, this variable returns information about the logged-in user. If the bot is deployed by a trigger, this variable returns information about the user who set the trigger. |
Git restoration
enhancements
|
|
View version history of Task Bots
You can now view the version history of your Task Bots to identify relevant changes performed by other users to your Task Bots during a specific date and time along with the check-in messages. |
|
External key vault support
Use external key vaults to securely store and retrieve credentials using a third-party key manager such as CyberArk and AWS Secrets Manager. External Key Vault support for AWS Secrets Manager and CyberArk for Bootstrap (database credentials,) and System (Service account credentials, Active Directory service account credentials, and SMTP credentials). |
|
New condition in If
package
(Service Cloud case ID:
00536088, 00690073,00717514, 00737243, 00702383)
Use the new Window with same title does not exist or Window with same title exist condition available in the If package to verify whether a window with the same title exists or whether the window title has changed. |
|
Google packages are now generally
available
Google Calendar, Google Drive, and Google Sheets packages are now generally available in Enterprise A2019, with a major change to the authentication method:
|
| What's changed |
|---|
|
Bots wait for Internet Explorer to fully render in Mouse
package
Bots (including bots migrated from Enterprise 11) that use the Mouse package now wait for the Internet Explorer to finish loading the page before executing the Click action. This prevents the bots from failing while the page is loading. |
|
Interface change in the Edit variable
window
When editing a variable, if you deselect the Use as input, Use as output, or Constant (read-only) check box, a message now informs you of the impact of this change and requests you to confirm this update. |
|
Enhancement to audit log
entries
(Service Cloud case ID:
00656155) The audit log entries are now enhanced to display the Item Name and Event Type for import, export, check-in, and check-out requests. |
|
The .atmx file not downloaded during migration
The migration process does not download the .atmx file if the associated bot is used as a child bot in the parent bot. The Download CR file action from the File package is no longer added in the migrated bot to download the depended bot (.atmx) file during migration. |
|
Option to either upgrade Recorder
package version or downgrade to older Google Chrome extension
Bots that use the Recorder package version 2.0.5 or older to automate in the Google Chrome browser, now need to be updated to use a Recorder package version that is newer than 2.0.5. This is only necessary for Bot Runner devices that have the new Google Chrome extension (ID:kammdlphdfejlopponbapgpbgakimokm) installed, and have not previously run bots that use the Recorder package version 2.0.5 or older. If you do not want to upgrade the Recorder package, you can manually install the old Google Chrome extension. See Google Chrome extension troubleshooting. |
| Build 8846 | |
|---|---|
| Service Cloud case ID | Description |
| 00764731, 00763373, 00765172, 763334 | You can now deploy bots and dependent files stored in a repository with a file path that exceeds the maximum supported character length (256 characters) for your Windows operating system. |
| 00714248 | Only those Bot Runners and Bot Creators expressly configured as credential vault consumers for a given bot can use that bot. |
| 00751728 | When you migrate Enterprise 11 bots that use the String Operation command with the space character as a delimiter, the extracted value now retains the space and works properly. Previously, after migration, the space from the String Operation command was removed. |
| 00760877, 00761211 | Bots that are migrated, modified, and scheduled now successfully deploy without a preprocessing error. Previously, migrated bots failed to execute due to the following preprocessing error: Attribute type ANY is not supported. |
| Build 8840 | |
|---|---|
| Service Cloud case ID | Description |
| 00747869, 00750571, 0744918 | When you create a bot using a loop with the Recorder Capture action to perform operations on the Chrome browser, the bot now executes without any disruption. Previously, the bot failed to run and displayed an error. |
| 00733635, 00743082, 00750865 | When you run a bot that contains the Excel Advanced > Find action, the found cell is now active and subsequent actions can perform operations on that active cell. |
| 00723075, 00717920 | When a bot encounters a workbook that contains links to cells in other workbooks, the system suppresses the Excel pop-up message so that the bot can run without interruption. |
| 00746651, 00757879 | After migrating bots, you can successfully run the bots without any preprocessing error. Previously, using variables inside brackets failed to process the task. |
| 00742159, 00743092 | The Excel Advanced Set cell and Delete cell actions now select the correct cells when the cell address column name contains more than one letter. |
| 00743636 | The Excel Advanced Set cell, Delete cell, and Go to cell actions now support all ranges. Previously, the actions encountered errors with ranges greater than AB1:AB100. |
| 00726030 | Bots can now use the Recorder to capture objects that contain characters that are not valid in XML. |
| Build 8815 | |
|---|---|
| Service Cloud case ID | Description |
| 00750668 | A workload bot is no longer stuck in a queue, and the device does not display a Pick up at run time status. |
| 00733227 | Control Room database tables are now created when you use the restored 11.x database while installing Enterprise A2019. |
| 00733720 | Bot Migration Wizard no longer encounters an error when processing a large bot for migration. Previously, this issue was encountered when a large bot was downloaded to the Bot Runner device for migration from the Control Room and the connection between the Bot Runner device and Control Room was reset. |
| -- |
Bot Scanner is now updated to include scenarios that were previously failing after migration. As a result, some bots might be moved from the list of bots that can be migrated to the list of bots that cannot be migrated in the output report. This can decrease the number of bots that can be migrated to Enterprise A2019. |
| 00703679, 00711398, 00729399 | Enterprise 11 or Enterprise 10 bots that use the string variable or an object captured from Internet Explorer whose property is null or empty no longer encounters an error after these bots are migrated. |
| 00667326 |
Bot Scanner no longer becomes unresponsive
when scanning bots for any of the following reasons:
|
| 00731068, 00737025 | An error is no longer encountered when you run a bot that contains multiple variables that return a number value in the same command after that bot is migrated. |
| 00720261 | An error is no longer encountered when you run a migrated bot that contains a special character. |
| 00713303 | In a migrated bot that uses the Run Task command, when you run a subtask within the main task and the subtask name contains Unicode characters, the bot now executes successfully without any error. Previously, the bot failed and displayed an error message. |
| 00691133 | You can now successfully delete migrated bots in your private workspace without encountering any issue. Previously, an error message was displayed when a migrated bot was deleted in the private workspace. |
| 00736166 | Previously, when the migration process was initiated, the process sometimes remained in the In progress status in the Bot Migration Wizard. Now the process starts running. |
| 00730131 | Bots that use the Run Script command with the $Clipboard$ system variable as an input or output variable no longer encounter errors when you run these bots after they are migrated to Enterprise A2019. |
| 00726833 | Enterprise 11 Work Items and queues that are associated with bots that use the Variable Operation command no longer encounter an error after the first item in the queue is processed successfully after migration to Enterprise A2019. |
| -- | Bot Scanner no longer encounters an error when scanning MetaBots that contain the Object Cloning command that is commented out and the MetaBot is trying to find the play mode from those commented out commands. |
| 00716557 | An error is no longer encountered when you run a MetaBot in Enterprise A2019 that was created in Enterprise 10, migrated to Enterprise 11, and then migrated to Enterprise A2019. |
| 00710569 | When you migrate a MetaBot that contains screens as assets from Enterprise 11 to Enterprise A2019, Japanese characters in the object properties are now displayed correctly in the migrated bots. Previously, the Japanese characters in the object properties were garbled in the migrated bots. |
| 00702262 | The Historical activity page now shows a detailed error message that specifies the cause of the error and the line where the error is encountered for bots that are migrated from Enterprise 11 and use the Error Handling command. |
| 00703513, 00708988 | Parent bots that use the Run action of the Task Bot package with the Upon error, start next repetition option selected no longer encounter an error if their child bots encounter an error at runtime and do not return the output variable to the parent bot. Previously, parent bots encountered an error if the child bots did not return the output variable to the parent bots because the child bots encountered an error during runtime. |
| 00702601 | A bot that uses an array variable that contains a system variable and which returns an integer no longer encounters an error after that bot is migrated. |
| 00707801 | You can now migrate an Enterprise 11 bot that contains Mouse Click to capture the coordinates of a maximized window. Previously, the bot with a Mouse Click encountered an issue during migration because the window left and top parameters were set to negative values for maximized windows. |
| 00710315, 00728228, 00729082, 00744242 | Migrated bots that use the Object Cloning command with legacy technology to capture objects with multiple lines of text now work properly, without any issues. |
| 00716650 | When you migrate an Enterprise 11 bot that contains an Excel command with two Excel sessions in it, the Get column name or Get row number actions now displays the correct values in the output. Previously, the actions set the wrong session values in the migrated bot if it contained two Excel sessions. |
| 00711148 | Enterprise A2019 installation no longer fails if there is a space in the data and log path (for example, D:\Automation Anywhere\ProgramData). And, the following error message is no longer displayed: Control Room database tables fail to create. |
| 00708902 | You can now use the Google Drive package to upload files in the Google Shared Drive. Use only the Folder ID option to upload files to a shared folder in the drive and enter the ID of the shared folder. Previously, an error occurred when a user tried to upload a file in the shared folder in the Google Drive. |
| 00735479 | When you create a bot that has a dependency with a long repository path that exceeds the maximum limit of 256 characters and when you run the bot on the Bot Runner machine, the bot now displays a message, prompting you to reduce the length of the file path. Previously, the bot execution failed without any message providing the reason for the failure. |
| 00727406 | You can now successfully send an email in HTML format with an HTML attachment using the Email server. Previously, when an email was sent in HTML format along with an attached HTML file, the email body content and the content of the attached file were merged. As a result, only the attachment was seen in the mail without the body content. |
| 00707734 | In the App Integration package, when you use the Capture text of window action in a Japanese browser, the window title now displays properly for Japanese language. Previously, the output was not displayed correctly in the Japanese text format. |
| 00699149,00707670 | You can now use the Unzip action of the Folder package and execute your bots on a Windows 10 server. Now, if two Windows users with different device credentials try to deploy a bot on the same machine, the deployment does not fail. Previously, if a user deployed the bot on the same machine with a different user profile, the bot failed to execute. |
| 00695224, 00730472, 00739431 | When you use the Find Image in a Window action in the Image Recognition package, image files are now deleted from the Temp location and storage space is freed after bot execution. Previously, the image files were not deleted from the Temp location and as a result disk storage ran out of space. |
| 00709162 | The CSV/TXT Open action now works without encountering any issue even if there are blank values in the last row of the .txt file. Previously, if there were blank values in the last row of the file, the bot encountered an issue. |
| 00711124 | In the Email package, when you use the Connect action, add a loop, and select For each in mail box to read emails as the Iterator option, a new line is no longer deleted and correctly displays the email content. Previously, the new lines were deleted when the mail was sent and received in plain text format. |
| 00673049 | In the SAP package, if an error is encountered when the Connect action is used to connect with a SAP system, the error is now captured in the Try and Catch blocks. Previously, the connection issue was not captured in the Try and Catch blocks in the action. |
| 00697215 | A bot now executes successfully when you use the Throw action with an expression. Previously, when an expression such as $number.ToString$ was used in the Exception message field of the Throw action, the bot encountered a preprocessing error. |
| 00714260 | Runtime errors are no longer displayed when you use the
following:
|
| 00704547 | The Pause action of the Task Bot package now works properly when you use it as the last task in the bot. Previously, the bot did not wait for the task to complete if the Pause action was used as last task in the bot. |
| 00675344 | A Task Bot now performs better when you use the Terminal Emulator Send text and Send key actions to execute a bot. Previously, the Task Bot took a long time to complete the execution. |
| 00699650,00716648 | When you use Image Recognition actions to execute a bot and if the bot fails during execution, the captured source and target images are stored in C:\ProgramData\AutomationAnywhere\BotRunner\Logs\IR with a maximum of 10 source and target image pairs. Now, when the maximum limit is reached, the oldest image pairs are overwritten with new images. Previously, the image logs were not overwritten. |
| 00716817 | A bot now executes successfully when you use the PDF Extract text action to extract structured text from PDF files. Previously, bot execution failed to extract structured text if it contained Thai characters. |
| 00717204 | You can now use a credential from the Credential Vault in the URI field of the REST Web Service actions. |
| 00682726, 00678580, 00695359, 00684985 | You can now use the Universal Recorder to automate in Oracle Fusion Middleware applications. Previously, an issue with the Java API caused the Recorder to select the entire window instead of the specific object. |
| 00693770 | Fixed an issue where numbers extracted from an SQL database to a data table variable were automatically converted to scientific notation. |
| 00669959 | You can now select the same start date and end date when you schedule bots with the Run repeatedly option () in the Control Room. |
| 00702841, 00700915 | Disconnected devices are now displayed in the Control Room () when you filter the devices list by Status as Disconnected. |
| 00707318, 00711529 | Work items in an active queue are now processed and you no longer have to delete the active queue and create another queue after you upgrade from a previous release to this release. |
| 00705046 | Bots that include embedded dependent files instead of a zipped folder are no longer queued intermittently for deployment on Bot Runner devices. |
| -- | Disabled tenant IDs or removed tenants that are later reused on the same deployment with a different tenant might produce a licensing error. This conflict is now removed and deboarded tenants in later reuse no longer generate the error. |
| 00685926 | When you import an exported bot into the private workspace and check in the imported bot, the bot is now checked in successfully without any issues. Previously, the check-in failed due to a metadata validation error. |
| 00682025 | When a bot or a file is modified in the public workspace, the cloned dependent file in the private workspace now reflects the changes and the bot executes successfully. Previously, the cloned dependent file did not reflect the changes and the bot execution failed. |
| 00726018 | The Google Drive Upload file action now uploads files to subfolders. |
| 00715080, 00731152 | You can now perform concurrent unattended bot deployment on a multi-user device with multiple user sessions running simultaneously. |
| -- | A non-admin Bot Agent user now remains connected to the Control Room and is not disconnected frequently. |
| 00709737 | Actions in the Google Sheets package now support worksheets that contain empty cells. |
| 00710354 | A hibernate exception error is no longer displayed when you log in to the Control Room as an admin user. |
| 00732178 | You can now check out bots from folders with
similar names but in different letter cases and edit the bots in your private workspace in the Control Room. For example, if there is a folder named Automation1 in the public workspace and a folder named automation1 folder in the private workspace, you can now check out bots from the Automation1 folder in the public workspace. |
| -- | Bots are now deployed on a multi-user device in a non-admin user session when another admin user session is also active on the device if auto-login setting in the Control Room is set to lock the session after the bot finishes executing from an existing unlocked session. |
| 00719407 | During a cluster installation of Enterprise A2019 on Red Hat Enterprise Linux, the installer now uses the same user ID across all cluster nodes. |
| 00703325 | The log file permission for an Control Room installed on Linux now maps to the crkernel user. Previously, it was mapped to the root user. |
| -- | When you access the Control Room with the Login with Windows option selected, you must now enter the FQDN to log in successfully. |
| 00732141, 00722919,00743006 | When you preload a package, after the download is complete, the completion status updates in the page and the pending record is no longer displayed in the page. |
| 00731376 | When you migrate MetaBot logic, if there is case mismatch in the variable name and the mapping variable, variables are no longer created twice. As a result, a preprocessing error does not appear when you execute the task. |
| Now, the migration of run logic with CV variables is supported. | |
| Now, when using the Date system variable in the File folders command, a migrated bot is no longer failing. | |
| When migrating bots (v11.x to A2019) with OC properties more than 64KB, such properties will be truncated and the bot will be migrated. | |
| Fixes | ||
|---|---|---|
| Build | Service Cloud case ID | Description |
| 8846 | 00764731, 00763373, 00765172, 763334 | You can now deploy bots and dependent files stored in a repository with a file path that exceeds the maximum supported character length (256 characters) for your Windows operating system. |
| 8846 | 00714248 | Only those Bot Runners and Bot Creators expressly configured as credential vault consumers for a given bot can use that bot. |
| 8846 | 00751728 | When you migrate Enterprise 11 bots that use the String Operation command with the space character as a delimiter, the extracted value now retains the space and works properly. Previously, after migration, the space from the String Operation command was removed. |
| 8846 | 00760877, 00761211 | Bots that are migrated, modified, and scheduled now successfully deploy without a preprocessing error. Previously, migrated bots failed to execute due to the following preprocessing error: Attribute type ANY is not supported. |
| 8840 | 00747869, 00750571, 0744918 | When you create a bot using a loop with the Recorder Capture action to perform operations on the Chrome browser, the bot now executes without any disruption. Previously, the bot failed to run and displayed an error. |
| 8840 | 00733635, 00743082, 00750865 | When you run a bot that contains the Excel Advanced > Find action, the found cell is now active and subsequent actions can perform operations on that active cell. |
| 8840 | 00723075, 00717920 | When a bot encounters a workbook that contains links to cells in other workbooks, the system suppresses the Excel pop-up message so that the bot can run without interruption. |
| 8840 | 00746651, 00757879 | After migrating bots, you can successfully run the bots without any preprocessing error. Previously, using variables inside brackets failed to process the task. |
| 8840 | 00742159, 00743092 | The Excel Advanced Set cell and Delete cell actions now select the correct cells when the cell address column name contains more than one letter. |
| 8840 | 00743636 | The Excel Advanced Set cell, Delete cell, and Go to cell actions now support all ranges. Previously, the actions encountered errors with ranges greater than AB1:AB100. |
| 8815 | 00750668 | A workload bot is no longer stuck in a queue, and the device does not display a Pick up at run time status. |
| 8815 | 00733227 | Control Room database tables are now created when you use the restored 11.x database while installing Enterprise A2019. |
| 8815 | 00733720 | Bot Migration Wizard no longer encounters an error when processing a large bot for migration. Previously, this issue was encountered when a large bot was downloaded to the Bot Runner device for migration from the Control Room and the connection between the Bot Runner device and Control Room was reset. |
| 8815 | -- |
Bot Scanner is now updated to include scenarios that were previously failing after migration. As a result, some bots might be moved from the list of bots that can be migrated to the list of bots that cannot be migrated in the output report. This can decrease the number of bots that can be migrated to Enterprise A2019. |
| 8815 | 00703679, 00711398, 00729399 | Enterprise 11 or Enterprise 10 bots that use the string variable or an object captured from Internet Explorer whose property is null or empty no longer encounters an error after these bots are migrated. |
| 8815 | 00667326 |
Bot Scanner no longer becomes unresponsive
when scanning bots for any of the following reasons:
|
| 8815 | 00731068, 00737025 | An error is no longer encountered when you run a bot that contains multiple variables that return a number value in the same command after that bot is migrated. |
| 8815 | 00720261 | An error is no longer encountered when you run a migrated bot that contains a special character. |
| 8815 | 00713303 | In a migrated bot that uses the Run Task command, when you run a subtask within the main task and the subtask name contains Unicode characters, the bot now executes successfully without any error. Previously, the bot failed and displayed an error message. |
| 8815 | 00691133 | You can now successfully delete migrated bots in your private workspace without encountering any issue. Previously, an error message was displayed when a migrated bot was deleted in the private workspace. |
| 8815 | 00736166 | Previously, when the migration process was initiated, the process sometimes remained in the In progress status in the Bot Migration Wizard. Now the process starts running. |
| 8815 | 00730131 | Bots that use the Run Script command with the $Clipboard$ system variable as an input or output variable no longer encounter errors when you run these bots after they are migrated to Enterprise A2019. |
| 8815 | 00726833 | Enterprise 11 Work Items and queues that are associated with bots that use the Variable Operation command no longer encounter an error after the first item in the queue is processed successfully after migration to Enterprise A2019. |
| 8815 | -- | Bot Scanner no longer encounters an error when scanning MetaBots that contain the Object Cloning command that is commented out and the MetaBot is trying to find the play mode from those commented out commands. |
| 8815 | 00716557 | An error is no longer encountered when you run a MetaBot in Enterprise A2019 that was created in Enterprise 10, migrated to Enterprise 11, and then migrated to Enterprise A2019. |
| 8815 | 00710569 | When you migrate a MetaBot that contains screens as assets from Enterprise 11 to Enterprise A2019, Japanese characters in the object properties are now displayed correctly in the migrated bots. Previously, the Japanese characters in the object properties were garbled in the migrated bots. |
| 8815 | 00702262 | The Historical activity page now shows a detailed error message that specifies the cause of the error and the line where the error is encountered for bots that are migrated from Enterprise 11 and use the Error Handling command. |
| 8815 | 00703513, 00708988 | Parent bots that use the Run action of the Task Bot package with the Upon error, start next repetition option selected no longer encounter an error if their child bots encounter an error at runtime and do not return the output variable to the parent bot. Previously, parent bots encountered an error if the child bots did not return the output variable to the parent bots because the child bots encountered an error during runtime. |
| 8815 | 00702601 | A bot that uses an array variable that contains a system variable and which returns an integer no longer encounters an error after that bot is migrated. |
| 8815 | 00707801 | You can now migrate an Enterprise 11 bot that contains Mouse Click to capture the coordinates of a maximized window. Previously, the bot with a Mouse Click encountered an issue during migration because the window left and top parameters were set to negative values for maximized windows. |
| 8815 | 00710315, 00728228, 00729082, 00744242 | Migrated bots that use the Object Cloning command with legacy technology to capture objects with multiple lines of text now work properly, without any issues. |
| 8815 | 00716650 | When you migrate an Enterprise 11 bot that contains an Excel command with two Excel sessions in it, the Get column name or Get row number actions now displays the correct values in the output. Previously, the actions set the wrong session values in the migrated bot if it contained two Excel sessions. |
| 8815 | 00711148 | Enterprise A2019 installation no longer fails if there is a space in the data and log path (for example, D:\Automation Anywhere\ProgramData). And, the following error message is no longer displayed: Control Room database tables fail to create. |
| 8815 | 00708902 | You can now use the Google Drive package to upload files in the Google Shared Drive. Use only the Folder ID option to upload files to a shared folder in the drive and enter the ID of the shared folder. Previously, an error occurred when a user tried to upload a file in the shared folder in the Google Drive. |
| 8815 | 00735479 | When you create a bot that has a dependency with a long repository path that exceeds the maximum limit of 256 characters and when you run the bot on the Bot Runner machine, the bot now displays a message, prompting you to reduce the length of the file path. Previously, the bot execution failed without any message providing the reason for the failure. |
| 8815 | 00727406 | You can now successfully send an email in HTML format with an HTML attachment using the Email server. Previously, when an email was sent in HTML format along with an attached HTML file, the email body content and the content of the attached file were merged. As a result, only the attachment was seen in the mail without the body content. |
| 8815 | 00707734 | In the App Integration package, when you use the Capture text of window action in a Japanese browser, the window title now displays properly for Japanese language. Previously, the output was not displayed correctly in the Japanese text format. |
| 8815 | 00699149,00707670 | You can now use the Unzip action of the Folder package and execute your bots on a Windows 10 server. Now, if two Windows users with different device credentials try to deploy a bot on the same machine, the deployment does not fail. Previously, if a user deployed the bot on the same machine with a different user profile, the bot failed to execute. |
| 8815 | 00695224, 00730472, 00739431 | When you use the Find Image in a Window action in the Image Recognition package, image files are now deleted from the Temp location and storage space is freed after bot execution. Previously, the image files were not deleted from the Temp location and as a result disk storage ran out of space. |
| 8815 | 00709162 | The CSV/TXT Open action now works without encountering any issue even if there are blank values in the last row of the .txt file. Previously, if there were blank values in the last row of the file, the bot encountered an issue. |
| 8815 | 00711124 | In the Email package, when you use the Connect action, add a loop, and select For each in mail box to read emails as the Iterator option, a new line is no longer deleted and correctly displays the email content. Previously, the new lines were deleted when the mail was sent and received in plain text format. |
| 8815 | 00673049 | In the SAP package, if an error is encountered when the Connect action is used to connect with a SAP system, the error is now captured in the Try and Catch blocks. Previously, the connection issue was not captured in the Try and Catch blocks in the action. |
| 8815 | 00697215 | A bot now executes successfully when you use the Throw action with an expression. Previously, when an expression such as $number.ToString$ was used in the Exception message field of the Throw action, the bot encountered a preprocessing error. |
| 8815 | 00714260 | Runtime errors are no longer displayed when you use the
following:
|
| 8815 | 00704547 | The Pause action of the Task Bot package now works properly when you use it as the last task in the bot. Previously, the bot did not wait for the task to complete if the Pause action was used as last task in the bot. |
| 8815 | 00675344 | A Task Bot now performs better when you use the Terminal Emulator Send text and Send key actions to execute a bot. Previously, the Task Bot took a long time to complete the execution. |
| 8815 | 00699650,00716648 | When you use Image Recognition actions to execute a bot and if the bot fails during execution, the captured source and target images are stored in C:\ProgramData\AutomationAnywhere\BotRunner\Logs\IR with a maximum of 10 source and target image pairs. Now, when the maximum limit is reached, the oldest image pairs are overwritten with new images. Previously, the image logs were not overwritten. |
| 8815 | 00716817 | A bot now executes successfully when you use the PDF Extract text action to extract structured text from PDF files. Previously, bot execution failed to extract structured text if it contained Thai characters. |
| 8815 | 00717204 | You can now use a credential from the Credential Vault in the URI field of the REST Web Service actions. |
| 8815 | 00682726, 00678580, 00695359, 00684985 | You can now use the Universal Recorder to automate in Oracle Fusion Middleware applications. Previously, an issue with the Java API caused the Recorder to select the entire window instead of the specific object. |
| 8815 | 00693770 | Fixed an issue where numbers extracted from an SQL database to a data table variable were automatically converted to scientific notation. |
| 8815 | 00669959 | You can now select the same start date and end date when you schedule bots with the Run repeatedly option () in the Control Room. |
| 8815 | 00702841, 00700915 | Disconnected devices are now displayed in the Control Room () when you filter the devices list by Status as Disconnected. |
| 8815 | 00707318, 00711529 | Work items in an active queue are now processed and you no longer have to delete the active queue and create another queue after you upgrade from a previous release to this release. |
| 8815 | 00705046 | Bots that include embedded dependent files instead of a zipped folder are no longer queued intermittently for deployment on Bot Runner devices. |
| 8815 | -- | Disabled tenant IDs or removed tenants that are later reused on the same deployment with a different tenant might produce a licensing error. This conflict is now removed and deboarded tenants in later reuse no longer generate the error. |
| 8815 | 00685926 | When you import an exported bot into the private workspace and check in the imported bot, the bot is now checked in successfully without any issues. Previously, the check-in failed due to a metadata validation error. |
| 8815 | 00682025 | When a bot or a file is modified in the public workspace, the cloned dependent file in the private workspace now reflects the changes and the bot executes successfully. Previously, the cloned dependent file did not reflect the changes and the bot execution failed. |
| 8815 | 00726018 | The Google Drive Upload file action now uploads files to subfolders. |
| 8815 | 00715080, 00731152 | You can now perform concurrent unattended bot deployment on a multi-user device with multiple user sessions running simultaneously. |
| 8815 | -- | A non-admin Bot Agent user now remains connected to the Control Room and is not disconnected frequently. |
| 8815 | 00709737 | Actions in the Google Sheets package now support worksheets that contain empty cells. |
| 8815 | 00710354 | A hibernate exception error is no longer displayed when you log in to the Control Room as an admin user. |
| 8815 | 00732178 | You can now check out bots from folders with
similar names but in different letter cases and edit the bots in your private workspace in the Control Room. For example, if there is a folder named Automation1 in the public workspace and a folder named automation1 folder in the private workspace, you can now check out bots from the Automation1 folder in the public workspace. |
| 8815 | -- | Bots are now deployed on a multi-user device in a non-admin user session when another admin user session is also active on the device if auto-login setting in the Control Room is set to lock the session after the bot finishes executing from an existing unlocked session. |
| 8815 | 00719407 | During a cluster installation of Enterprise A2019 on Red Hat Enterprise Linux, the installer now uses the same user ID across all cluster nodes. |
| 8815 | 00703325 | The log file permission for an Control Room installed on Linux now maps to the crkernel user. Previously, it was mapped to the root user. |
| 8815 | -- | When you access the Control Room with the Login with Windows option selected, you must now enter the FQDN to log in successfully. |
| 8815 | 00732141, 00722919,00743006 | When you preload a package, after the download is complete, the completion status updates in the page and the pending record is no longer displayed in the page. |
| 8815 | 00731376 | When you migrate MetaBot logic, if there is case mismatch in the variable name and the mapping variable, variables are no longer created twice. As a result, a preprocessing error does not appear when you execute the task. |
| 8815 | Now, the migration of run logic with CV variables is supported. | |
| 8815 | Now, when using the Date system variable in the File folders command, a migrated bot is no longer failing. | |
| 8815 | When migrating bots (v11.x to A2019) with OC properties more than 64KB, such properties will be truncated and the bot will be migrated. | |
| Limitations |
|---|
| (Service Cloud case ID: 00822176)
When you create an RDP session on multi-user devices and enter a
custom port, RDP-based deployments will
fail. Recommended: Use the default port 3389 for RDP sessions. |
| When you create a bot
with Open and
Close browser actions
in a loop and select the Window option to
close the selected tab, an error might occur when you execute
the bot. Workaround: Use the Close action of the Window package instead of the Close action in the Browser package to close the window. |
| 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 will not be updated
automatically. The device is will be shown as disconnected in
the Control Room. Workaround:
|
| Configuring multiple IP addresses for Control Room nodes in a cluster is not supported
during installation in On-Premises deployments.
You
must manually configure the primary IP address in the
cluster.properties file. Add primary IP address for cluster | Configure additional IP address for a new cluster node |
| Bot deployment on multi-user sessions is not supported for workload automation. |
| Using an Enterprise A2019.20 SDS On-Premises Control Room with an Enterprise A2019.19 SDS Cloud Control Room is not supported. |
| When you run a bot containing a Capture action that uses the anchor object feature, your device DPI settings must match the settings at which you configured the anchor object. |
| The Control Room does not allow hyphens and underscores to be used interchangeably when creating and calling global value names. |
| When you migrate an Enterprise 11 bot that uses Object Cloning command with Silverlight technology and execute that bot in Enterprise A2019, the bot might fail with an error due to a play reliability issue. The same play reliability is also seen in Enterprise 11 when you use Object Cloning command with Silverlight plugins. |
| For actions that use
file input, when you select a network path using
Browse, bot execution
fails because the double backslash (\\) in the file location is
replaced with a forward slash. Workaround: Do not use the Browse option to select the file location. Instead, manually enter the complete file path. |
| When a Bot Creator, attended Bot Runner or unattended Bot Runner user logs in to the Control Room from their Bot Agent machine and if the package download option is enabled, the package download takes priority, and bot deployment waits until the package download is complete. This occurs only when the package is downloaded for the first time. |
| When a bot runs an automation in the Microsoft Internet Explorer browser, the Microsoft API responsible for the browser delay might encounter an exception, causing the bot to fail and a Chrome-related error message to appear in the Control Room. |
| (Service Cloud case ID: 00712808) Automation Anywhere related files are sometimes generated in C:\Windows\Temp. These files can be safely deleted. |
| For Enterprise 11 bots that contain an object that is captured using the Object Cloning command using the Image or the Coordinate play mode, the Set Text is performed on that object and the credential variable is used to set text for the object. The credential variable for these bots is not migrated when the bots are migrated to Enterprise A2019. |
| If you use the Set text
action in the
action to enter data into a text box, when you
run the bot, the data appears over the old data
in the text box and is not entered. The old data is not cleared
from the text box because the application requires a physical
event to clear the old data. Workaround: To ensure that the data is entered into the text box, along with the Set text action, add a value greater than 0 in the Time between keystrokes field. |
| When you use the Recorder to capture an object, set the waiting time for detecting the object to less than 30 seconds in the Keep trying for (seconds) field, and run the bot, the Recorder waits for a minimum of 30 seconds by default to detect the object. |
| When you use the
Recorder to capture objects on an
application that is installed on a virtual machine, finish the
recording after the objects are captured, and relaunch the Recorder, the bot inserts
the actions recorded earlier instead of launching
the Recorder. Workaround: Refresh the Bot editor or run the bot to launch a new session to start recording again. |
Automation Co-Pilot for Business Users (Automation Co-Pilot)
| What's new |
|---|
|
Get Storage file
action
The new Get Storage file action in the Automation Co-Pilot Web package enables you to download storage files to a bot device. |
|
Upload files in initial forms
or
tasks
Add the Select File element to forms to enable users to select and upload files in the initial forms or tasks in the web interface. Users can browse to upload a new file or replace an existing file. The uploaded file is shown as a hyperlink and redirects users to a new tab when opened. |
|
Hyperlinks support for initial
forms or
tasks
Use the new Hyperlink element to add links to forms and access them in initial forms and tasks. |
|
Configure a scheduler user
for each process (Service Cloud case ID:
00713786) As an Automation Co-Pilot administrator, you can now configure a scheduler user for each process to allocate the Control Room resources (devices and unattended Bot Runners) on the web interface. By default, the Global scheduler user is selected if a scheduler user is not configured for individual processes. |
|
Update to properties
panel for human task (Service Cloud case ID:
00718109) As a Bot Creator, you can choose to not configure any actions in the human task by selecting the Make the form read-only check box in the Properties panel. The human task does not require any input and it is executed automatically to the next task. |
|
Bookmark any page as landing
page for Automation Co-Pilot on the
web
The web interface is now enhanced to a new multiple page system so that you can directly bookmark any page (Requests, Tasks, or Recycle Bin) as your landing page. Also, the tabs in the web interface have been removed so that the requests are opened one at a time and not simultaneously. To perform multiple tasks, you can open the requests pages in different browser tabs. |
|
Navigation enhancement in Automation Co-Pilot on the web
The web interface is now enhanced with a side navigation pane so that you can easily navigate to various pages (Processes, Requests, Recycle Bin, and Tasks). |
|
New processes page
(Service Cloud case ID: 00694786)
As an Automation Co-Pilot user, navigate to your assigned processes and create new requests by using the new Processes page in the web interface. Use the navigation bar to quickly access the page. |
Enhancements to the Button
element
|
|
Enhancement to the form
logo
You can now use the Logos in footer field option to select up to two separate logos that are displayed in the footer of the form during bot runtime. |
| What's changed |
|---|
|
Enhancement to the delete
process
An Automation Co-Pilot administrator or a user with the Delete from Public permission can now delete a process in the public workspace. When the process is deleted from the public workspace, it is removed from the process management page in the web interface. Additionally, if the process is already assigned to any Automation Co-Pilot user or team, access is removed after the process is deleted. |
|
Variable selector window
update
The variable selector is now organized by Variable Source, Variable Type, and Variable sections. The variable source contains a request or task. The variable type is now an interface option for you to select an input, output, or meta types. The variable option specifies the variable names and type. |
|
Request variable
source
The variable selector now enables users to select a Request variable source with an Input (previously InitialData) and Meta variable types. Create a process automation in Process Composer | Supported variable types in Process Composer |
|
Insert variables to existing
text
You can use the variable selector in the process editor to insert or add variables without replacing the existing texts. |
|
Filter update
In the web interface, when you filter or search for keywords, the filter user interface now updates and reflect the filter criteria accordingly. For example, if you search for the ending status of requests, the filter shows Status: Pending. |
| Fixes | |
|---|---|
| Service Cloud case ID | Description |
| 00702607 | If you have a Message box action within a trigger loop, you can now use the Run from here option to run the bot without any error messages. |
| 00725237 | Error messages are no longer displayed when the Dropdown element in the form is populated with dynamic values during bot runtime. |
| 00733978 | Forms with read-only elements can now be submitted successfully without any issues when the value of the form field exceeds 100. |
| - | If you select any of the Advance behavior options in the Dropdown element, error messages are no longer displayed during bot runtime. |
| -- | A Bot Task can now pass data to the next task (Human Task or Bot Task) if it contains Japanese characters in its output variable name. Previously, English characters had to be used for the variable name in the Bot Task. |
| -- | In a cloud environment, the Automation Co-Pilot web interface now displays the correct screen for the selected locale. Previously, the screen was not displayed correctly for the selected locale. |
| Limitations |
|---|
| In the process editor, the
If/Else condition of string type does
not allow the source and target values to be empty. As a result,
you cannot validate if a string variable is
empty. Workaround: Create an empty string output variable for the bot. Use this variable as the target value to compare with a form or bot source variable so that the validation in the If/Else condition does not fail. |
When you enter data in a form of your
process that contains a hyperlink, the data is ignored when you
try to submit the form. The hyperlink instead displays the
following behaviors:
|
Discovery Bot
| What's new |
|---|
|
Search for a
business process from the Processes
page
You can now use the search field to help you locate a specific process by name. The field is not case-sensitive. The search field is available from the Processes page. |
|
View all captured
images from the screenshot modal
window
You can now navigate across all captured screenshots when you click an image in full size from the modal window. Click the pagination located below the image to select a step number or use the right or left arrows to quickly display all captured images. |
|
Process Discovery
package is included in default
packages
The Process Discovery package is now included in the default packages. You can preload the default package when you connect to your device. Preloading the package helps to speed the start time of the recorder the first time you begin recording a process |
|
Recorder
enhancements
You can now perform actions such as double-click, drag-drop, click and hold, and text select when recording a business process. Actions performed using keyboard strokes are displayed in the Data field. Double-click is captured by the recorder and displayed in the screenshot from the Recordings page. Note: The Discovery Bot recorder does not
capture the drag-drop and click and hold actions from the
Recordings page. To include these
actions performed during the recording, you can document the
individual steps in the Step
description text field for the analyst.
|
|
Support for IPv6
addresses
IPv6 addresses are now supported for Discovery Bot. |
|
Linux
support
Discovery Bot is now supported on Red Hat Enterprise Linux and Linux CentOS platforms. |
|
Support for high
availability
Discovery Bot now supports high availability deployment. |
| What's changed |
|---|
|
Changing default repository path for custom
installation
For custom installation, you can now change the default repository path location to a new location on your server after installation. |
| Fixes | |
|---|---|
| Service Cloud case ID | Description |
| -- | You can now export a PDD for an opportunity with 2000 steps by using the Download PDD option from the Opportunities page. |
| Limitations |
|---|
| When Tab is used to move across fields to a password-type field, the entered data is displayed as clear text, for example, when you move from the Username to Password field. Review the text in the Data field for confidential information before you submit the process. |
| Some actions might not be supported during a recording session, for example, when you click through the Network tab in Inspect mode using Chrome. For such unsupported actions, pause the recorder, complete the action, and then resume the recording. |
| When you record a process with 1000+ steps, the
Recordings page takes some time to
load.
Workaround: Depending on your environment, you
can perform one of the following actions:
|
IQ Bot
| What's new |
|---|
|
Enhancement to the
Document Classifier
package
The Train Classifier action now provides an option to retrain the documents using an existing model file. |
| What's changed |
|---|
|
IQ Bot Pre-processor
actions
renamed
The names of all the available actions in the IQ Bot Pre-processor package are now changed. For example, the Get barcodes action is now renamed as GetBarCodes. |
|
Download all processed documents without any timeout
(Service Cloud case ID:
00587817) You can now download all your processed files from the Amazon S3 server to your local machine without causing any timeout, irrespective of the number of files. Even when you choose the Delete files from the server after downloading option and if your download fails, a compressed .zip file containing the failed documents is available for downloading again. |
Enhancements to IQ Bot APIs (Service
Cloud case ID: 00688683, 00688678, 00688675)
APIs to upload files, check file status, and downloading CSV file (A-People login required) |
|
IQ Bot license renamed
The license required to run IQ Bot is now renamed to IQBot Platform from the previous Cognitive Platform. |
| Fixes | |
|---|---|
| Service Cloud case ID | Description |
| 00708806 | You can now save documents of up to 20 MB after validating, without any issues. |
| 00662968 | Fixed an issue that caused the gateway service to become unresponsive. |
| 00644948 | When you now upload a document in production, deadlocks no longer occur in the system and documents are correctly sent to the Validator. |
| 00707965 | When you now migrate from IQ Bot Enterprise 11 to A2019 using the Migration Assistant tool, all database tables are correctly migrated, without any errors. |
| 00715124 | IQ Bot now deletes temporary files downloaded from Amazon S3 server in the C:\windows\temp\ folder when they are no longer required. As a result, storage is no longer consumed by these temporary files. |
| -- | Logs are now available for the IQ Bot node servers in the C:\Users\Public\Documents\Automation Anywhere IQBot Platform\Logs\ folder. |
| -- | IQ Bot now displays the correct error message when you refresh the extraction results page for a learning instance when its associated bot is moved to production. |
| -- | When creating a table on the Designer
page, if you click See Extraction results
without completing the table creation, the correct error message
is now displayed. Previously, the following incorrect message was displayed: Preview will be opened in a new tab. |
| -- | When a bot is deleted and you click the Test bot option on the Bots listing page, the following correct error message is now displayed: Bot not found. |
| -- | Python logic is now correctly applied on all the tables. Previously, IQ Bot failed to execute Python logic for tables other than the default one. |
| -- | You can view more granular logs for troubleshooting RabbitMQ v3.8.18 issues. These logs are now stored in the
C:\Users\Public\Documents\Automation Anywhere
IQBot Platform\Logs\RabbitMQ folder, depending on
the log level, log size, and the rotation limit. If any error occurs in the RabbitMQ v3.8.18 connection, those crash logs are stored in C:\Users\Public\Documents\Automation Anywhere IQBot Platform\Logs\RabbitMQ\log folder. |
| -- | When you now create a user role with 2-byte non-English characters, services no longer fail to execute. |
| -- | If there is an existing database, IQ Bot installer now does not check for the db_creator role for that user. |
| -- | A user with AAE_IQ Bot Validator role and
AAE_Basic role can now successfully launch
and validate documents in the IQ Bot
Validator. |
| Limitations |
|---|
| IPv6 addresses are not supported for IQ Bot, so ensure that you use IPv4 addresses only. |
| If you try to apply Python logic to a linked column between two tables, an error message is displayed for the linked column in the second table and the applied logic fails. |
| If you add a blocked library to a
custom Python logic and click Test Run
for any field, an error message is displayed on the designer
page. Workaround: Remove the blocked library from the Python logic. |
| If you use the Overwrite option to import a learning instance, all the available bots and groups are imported. |
| When you use the Process documents action from the IQ Bot Extraction package to run a bot through workload management, the Current Action tab displays Downloading additional resources along with your command instead of IQ Bot extraction in the In progress activity page. |
| Average processing time increases when you use the IQ Bot Extraction package on a document with more than 30 pages. |
| Running existing bots
that use the IQ Bot Pre-processor
package might fail after you upgrade to this
release. Workaround: Because the names of the available actions in the IQ Bot Pre-processor package have changed, delete the existing actions in the bots and update them with the new names before running the bot. |
| (Service Cloud case ID: 00601790) You cannot register IQ Bot when the Control Room is installed on a Linux machine. |
| When you run a bot that has the IQ Bot Extraction package, the activity information under does not display the details correctly. |
| If you use the File Download
API option, the json response you
receive does not have a valid format. Workaround: This issue occurs because the : (colon) is replaced by = (equal sign) in the json key value. After you receive the json response, use these options:
|
| When you try to sort the PagesUpload column in the tab, an error message is displayed. |
|
On the Designer, if you resize the system identified region (SIR) of an auto-mapped field, the values from the resized selection are not captured in the corresponding value field.
Workaround:To update the content of an auto-mapped
field:
|
Bot Insight
| What's new |
|---|
|
AAE_Admin role access to operations API from Power BI connector
The Power BI connector now provides the AAE_Admin user role access to the botrundata operational API. With this role, you can connect to the botrundata API and extract operational metrics to be analyzed and visualized within Power BI. |
|
Enhancements to the publish (production)
dashboard
Users with the AAE_Bot Insight Admin and AAE_Bot Insight Expert role can now edit the published dashboard. You can use the save as option to save the production dashboard as a custom production dashboard and add widgets to your custom dashboard. You can also delete a default production dashboard and a custom production dashboard. |