See Create a credential.

• Introduced role-based access to generate an API key for authentication. See Feature permissions for a role.
• The validity of the API key for authentication is controlled from the Control Room Settings page. See Configuration settings.
• Control Room users with appropriate permissions can generate the API key from their user profile page.

You can now ensure that when creating a credential in the Control Room, a password-type attribute can only be selected from a password field in the commands supporting Credential Vault variables, by selecting the This is a password attribute. This feature enhances the security of credential variables because the password-type attributes are not exposed and their values cannot be printed in a plain text application.

Using the Override default browser option in the Launch Website command, a bot developer can now choose the browser to use and override the default browser setting of the system.

The supported browsers are Google Chrome, Microsoft Internet Explorer, and Microsoft Edge. See Enterprise 11: Launch Website command.

The Flex plug-in is now installed in the approved Microsoft directory, that is, the Client installation folder instead of "C:\users\<username>\AutomationAnywhere\"

You can now clean up the Terminal Emulator log at specific intervals to optimize disk space. For example, if you set an interval of seven days, older log files are deleted during cleanup.

Valid interval ranges: 1 through 60 days Default: 7 days.

• You can now configure an Access Manager Reverse Proxy server, for example, the IBM WebSEAL, between the Automation Anywhere Enterprise Client and Control Room for secure communication.
• The client certificate authentication mechanism is used for the first-time authentication of Automation Anywhere Enterprise Client.

  See Enterprise 11: Configuring Access Manager Reverse Proxy.

The Remote Agent for Citrix enables you to use the Object Cloning command to capture objects from the applications that are installed on a Citrix environment, even when the Enterprise Client is installed outside the Citrix environment. See Object Cloning command.

Bot Insight is now available in the following 14 languages: Arabic, Chinese (Simplified), Chinese (Traditional), Dutch, English, French, German, Italian, Japanese, Korean, Polish, Portuguese (Brazil), Spanish (Latin America), and Turkish.

Bot Insight automatically detects your locale and if it finds a match, it translates all the UI elements to its appropriate language.

• Added Units as a measurement for ROI. You can now calculate the ROI based on the transactions processed by the bots.
  Note: If you are upgrading to Version 11.3.2, you must run the new analytic tasks and regenerate the CoE dashboard to reflect the new changes.
• Added a quick link on the Business Information section for consumers to view the published dashboards corresponding to a bot. This is very useful for analyzing the processed transactions.

• Bot Insight v2 APIs are now available for Control Room users. These APIs are backward-compatible. You can use the Bot Insight APIs to either push the data logged by Bot Insight to third-party applications, for example,Tableau, PowerBI, and so on, or use with bots to make them data-driven and add more power to the business rules.
• Added From and To Date to add more flexibility to retrieving data from the APIs.

1. Now complete a CAPTCHA text to log in to an Automation Anywhere Control Room instance after three incorrect attempts at answering the security questions. See Log on to Control Room hosted in non-Active Directory mode.
2. If you have manage settings permissions, you are allowed to modify the global security-related policy from the Control Room > Administration Settings > Email tab. See Configuring email notification settings.

When installing the Enterprise application, the installer now detects whether the system used for installation meets the minimum hardware requirements of CPU, RAM, and free hard disk space in addition to the minimum supported operating system. If any of the requirements are not met, the installer warns the user to be aware before continuing with the installation.

The separation of permissions enables a reduction in errors when validating many roles.