Automation Anywhere for Salesforce 3.0 Release Notes

Review the new and changed features in Automation Anywhere for Salesforce version 3.0.

Supported Automation Anywhere Enterprise versions

Supported for Automation 360 Cloud deployment and On-Premises.

The Automation Anywhere for Salesforce solution in the Automation Anywhere platform enables users to run bots for routine business processes from any Salesforce Cloud record page.

New features
Maintain multiple Control Room connections

Multiple Control Room connections can now be created in the Automation Anywhere for Salesforce App. This feature enables you to maintain connections to multiple Control Room instances or as a way to enable multiple connections to the same Control Room. For example, when departmental access are required through dedicated logins for auditing and compliance.
Manage incoming data in Bot Configuration wizard

Users can map bot output variables to data fields of a specified Salesforce object. The field also enables the user to specify one of five operations to apply to the incoming data: None, Create, Update, Upsert, or Delete.

Create new bot configurations in Automation Anywhere for Salesforce

Quickly select a bot by using subfolders

The Bot Directory tree component simplifies selecting bots in the Bot Configuration wizard.
Improved parameters for bot configurations
  • A Run-as user is now a configurable parameter in the Bot Configuration wizard and enables you to select a Bot Runner to run the automation. Multiple run-as users can be selected from the list, which then enables the Control Room to send the request to the first available device.
  • Use the Number of Run As Users to Use value to indicate the number of run-as users that should be used from the list of run-as users provided. The system selects a specified number of run-as users with the least number of tasks queued for the run-as user at the time of the deployment request.
You can now select bots quickly with a real-time search feature that filters results in the bot search field as keywords are entered.
Changed features
Bot configuration supports additional data types
Numerous data types are now included for configuration in Automation Anywhere for Salesforce. When you select a variable of either input or output type from the bot, the Salesforce drop-down menu automatically filters by data type to match the variable.
  • The bot configuration input mappings now support the following Automation Anywhere variable types in addition to the string type in previous versions: number, Boolean, date/datetime, list, and dictionary.
    Note: You can use the list type only with multi-picklist Salesforce fields when using the mapping type of SF Field. If you use Input Field type to pass static values, you should specify the list values in the following format: VALUE;VALUE;VALUE.

    You can use dictionary type only with mapping type: Input Field. Specify dictionary values key-value pairs in the format KEY:VALUE,KEY:VALUE

  • The bot configuration output mappings now support the following Automation Anywhere variable types: number, Boolean, date/datetime, and list.
Updated features of Automation Launcher web component
  • The Automation Launcher only polls one time for the status of the bot run from the Control Room 5 seconds after the bot trigger action. After this interval, the user can refresh the entry for an updated status.
  • The Automation Launcher now displays details for the previous five executions, including detailed error messages, instead of only the most recent.
Authentication now allows use of both password and API key

Users can choose a preferred method when creating Control Room connections through the Automation Anywhere for Salesforce application.
Device pool is now an optional parameter.
Enhanced notifications

Notifications (through the Salesforce Customer Notification framework) are now provided after a bot completes running successfully, or if it fails. Notifications are also provided on completion of a callback operation, and when a bot is triggered to run from a Process Builder or Lightning Flow. Each notification is an active link and you use it to navigate to the corresponding record detail page.
Known limitations
Unable to connect to Control Room API

When you attempt to connect Salesforce apps to the Control Room API with an HTTPS connection, the following error might occur: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Due to Salesforce guidelines placed on trusted certificates, an authorized connection might require an intermediate certificate (certificate chain) that requires proper installation and configuration.

Workaround: Confirm the certificate issue by using an online SSL test.

When the confirmation is complete, follow these instructions to install the certificate and connect the Control Room API.
  1. Obtain a CA-signed certificate.
  2. Install the certificate and copy it into Notepad.

    Import HTTPS and CA certificates

  3. Find the pem file in the C:\Program Files\Automation Anywhere\Enterprise\pki directory.
  4. Open it with a new instance of Notepad and paste the intermediate certificate from step 3 above the Site Certificate.
  5. Save the pem file.
  6. Restart the Automation Anywhere Control Room Reverse Proxy service.