In parts I and II of our Salesforce Connector series of tutorials, we set up our Salesforce Dev environment, installed and configured the Automation 360 connector, and did a quick smoke test to ensure that the connection from Salesforce to our Automation 360 Control Room was working. With all of that setup out of the way, we're going to jump into building out a full bot that's able to be triggered from the Salesforce UI, perform a data lookup on a case, then update the Salesforce object properties with the data the bot gathered. If you didn't get a chance to check out part 1 or 2 yet, be sure to check it out so you can learn how to set up your Salesforce Dev environment (free) and install the Automation 360 connector (part 1) and configure the connector to interface with your Automation 360 Control Room (part 2).
Setting Up and Using the Salesforce Connector Part III
The Automation Anywhere RPA Bots for Salesforce app that's available on Salesforce's AppExchange enables organizations to tightly integrate their Salesforce environment with the Automation 360 platform. This integration enables Salesforce users to trigger bots directly from the Salesforce interface (or via flows) that can run on attended or unattended Automation 360 bot runners. The Salesforce users triggering bots don't have to have Automation Anywhere Control Room accounts, nor do they need to know anything about configuring a bot runner. Best of all, object attributes from Salesforce can be mapped to input variables of the executing bot, and variables marked as output values can be mapped back to Salesforce to automatically update/create/delete Salesforce objects.
This tutorial is part 3 of our 3-part Salesforce Connector tutorial series. This part of the series will focus exclusively on creating a bot that can do some data lookup for the purposes of updating a Case object in Salesforce. It does make use of the setup that was done in parts 1 and 2 of the tutorial series, so if you haven't had a chance to follow along with those yet, be sure to check them out.
Our Use Case
Many times organizations that use Salesforce ultimately have data that may be helpful to a Salesforce Object (Case, Lead, Employee, etc), but that ultimately exists in another system. In this scenario, we're going to build a bot that can be used to:
- Receive Case details for a work order
- Perform a lookup of the Case Number in a fictitious Field-Ops Ticket Management application
- Extract Case Details from the Field-Ops Ticket Management application
- Update Salesforce with details from the Field-Opps app on the Salesforce Object that was originally used for triggering.
You'll be using the Salesforce Development Environment that was set up in part 1 of our tutorial series, so nothing new is needed there.
To follow along with Micah in building a bot to read from the Field-Ops Ticket Management Application, use the following login detail:
The Automation Anywhere Salesforce App enables organizations to quickly scale the consumption and use of RPA bots through seamless integration with Salesforce. This tutorial focused on the creation of an Automation 360 bot and the Bot Configuration Wizard of the RPA Bots for Salesforce connector to demonstrate how organizations can easily create automations that can be invoked directly from the Salesforce UI without a Salesforce end-user needing to use/see the Automation Anywhere Control Room at all. Consider how your organization may use the RPA Bots for Salesforce connector to add RPA capabilities to your Salesforce environment and to enable connections between applications that may previously not had any methods of connecting with Salesforce.
Bonus Tip: Looking to do a bit more with Salesforce from a bot? Check out our tutorial on the Bot Store Salesforce Package to see how bots and connect to and interact with Salesforce directly - which could be used separately from the Salesforce Connector (meaning there is no dependency) or in conjunction with the Salesforce Connector.