Version 11.3.4.2 Release Notes

Review the new features, changed features, fixed features, security fixes, and known limitations in Version 11.3.4.2 for Automation Anywhere Control Room, Enterprise Client, and Bot Insight.

New features

Control Room
Support for LDAP required signing

The Control Room supports LDAP required signing in order to comply with an upcoming security release from Microsoft. LDAP signing provides enhanced security for network communications between an Active Directory and the Control Room.

LDAP required signing is not applicable to customers who use secure LDAP (LDAPS).

Configuring LDAP signing | Configuring LDAP schema

Changed features

Control Room
User who has created schedules cannot be deleted

An admin user cannot delete a user in the Control Room if the user has created schedules. A message appears listing the reasons why that user cannot be deleted.
Map up to 1000 Active Directory groups to roles

Service Cloud case ID: 00361617, 00372134

The Active Directory can now include 1000 groups. You can map 1000 Active Directory groups to user roles in the Control Room by defining the domain, organization unit, and prefix for groups of organization units in the um.properties file located in the installation path. Search for Active Directory groups that are defined in the um.properties file.

Note: Nested organization units are not supported.

Map up to 1000 Active Directory groups to roles

Warning message appears when consumer privileges are removed from the locker

Service Cloud case ID: 00462926

When users with consumer privileges are removed from the locker in the Control Room, a warning message now appears stating that removing the role will remove the consumer privilege to credentials as well any previously set user-defined values. Previously, removing the user deleted the user credentials from the locker without any warning.

Enterprise Client
Tasks run from local command line display proper entries in audit log

You can now view the audit log entries for tasks run from the command line. The Control Room audit log now displays the proper entries. Tasks executed from the Enterprise Client, local scheduler, triggers, Workbench, or command line for Bot Runners and Bot Creators are logged in the audit log with the action type displayed as Pause, Suspend, or Stop.
Configure timeout to unlock machine for Auto Login

Service Cloud case ID: 00345570

You can now configure a timeout period in the AA.Settings.xml configuration file that enables the machine to wait until Auto Login unlocks the machine. The default value is 60 seconds. You can increase or decrease the timeout value according to the time taken by the machine to unlock and successfully deploy the bot.

Configure timeout for Auto Login

Terminal Emulator commands retain parameter values while navigating between commands

The Terminal Emulator commands in the Workbench now retain their parameter values while navigating between commands. Previously, the commands were not retaining the values while navigating from one command to another.

Fixed features

Control Room
Zendesk ticket ID or Service Cloud Case ID Description
00437121 Login to the Control Room is no longer delayed if the logged-in user is assigned the locker role (Owner, Manager, and Participant), or queue (Owner or Participant). The system performance is no longer degraded.
00423045 The SourceIndex setting is now optional. Users can now log in to the Control Room without setting SourceIndex in the IdP when the Control Room is configured without single logout in SSO authentication.
378563 Regardless of the priority of a dual NIC configuration, the Apache Ignite server now points to the correct IP of the nodes and takes the value of ignite.local.static.ip defined in the cluster.properties file.
00377355 When the Control Room is down and a schedule should be triggered at the same time, the schedule no longer disappears and triggers properly when the Control Room is restarted. Based on the configuration in the schedule.misfire.time.in.minutes=15 property in the deployment.properties file, the triggered schedule will either be deployed or will generate a misfire audit.
Enterprise Client
Zendesk ticket ID or Service Cloud Case ID Description
00423588 When using the Search by Caption command, the Web Recorder now searches the first opened Internet Explorer window.
238114 The ABBYY OCR engine now releases resources after completing OCR operations in MetaBots. The OCR engine was previously not releasing resources when using OCR-based screens for the GetText operation in MetaBots.
-- When the Enterprise Client service is performing a refresh, other tasks are no longer delayed. Previously, when the Enterprise Client was busy with a refresh token task, the rest of the services were delayed.
00369774 The Enterprise Client task deployment is now optimized for a multi-user session environment (for example, terminal server and Citrix).
-- When Version control system (VCS) is enabled, after you upload a MetaBot and add a new Logic, or edit or save the existing Logic through the MetaBot Designer window, a warning message now appears. You are restricted from adding a new Logic, or editing or saving the existing Logic until you check out the uploaded MetaBot from the Control Room.
00380355 When you simultaneously use multiple instances of the Enterprise Client that are connected to the same Control Room to open a Logic through the MetaBot Designer window or run a task that contains a MetaBot command, you no longer intermittently see an error message.
00416871 When you use a bookmark level in the PDF integration Split command, the last page of the PDF file is no longer missed--all the pages in the PDF file are included.
00446132 In the Japanese AS400 system, the output of the Terminal Emulator > Get Text > All Lines action now displays all the lines in the TN5250 screen, even when the Japanese text is displayed.
Bot Insight
Zendesk ticket ID or Service Cloud Case ID Description
00416233, 00429767 The Control Room log settings are fixed at the Debug level. During the PostgreSQL Server to Microsoft SQL Server migration, memory consumption in the Control Room will not be saturated. Additionally, the Control Room will not run of space for storage.

Security fixes

Control Room
Zendesk ticket ID or Service Cloud Case ID Description
00434451 Tasks run using the command line for Attended and Unattended Bot Runners and Bot Creators are now logged in the audit log. The Control Room audit log displays the action type as Run Bot (Local Command-Line) for this task run.

Known limitations

Control Room When the Active Directory service account password for an Control Room user expires, changes, or is reset and the required signing option is enabled, users must enter their domain name as well as the fully qualified domain name (FQDN) along with the username in the format: domain\user1@domain.parentdomain.com

Users have to perform this activity only once, unless the password expires, changes, or is reset again.

Enterprise Client
  • The PDF integration Split command does not split the files if the PDF does not have any bookmarks. Due to this, execution of the Task Bots might stop.
  • In the Terminal Emulator, for the TN5250 Japanese DBCS model, the Get Text > Lines With Column Range option might not work properly as expected in the following cases:
    • When the input text contains Japanese DBCS characters, the Get Text > Lines With Column Range option does not display the output line by line for the defined column range and instead displays it in a single line.

      To display the output line by line, retrieve the data row by row and append the results using the String Operation or Variable Operation.

    • When the input text contains Japanese DBCS characters along with a single-byte character, the Get Text > Lines With Column Range option displays incorrect output.