Automation Anywhere for Salesforce 3.4 Release Notes

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

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
Bot history in Chatter feed
Bot activity is now recorded in the Chatter feed of each impacted record detail page. When a bot deploys, updates the record or attempts and fails, those details will appear in the Chatter feed for auditing purposes.
Note: Chatter must be enabled within the Org and the Lightning component must be available in the page layout.
Automation Launcher
In cases where bots do not rely on Objects it is more appropriate to deploy from a generic page, like the Home page. We have added an option to select Page Visibility, in the setup of Bot Configurations, for these scenarios. You can select all or one of the following options to attribute the bot configuration, making the bot visible and deployable from the selected pages.
  • Home Page
  • App Page
  • Record Page
Note: If an Object is selected, you will not be able to select the Home or App pages.
Visibility Filter

The Visibility Filter has been added to the Object Selection and Field Mapping section of Bot Configurations and offers admins a way to drive which bots are available to run on record detail pages. By setting conditions, automations are focused into relevant tasks in the Automation Launcher.

Visibility Filter in Automation Anywhere for Salesforce

Run Locally added to Run Options

For admins that want to supervise the process of a particular automation, they can now set their bot configuration to Run Locally on their device. This will use attended automation, requiring specific prerequisites to be met for success.

Prerequisites for Automation Anywhere for Salesforce

Changed Features
Updates to Home page
The appearance of the Home page has changed slightly to accommodate additional panels that include access to new features and helpful information.
  • Tile to new Monitoring Dashboard feature

    Quickly access the Monitoring Dashboard through the Home page for analytics and trends of bot deployment.

  • Essential information panel

    The Home page now presents a snapshot of License and bot details. The number of bot configurations allowed under your license and average of bots run in the current month are detailed in this panel.

  • Upgrade to Premium Link

    For users who would like to upgrade the number of bot configurations available for use, this link is available for an easy way to contact sales.

Bot mapping no longer requires Object selection

Previously, the bot required an Object to run on. To enable the use of more general bots (ex. Emailing reports), there is no longer Object dependency. During the Object Selection and Field Mapping section of the Bot Configuration wizard, you can choose None for the Object and use the new Visibility Filter feature to assign the page the bot will run from.

Custom Objects can be mapped during Bot configurations

Another change to the Object Selection and Field Mapping section is that bot configurations can now map inputs and outputs to Custom Salesforce Objects. Previously, mapping was restricted to Standard Salesforce Objects. During mapping selection steps, Custom and Standard Objects are visibly listed in the drop-down menus for data to be retrieved from or updated to the Object by the assigned bot.

Fixed Features
Bot Directory improved
  • Previously, some bots were not accessible in the bot directory of bot configuration due to truncation of Control Room folders. Now users have access to all bots. However, to access bots in subfolders users must first select the folder from the bot directory to access a specific bot stored within. The global search function no longer exists.
  • Previously, some system folders could be accessed in the bot directory, although they served no purpose in bot configuration. This clutter has been hidden to present only relevant options.
Automation Launcherfully functioning on Mobile app

The Automation Launcher now has full functionality in the Mobile app and bots can be launched.