Enterprise A2019.19 Release Notes
- Updated: 2024/04/25
Enterprise A2019.19 Release Notes
Release date: 11 February 2021
Review the new features, changed features, fixed features, security fixes, deprecated features, and known limitations in the Enterprise A2019.19 release. Enterprise A2019.19 Build 8147 is available for On-Premises and Build 8145 is available for Cloud. IQ Bot is on Build 8098.
- System variables that are displaying blank in the action field (Service Cloud case ID 00737695, 00737698)
- Editing the table size when creating a new table variable in On-Premises (Service Cloud case ID 00725978, 00727695, 00736105)
- Issues editing a bot in the Bot editor and opening the packages listing page that includes special characters (Service Cloud case ID 00733529, 00739634)
- Assigning a bot from the private workspace to a file variable (Service Cloud case ID 00727695)
- Actions in the Image Recognition package not allowing the use of files with .PNG extension and files with uppercase letters in the extension (Service Cloud case ID 00734972, 00734266)
- Variable names in uppercase changing to lowercase, hyphen changing to underscore, and variable not being displayed if it contained an uppercase character (Service Cloud case ID 00734784, 00734842, 00734999)
- Bots not getting deployed on a multi-user device when the user session is signed out and no active session existed (Service Cloud case ID 00727228, 00722888, 00732830, 00732835, 00733877, 00733362, 00726489, 00733070, 732959, 733160, 733269,733321, 733391, 733435, 733438, 733451, 733680, 733765, 733770, 733790, 733940, 00734067)
- Child bots encountering an error if they contained the Find window in window action of the Image Recognition package (Service Cloud case ID 00727031, 00730358, 00733607, 00733544, 0073464)
- Use of variables with camel case names in the Data Table, List, and Loop packages (Service Cloud case ID 00733263,00733459, 00733007, 00733988, 00734168, 00733141, 00733074, 00733087, 00733001,00734019)
For more information, see the Fixed features sections for Enterprise A2019 and Automation Co-Pilot.
Migration features
| Enterprise 11 and Enterprise 10 features |
|---|
|
Review messages in Migration Assistant
The Migration Assistant displays review messages for migrated bots. Open the migration assistant for a bot to review messages for that bot. |
|
Migrate MetaBots with screens
Migrate MetaBots that contain screens as assets. You can migrate screens based on UI Automation technology and captured using the Object play mode. |
|
Review messages in Bot Scanner
report
The Bot Scanner report shows review messages about the behavior change in commands that are used in bots that can be migrated to Enterprise A2019. |
|
Stop, or pause and resume migration
You can stop, or pause and then resume the migration process from the bot launcher and the page. |
|
Migrate bots that use capture scrollable
text action in App Integration
command
Enterprise 11 and Enterprise 10 App Integration commands that capture text from an application window with a vertical scroll bar are migrated to the action in Enterprise A2019. |
| Enterprise 11 only features |
|---|
|
Map output of PDF integration
command to multiple variables
The output of an Enterprise 11 bot that uses the PDF integration command is mapped with multiple variables in the equivalent actions of the PDF package after the bot is migrated to Enterprise A2019. |
Migrate bots that use the following
attributes:
|
Migrate bots that use the following options in the Active Directory
command:
|
| Enterprise 10 only features |
|---|
|
Migrate latest version of Enterprise 10
bots enabled with version
control
You can now migrate the latest version of bots from your Enterprise 10 Control Room configured with SVN version control to Enterprise A2019. Use the Copy 10.x data option to copy the latest version of the Enterprise 10 bots to Enterprise A2019 and then use the Bot Migration Wizard to migrate the bots to Enterprise A2019. Copy Enterprise 10 data | How Enterprise 10 data is copied to Automation 360 |
Enterprise A2019
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.
| New features |
|---|
|
Auto-login settings
Use the auto-login configuration in the Control Room to reduce bot startup time by reusing an existing user session. Configure auto-login in the Administrator settings for all devices or customize it from the Devices page for each device.
|
|
New CPU utilization and device memory
settings
Configure the CPU utilization and device memory threshold value in the Control Room settings to determine whether to deploy bots on devices or not. |
|
Install Bot Agent on devices without
administrator
privileges
You can now choose to install the Bot Agent on user devices with either local user privileges (without administrator privileges) at the local user level or administrator privileges at the system level. Install Bot Agent and register device | Create device pools | Users When you install the Bot Agent at the user level, the device will not be available as a default device for another user or for device pool selection during bot deployment. For more information, see Bot Agent known limitations. |
|
New diagnostic utility for Bot Agent
Use the Bot Agent diagnostic utility to perform diagnostic checks on Bot Runner devices and to resolve Bot Agent connectivity issues. |
New features in Data Table
package
(Service Cloud case ID: 00656843,
00707635)
|
|
New action in App Integration
package
Use the Capture scrollable text action to extract text from the selected window or any control within the selected window and save it to a variable. If you click any control within the window, then text from that specific control is extracted. If you click outside the window, then all the text from that window is extracted. |
|
New
encoding combo box option in Terminal Emulator for VT Series
To send and receive Japanese text, you can now use the Encoding and CodePage combo boxes when you connect to the Terminal Emulator for the VT series terminal type. |
|
New actions in Active Directory
package
Use the following actions in the Active Directory to automate a task:
|
|
New system
variable for new line character (Service Cloud case ID:
00669232, 00672775, 00673578) Use the $String:Newline$ system variable to add a new line character. This variable adds a new line character in various applications regardless of the operating system of the device. |
|
Zero-size form for
Enterprise A2019 (Service Cloud case ID:
00677611) The Run action uses the zero-size form with name AAZeroSizeForm that can be used by DLLs to identify zero-size forms created by Enterprise A2019. |
|
Enhancement to
define parent path in Active Directory
When you establish a connection with an LDAP server, you can now select the LDAP path by connecting to the server. |
|
Obtain information
about Run-As user after bot deployment
Use the AATaskExecutor system variable to return the username, first name, last name, and email of the user that ran the bot. If the bot is deployed on 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 associated with that Bot Runner license. |
Enhancements to
the Recorder
Universal Recorder supported applications and browsers | Actions performed on objects captured with Universal Recorder |
|
Multi-user device supported on Citrix Windows 10
Enterprise (Service Cloud case ID:
00526001) Multi-user device sessions are now supported on Windows 10 Enterprise on Citrix, enabling multiple users to access the same device at the same time. |
|
Event triggers on unattended Bot Runners
(Service Cloud case ID:
00681548) Ensure that you select the Reuse an existing session option for auto-login settings in the Control Room to use event triggers on unattended Bot Runners when a device is locked or is in a disconnected state (such as RDP). |
|
Auto Login support on Citrix VDI
(Service Cloud case ID:
00680200) Auto Login is now supported on Citrix VDI, which enables bot deployment in unattended mode. |
|
Restore bots from Git
repository
If your database is deleted or corrupted, the admin user can restore all your bots and the associated dependent files from the Git repository to your new empty database. |
|
Bot Deploy API checks for available devices in the order
of listed pool IDs
If you enter multiple pool IDs in the request body, the API checks the pools for available devices in the order that you listed the pool IDs. If none of the devices are available at the time of deployment, the automation is queued. |
| Changed features |
|---|
|
Enhanced security for multi-user
Bot Agent devices (Service
Cloud case ID: 00695858) The Bot Agent configured on multi-user devices for RDP-based deployments now uses the updated version of wfreerdp.exe for enhanced security. |
|
Deployment API enhancement
(Service Cloud case ID: 00655548) When you invoke a regular deployment API, if a RunAsUser is being used to deploy a bot, the deployment API will not deploy other bots until the RunAsUser is free to run the other bots. |
|
Status change initiates workload automation
deployment
When you change the status of a Work Item from Failed to New in the Control Room (Queues), the deployment of a workload automation in queue is initiated. |
|
Install Google Chrome
Enterprise extension offline with Bot Agent
(Service Cloud case ID:
00623511, 00689623, 00715413) You can now install the extension for Google Chrome Enterprise offline from the Bot Agent setup and MSI files. |
|
ANSI as default encoding in Data Table
package
For text write operations, Data Table package > Write to file action supports ANSI as default encoding type. Bots created in the previous version of Enterprise A2019 with UTF-8 is not impacted by this change. |
|
Enhancement to PDF
package
In the PDF package, when you enter an incorrect page range in the Page range field and execute the bot, an error message is now displayed, requesting you to provide the correct page range. The message is displayed for the following actions:
|
|
Bots wait for Google Chrome web
page to load
When automating a task in the Google Chrome browser, bots now wait up to 30 seconds for the web page to load, and then run the subsequent action. When the page loads, bots search for the object for the duration specified in the Wait for control field. Waiting for the web page to fully render increases the bot's ability to identify the target object in the web page. |
|
Enhancement to desktop operations
When you create a bot and select an option for desktop operations, the data selected from the drop-down list now persists even when you navigate to other fields. |
Flow view updates in the Bot editor
(Service Cloud case ID: 00701626)
|
| Fixed features | ||
|---|---|---|
| Build number | Service Cloud case ID | Description |
| 8147 | 00737695 | When you insert a system variable into an action field, the variable now appears in that field. |
| 8147 | 00725978, 00727695 | When you create a table variable in On-Premises, the table expands to the full size of the window. Previously the table only showed three rows at a time. |
| 8147 | 00733529,00739634 | You no longer encounter any issues when you edit a bot in the Bot editor and open the packages listing page. Previously, if an installed package had an object name with a space (' ') character in it, the package listing page displayed an error. |
| 8145 | 00727695 | You can now assign a bot from your private workspace to a file variable. |
| 8145 | -- | When you create a variable in an action, the variable automatically appears in the field for which you created the variable. |
| 8145 | -- | You can now use .png files in actions in the Image Recognition package. |
| 8145 | 00734972, 00734266 | You can now select a Control Room file with uppercase letters in the file extension in the action. |
| 8145 | 00734784 | Variables names are now displayed correctly in the Bot editor List view; uppercase letters in the variable name are no longer changed to lowercase letters and hyphens are not changed to underscores. |
| 8145 | 00734842, 00734999 | Actions now display Boolean, date time, or list type variables if the variable name contains uppercase letters. |
| 8145 | 00727228, 00722888, 00732830, 00732835, 00733877, 00733362, 00726489, 00733070, 732959, 733160, 733269, 733321, 733391, 733435, 733438, 733451, 733680, 733765, 733770, 733790, 733940, 734067 | You can now deploy bots on a multi-user device when the user session is signed out and no active session (signed in, locked, or disconnected) exists either for that user or any other user. The following error message is no longer displayed on the View historical activity () page: Unable to perform auto-login for user <username>. |
| 8145 | -- | The Cloud migration utility no longer keeps running in the background if you close the utility when the Enterprise 11 data is being uploaded. |
| 8134 | 00727031, 00730358, 00733607, 00733544, 00734642 | You can now successfully execute bots when you use Image Recognition with the Find window in window action in a child bot. Previously, bot execution failed when you used Image Recognition with this action in the subtask. |
| 8134 | 00733263,00733459, 00733007, 00733988, 00734168, 00733141, 00733074, 00733087, 00733001,00734019 | The Data Table, List, and Loop packages now support variables with camel case names. |
| 8122 | 00713867 | Variables are now listed in alphabetical order in the Variables palette and in the Insert a value window that appears when you press the F2 key. |
| 8122 | -- | The Control Room now does not take time to launch, and the following error message is no longer displayed: An Unexpected Problem Occurred. |
| 8098 | 00689022, 00697417, 00697420, 00697079 | A Bot Agent device no longer disconnects from the Control Room that is configured on Microsoft Azure. The following error message is no longer displayed: disconnecting due to outstanding pong. |
| 8122 | 00719167, 00721731 | Tasks such as scheduling bots and connecting to user devices are not delayed in an Control Room hosted on Cloud. |
| 8098 | 00626595, 00680433 | The actions in the Image Recognition package no longer return an incorrect error message about the target image data type. |
| 8098 | 00698201 | Fixed an issue where bots were stuck in the preprocessing mode when the bot was used as a child bot in several running bots or was deployed back to back using the Deploy API. Now bots are deployed from the cache and fewer calls are made to the database, thus avoiding a database deadlock. |
| 8098 | -- | The Bot Scanner now displays the correct message for the MetaBot logic that contains credential variables that cannot be migrated to Enterprise A2019. |
| 8098 | 00687223 | An Enterprise 11 bot that passes a blank value as an input to the string, list, one-dimensional array, and two-dimensional array of string type variable used in a DLL no longer encounters an error when you run that bot after migrating to Enterprise A2019. |
| 8098 | 00677231 | A bot is no longer unresponsive if it contains an action to close the Google Chrome browser followed by an action to open the Google Chrome browser. |
| 8098 | 00687207 | When an Enterprise 11 bot contains objects captured using the Object Cloning command and that object has a property that contains an expression within the $ character, the Enterprise 11 bot no longer encounters an error after migration. |
| 8098 | 00689286 | The Bot Scanner no longer encounters an error when you scan an Enterprise 11 bot that contains the If command with the Windows control condition selected and is automating a task on a Microsoft Excel file. |
| 8098 | 00706438 | An error is no longer encountered when you are installing
Enterprise A2019 and:
|
| 8098 | 00708522 | An error is no longer encountered when you clone a dependent file of an Enterprise 11 bot after it is migrated to Enterprise A2019. The error is encountered only when the migrated bot contains a null description. |
| 8098 | 00626664 | You can now migrate bots that automate tasks in BMC applications. The migrated bots use the action to automate interactions with objects. |
| 8098 | -- | You can now select the regular expression Case insensitive option in actions that contain a window title field and successfully perform a recapture in the application window. |
| 8098 | 00688134 | In the Database package, Korean characters are now displayed properly when you use the Insert/Update/Delete action in an Excel file. Previously, the Korean characters were not displayed properly when the action was used. |
| 8098 | 00675749 | In the Email package, you can now forward an email using groupId or Alias. Previously, the mails were not sent by the SMTP server if the email address contained groupId or Alias in the To address field. |
| 8098 | -- | You can now use a double backslash (\\) in the Send text action of the Terminal Emulator and execute bots. Previously, when a double backslash (\\) was used in this action and the bot was executed, the terminal displayed a single slash (\). |
| 8098 | 00688692 | When you connect to the EWS server to read mails using Loop, the retrieved email now displays the content correctly per the selected mode (HTML or plain text formats). Previously, when connecting to the EWS server to read an email in HTML format, the email body displayed a blank output. |
| 8098 | 00659456 | In the Loop package, when you select For each file in folder as the Iterator option, the Note below the Assign file name and extension to this variable field now displays the key name in English. Previously, the key name in the Note was translated to the languages you selected. |
| 8098 | -- | A bot no longer runs intermittently when the focus changes from one window to another window and does not display the Type_015 Google Chrome plug-in error. |
| 8098 | 00683528 | In the Database package, single entries are now inserted in the database when you execute a store procedure to add rows in the table and the option Export data to CSV is selected. Previously, duplicate entries were added in the database. |
| 8098 | 00693664 | Fixed an issue where Japanese characters did not display correctly when input into a field that contained a variable. |
| 8098 | 00677167 | The locker Participants tab now shows only the assigned participants for that specific locker. Previously, the tab displayed the participants of the previously viewed locker, requiring the user to refresh the browser to see the correct participants. |
| 8098 | -- | The Control Room services can now be run using the non-administrator service account users. The Bad Gateway error message is no longer displayed. |
| 8098 | 00691232 | Fixed an issue that did not allow users to update the value of a file type input variable after saving the bot. |
| 8098 | -- | The Save option is now correctly enabled when users make any changes to the metadata, unique entity, or SAML assertion mode. |
| 8098 | -- | The username is no longer saved in the login window after the user logs out unless the user has selected the Remember my username option. |
| 8098 | 00682021 | When you check in a bot that has cloned bots as dependencies, the dependent files are no longer lost from the private workspace. Also, after the check-in, if you create a new bot using the same dependencies as in the earlier bot, the new bot executes successfully. |
| 8098 | -- | Work Items are now processed for workload automation after you add more Work Items to an existing queue. |
| 8098 | -- | Work Items are now reprocessed for workload automation after you change the status from failed to new. |
| 8098 | 00711410 | You can now migrate workload automations in an Control Room configured to use a manual mode for Credential Vault. |
| 8098 | 00667047, 00673289 | Auto-login for a user session no longer fails for bots deployed on virtual machines when the VDI session is disconnected or is in a locked state, and the following token error message is no longer displayed: An attempt was made to reference a token that does not exist. |
| 8098 | 00560593, 00585092 | Universal Recorder is now aligned with the Bot Agent, so the recorder can capture objects on devices with any proxy server configuration. |
| 8098 | 00675695 | When you use the Excel advanced package, the bot now opens an Excel file without any issues. Previously, the bots failed to open an Excel file in some scenarios due to internal hardware components. |
| 8098 | 00678567 | CSV formulaic entries are no longer permitted in data fields of web applications, such as device names. These fields are limited to accept alphabetic characters, numbers, hyphen, and underscore entries only. |
| 8098 | 00691551 | Turkish characters are now supported in user names. |
| Known limitations |
|---|
| When you update the Bot Agent from user
level to system level, the user is unable to capture objects
using recorder actions or from a window list in a Google Chrome browser. Workaround: Remove the registry entry for the user. Ensure the registry entry is in HKLM: Computer\HKEY_CURRENT_USER\SOFTWARE\Google\Chrome\NativeMessagingHost\Automation*. |
| When you uninstall the Bot Agent, the Bot Agent service and registry entry are not removed. Therefore,
subsequent Bot Agent reinstallations
fail. Workaround:
|
| When you install a Bot Agent at the user level, the user device is not registered as
admin.
Workaround: Before installing the Bot Agent, ensure that the user has write permission to the user profile folders (for example, C:\Program Files). |
| When you deploy a bot using a
custom package and if the package
has an object name with a semicolon (;) or percentage (%)
character in it, the bot execution fails.
Workaround: Do not use special characters such as a semicolon (;) or percentage (%) in the custom package name. |
|
Limitation for multi-user deployments with
auto-login
If the auto-login setting in the Control Room is set to lock the session when the bot finishes executing from an existing unlocked session, deployments will fail when you deploy a bot on a multi-user device with non-admin user session and another admin user session is also active on the device. Workaround: Restart the Bot Agent service from the Windows Start menu and log off from the admin user session. |
|
Bot Agent
installation
Starting from this release, when you install the Bot Agent at the local user level, keep the following in mind:
|
|
Bots encounter a Java heap space error when they
use the Excel basic
package to open an Excel file that is 20 MB or
larger. Workaround: Increase the Java virtual machine heap space to 8 GB:
|
| Bots wait a maximum of 30 seconds for an object to appear in the Google Chrome browser, regardless of the value in the Wait for control field in the action. |
Limitations in Cloud migration
|
| (Service Cloud case ID:
00737669) When you upgrade to this release, the Bot Agent is also updated. As a result, all
the event triggers associated with Bot Runner
(attended or unattended) users are stopped. Workaround: Bot Runner (attended and unattended) users must re-login to the Control Room to activate the associated event triggers. |
|
Enterprise 11
bots that use identical names for variables that
are differentiated by a hyphen or an underscore (for example,
L-Lower and L_Lower) encounter an error when you run them after
migrating to Enterprise A2019. Workaround: Update the name of one of the variables to a different name before migrating the bot. |
| String system variables do not
function in Email
action fields when the format is set to HTML.
Workaround: Use HTML tags that perform the
same function as the string variables. For example, instead
of |
|
When you insert a variable into an action field that contains other content, the
variable appears at the end of the content, regardless of the
cursor position. Workaround: Highlight the variable name, and then cut and paste it to the correct position in the action field. |
| (Service Cloud case ID:
00781974) In a Linux environment, some of the Control Room log messages are stored in the
/var/log/messages file instead of the
/var/log/automationanywhere directory.
As a result, disk space increases, and the services might stop
when the disk space is full. Workaround: Clear the messages file regularly to avoid a disk storage issue. |
Automation Co-Pilot for Business Users (Automation Co-Pilot)
| New features |
|---|
|
New filter task in the
process
editor
In the process editor, the Filter Task enables users to filter variables such as human or bot task output with a specific filter criterion. |
|
New process task in the
process editor
Use the new Process Task option in the process editor to call a subprocess within the main process. This feature enables you to separate tasks into different processes instead of including all the tasks in a single process. Multiple teams can now work at the same time on different tasks within the main process and remain segregated, without any conflicts. |
|
Hide a task or view
a hidden task
With a Bot Creator license, you can now perform the following:
|
|
Edit title in process
editor
Users can now edit the title in the process editor. |
|
Rich-text editor
updates (web
interface)
In the web interface, you can use rich-text editor features such as bold text, italics, underline, alignment, formatting, color, and size in tasks. |
|
Table element updates
(web
interface)
In the web interface, the Table element now supports the use of date, number, drop-down, and text values in tasks. |
|
Updates
to elements in form builder
The form builder now includes the following new elements:
|
|
Enhancement
to the Checkbox action
trigger
If a form with a Checkbox element is used within a trigger loop package, you can now use the Value selected and Value unselected trigger actions. |
| Changed features |
|---|
|
Create and view requests (Automation Co-Pilot
manager) An Automation Co-Pilot manager can create and view requests from processes that are assigned to the team they belong to or own. They can also create and view requests from processes that are assigned to themselves but not to the team. |
|
Same device cannot be assigned to Bot Creator and unattended Bot Runner for
triggers
After you update to this Enterprise A2019 version from an earlier version, a default device that is assigned to a Bot Creator or an attended Bot Runner cannot be assigned to an unattended Bot Runner for deploying triggers. Recommended action: Use separate devices or device credentials (auto-login) for a Bot Creator and an attended Bot Runner as deployments can overlap or override across licenses. |
|
Create a Request action URI
The process selector in the Create a Request action is replaced with a public repository uniform resource identifier (URI). |
| Fixed features | ||
|---|---|---|
| Build number | Service Cloud case ID | Description |
| 8134 | -- | The table element now renders properly even when the Row before scrolling parameter value does not match the number of rows. Previously, the table did not render properly and displayed empty cells. |
| 8122 | -- | When you check out a process, and add, modify, or remove tasks in the process editor, the dependencies are now correctly updated when the process is checked in. |
| 8098 | 00707684, 00707688, 00707192, 00706781, 00707900, 00709109 | All event triggers are now retained when you update to this version from an earlier version. |
| 8098 | -- | In the process editor, undo and redo functions are now available for both canvas and properties panel interactions by default. Previously, the undo and redo functions were only available for canvas interactions. |
| 8098 | -- | Previously during bot runtime, if you deleted all the existing rows from a table before adding a new row, the columns and rows of the table were misaligned. You can now drag and resize any column to reset the table alignment. |
| 8098 | -- | All the trigger events within a form are now retained and no longer fail when the form is closed and reopened during bot runtime. |
| 8098 | -- | In the process editor, if you replace the Go to option with an End process, the End process icon now displays the correct status (Completed, Failed, Canceled). Previously, the status was not displayed correctly and had to be changed manually by using the End process option. |
| 8098 | -- | 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. |
| 8098 | -- | When you filter your tasks in the Task tab, the results shown in the tab now retain the information when you navigate between different tabs. |
| Deprecated features |
|---|
|
Support removed for device pool
configuration
An Automation Co-Pilot administrator can no longer use the device pool configuration to deploy bots in a process. After upgrading to Enterprise A2019.19 from an earlier version, verify that the scheduler user configuration is set up in order to successfully execute your bots in the process. |
| Known limitations |
|---|
| When you create a request from a
process (public or private) and enter all the required
information in the initial form, the initial form cannot be
submitted because the Submit option does
not work. This issue occurs for all initial forms with at least
one mandatory field. Workaround: Make all fields optional. |
| When you submit an initial form or task in a request view that contains a check box with at least two options and at least one option is selected, the check box value is not changed and defaults to a false Boolean value. |
| If the Set action is used immediately after a Get action, the value assigned to a variable using the Get action is not retrieved in the specified form element of the Set action during bot runtime. |
| An Automation Co-Pilot
manager can create a request from a process that is assigned to
them but not to their team. They can create and complete the
request if the process contains only bot tasks.
If the process contains a human task, the manager cannot assign
the human task to themselves. Workaround: Assign the process to both the manager and their team. |
| In the process editor, the Go To option shows only the Human Task and Bot Task, it does not show the Filter Task or the Process Task. |
| (Service Cloud case ID: 00736309, 00765069, 00784362) If you use a file trigger for a document that is in .csv, .xlsx, or .xls format, the corresponding bot is not triggered when that document is modified. |
Discovery Bot
| New features |
|---|
|
View the
duration of each recorded
step
A recorded step is now displayed in minutes and seconds for the business user and analyst. Use this information to understand which steps are a bottleneck in the current process and will provide most benefit from automation. The step duration is displayed from the Recordings page (below the screenshot image), and from the View process and View opportunities page from the Preview pane window. |
| Changed features |
|---|
|
Enhancement to the screenshot
The screenshot image of the recorded step is now increased to full size for a more clear, detailed view of the recorded step. |
| Fixed features | |
|---|---|
| Service Cloud case ID | Description |
| -- | You can now click the Screen icon to display an image that you have hidden and saved. Previously, you had to click Screen and then click Save to display the image again. |
| -- | When an opportunity is created for a system-generated view with filters applied, the filter now persists across the view displayed in the Aggregated tab from the Opportunities page. The filter is not reapplied on the view from the Opportunities page and the No recording data message is no longer displayed. |
| -- | When you now cancel a recording, the recording is not displayed on the process tile in Process Cycle. |
| -- | You can now approve a recording with 2000 steps. The Recording status is displayed as approved. |
| Known limitations |
|---|
| Actions such as double-click, drag-drop, click and hold, and text select are not supported when you are recording a business process. |
IQ Bot
| New features |
|---|
|
Support for variables in IQ Bot
actions
(Service Cloud case ID:
00511178) IQ Bot On-Premises and Cloud You can now use variables in the Download all documents and Upload Document actions in the IQ Bot package. |
| Changed features |
|---|
|
Rename a learning instance (Service Cloud case ID:
00675803)
You can now rename a learning instance in staging in IQ Bot. |
|
Sequential document
processing (Service Cloud case ID: 00662968, 00665331)
When you click See Extraction Results, IQ Bot now opens that request in a new browser tab where its number in the queue is displayed. This number keeps decreasing as the previous requests in queue are processed. |
|
Dutch language support
IQ Bot now supports the Dutch language with ABBYY FineReader Engine. |
|
Configure OCR
settings using REST APIs
A user with AA IQ Bot Administrator role can now use the appConfigurations API to read and update the OCR settings. |
| Fixed features | |
|---|---|
| Service Cloud case ID | Description |
| 00639117 | Numeric format in the Polish language is now accepted in the IQ Bot Validator. |
| -- | When you upload a document immediately after deleting a bot it was associated with, extraction results are now displayed irrespective of when the bot was deleted. Previously, an interval of 3 minutes was required to view the extraction results of the deleted bot. |
| 00636899, 00683451 | When you create a learning instance using the custom domain, the field names now appear correctly, irrespective of the custom domain language. |
| 00459301, 00677204, 00532325, 00658245 | Custom Python logic now displays extraction results in the Designer without any errors. |
| 00657928, 00679540 | Exported IQ Bot archive (.iqba) files no longer contain any unclassified records in the .csv files. |
| 00704365 | If documents uploaded during production have fewer pages than the staging documents that the bot was trained with, these production documents are now processed without any errors. |
| 00703560, 0062442 | When you migrate learning instances using the append option, all records are now correctly migrated, irrespective of the number of records in the IQBA file. |
| 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. |
| 00686297 | IQ Bot machine learning services are now correctly installed when you install IQ Bot. |
| 00657928, 00679540, 00727633 | You can now migrate learning instances to production, even if they contain unclassified documents. |
| Known limitations |
|---|
|
IQ Bot
On-Premises and Cloud
If you click See Extraction results multiple times, the Learning instances listing page is opened instead of the extraction results. |
|
IQ Bot
On-Premises and Cloud
When creating a table on the Designer page, if you click See Extraction results without completing the table creation, extraction results are not displayed. Workaround: Create the table first and then click See Extraction results. |
|
IQ Bot
On-Premises and Cloud
An error message is displayed when you refresh the extraction results page for a learning instance when the associated bot is moved to production. |
|
IQ Bot
On-Premises and Cloud
When a bot is deleted, an incorrect error message is displayed when you click the Test bot option on the Bots listing page. |
|
IQ Bot
On-Premises and Cloud
If you rename a learning instance in production and download the files, all the files associated with the original learning instance are also downloaded. For example, if you rename a learning instance from Sales1 to Sales2, all the files associated with Sales1 are also downloaded when you download Sales2. |
|
IQ Bot
On-Premises and Cloud
If you have multiple learning instances and you click See Extraction results for all of them, the extraction results are not processed in the order of their request. |
|
IQ Bot
On-Premises and Cloud
When you create a learning instance with check box fields and run a Python script associated with the check box, an error message is displayed on the Designer page. |
|
IQ Bot
On-Premises and Cloud
When you upload staging or production documents to a learning instance, temporary files are created in the C:\Windows\Temp folder, and the folder size might increase over a period of time. Therefore, manually delete the files from this folder because it can cause IQ Bot to stop responding. |
|
IQ Bot
On-Premises and Cloud
If you select the
Only for me option when
installing the Bot Agent, the
IQ Bot Extraction
action has the following issues:
Workaround: During Bot Agent installation, choose the Anyone who uses this computer (all users) option. |
|
IQ Bot
On-Premises
(Service Cloud case: 00762174) Using the Database Migration Assistant to migrate from IQ Bot 11.x (five databases) to A2019 (unified database) in Microsoft Azure Database is not supported. |
|
IQ Bot
On-Premises and Cloud
When you change the display language of any learning instance that has a document in Validator, although the selected display language is successfully applied to the learning instance, an error message is still displayed. |
|
IQ Bot
Cloud
The auto-correction and auto-suggestion features, which are part of the MLScheduler service, use system resources extensively and cause the system to slow down or stop responding. |
| Deprecated features |
|---|
| IQ Bot On-Premises is no longer supported on Windows Server 2012. |
Bot Insight
| Fixed features | |
|---|---|
| Service Cloud case ID | Description |
| 00669196 | When you apply date filters on a dashboard and then apply an attribute filter in the widget, the system now filters by a specific date. Previously, the date filter applied at the dashboard level was ignored when the attribute filter was selected at the widget level. As a result, historical data was also displayed. |