RPA Bots for Salesforce 3.4 Release Notes
Review the new and changed features in RPA Bots for Salesforce version 3.4.
Supported Automation Anywhere Enterprise versions
Supported for Automation 360 Cloud deployment and On-Premises.
The RPA Bots for Salesforce solution in the Automation Anywhere platform enables users to run bots for routine business processes from any Salesforce Cloud record page.
|Bot history in Chatter
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.
注： Chatter must be enabled within the Org and the Lightning component must be available in the page layout.
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.
注： If an Object is selected, you will not be able to select the Home or App pages.
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.
|Run Locally added to Run
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.
|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.
|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.
|Bot Directory improved
functioning on Mobile app
The Automation Launcher now has full functionality in the Mobile app and bots can be launched.