Big Idea or Enduring Question:

How do you set automation to auto-convert marketing qualified leads?

When there is a chance of further negotiations with a lead, it can be converted into an account, contact, optionally an opportunity. In short, once the lead status has reached a certain stage, it can be qualified as a potential. On conversion, all the lead details are transferred in creating an account, contact, and optionally an opportunity. The lead conversion process is a manual process, if you want to automate it then you have to use Apex code. This article will help you to understand how to automate the lead conversion process using the Lightning Flow.

Objectives:

After reading this blog post, the reader will be able to:

Use After-save Record-Triggered Flow to auto-convert marketing qualified leads
Understand @InvocableMethod Annotation
Use Schedule-Triggered Flow to call an Apex method

Business Use Case

Pamela Kline is working as a System administrator in Universal Container. She has received a requirement from the management to auto-convert marketing qualified (i.e. leads with Rating = Hot) leads and create an account and contact record.

Automation Champion Approach (I-do):

While this can be solved using various automation tools like Apex or Process Builder and Apex, we will use After-save Record-Triggered Flow and call an Apex method. To call an Apex method, add the Call Action element to your flow and select an Apex class with a @InvocableMethod Annotation. It means they allow us to extend the Lightning Flow by writing Apex code that meets certain criteria and then invoking the Apex from our Flows. If the class contains one or more invocable variables, manually enter values or reference field values from a related record. @InvocableMethod Annotation supports bulk operations. Let’s begin the solution for the business use case.

In this article, we will use the call LeadConvert database class from Apex code. Make sure to review it.

Before discussing it, let me show you a diagram of a Process Flow at a high level. Please spend a few minutes to go through the following Flow diagram and understand it.

Let’s begin building this automation process.

Guided Practice (We-do):

There are 2 steps to solve Pamela’s business requirement using Lightning Flow. We must:

Create an Apex class and test class
Lightning Flow Steps:
1. Define flow properties for record-triggered flow
2. Adding an action to Call an Apex Class

Step 1: Create an Apex class and Test class

Click Setup.
In the Quick Find box, type Apex Classes.
Clicks on the New button.
Copy code from GitHub and paste it into your Apex Class.
Click Save.

Repeat the above steps and click the Test class. You can get the code from my GitHub repo.

Step 2.1: Lightning Flow – Define Flow Properties

Click Setup.
In the Quick Find box, type Flows.
Select Flows then click on the New Flows.
Select the Record-Triggered Flow option and click on Next and configure the flow as follows:
1. How do you want to start building: Freeform
2. Trigger the Flow When: A record is created or Updated
3. Run Flow: After the record is saved
4. Object: Lead
Select All Conditions Are Met (AND).
Set Conditions
1. Row 1
  1. Field: Lead | Rating
  2. Operator: Equals
  3. Value: Hot
Choose the Option to Only when a record is updated to meet the condition requirements.
Click Done.

Step 2.2: Lightning Flow – Call an Apex Class

The next step is to call the AutoConvertLeads class from flow so that when flow fires it auto-convert the leads.

Under Toolbox, select Element.
Drag-and-drop Action element onto the Flow designer.
In the Action box, type AutoConvertLeads.
Clicks on the AutoConvertLeads apex class.
Enter a name in the Label field; the API Name will auto-populate.
Set Input Values:
1. Row 1:
  1. LeadIs: {!$Record.Id}
Click Done.

In the end, Steven’s Flow will look like the following screenshot: Once everything looks good, perform the below steps:

Click Save.
Enter Flow Label the API Name will auto-populate.
Click Show Advanced.
Type: Record-Triggered Flow
API Version for Running the Flow: 50
Interview Label: Auto Convert Leads {!$Flow.CurrentDateTime}
Click Save.

Almost there! Once everything looks good, click the Activate button.

Proof of Concept

Now onwards, if a business user updates the Lead Rating to Hot, Lightning Flow will automatically convert such leads and create an account as well as a contact.

Currently, the lead Gaurav Pradhan is Open and the Rating is Warm as shown in the following screenshot:
Now we update the Rating to Hot and see the flow magic.
Flow auto converts the Lead and create an Account and Contact or it.

Note: – I will suggest you implement this first in your developer org, test it and then move it to production. The same approach will work for the case assignment rule. Download Apex and Test class from GitHub.

Process Builder Approach

Formative Assessment:

I want to hear from you!

What is one thing you learned from this post? How do you envision applying this new knowledge in the real world?

Let me know by Tweeting me at @automationchamp, or find me on LinkedIn.

I am looking for a way to automatically delete an installed package members whenI inactivate their User account. Currently, I have to delete the User; then delete them from the installed package. Is there a way via PB and/or Flow? I'd like an automated deletion process that captures all associations. Thank you, Erin Ryan

Business Use Case

Martin Jones is working as a System Administrator at Gurukul on Cloud (GoC). At GoC they are using Conga Composer to streamline and scale their document generation process and Resco to use true offline mobile capability for their Sales and Field Service reps. Martin received a requirement from the management to auto remove managed package licenses as soon as a user’s account is deactivated.

Solution for the above business requirement

Before we proceed, let us first ponder – why do we need to automate this process in the first place?

On AppExchange, App providers use managed package, partly, to hide the code and implementation logic from customers. Another benefit of a managed package is that app providers can easily push updates to their customers’ org in one stroke.

When a user’s account is deactivated is Salesforce, his/her Salesforce license is released and available for reassignment. Such is not the case vis-a-vis the deactivated user’s managed package license. For despite being deactivated, a user’s managed package license is not automatically removed from his/her account; the System Administrator has to manually remove the managed package license from the deactivated user’s account.

There are a few possible solutions for the above business scenario, but we’ll use Flow and Process Builder to solve the above business requirement. Before trying to understand the technical aspect of the solution, let us spend some time to understand the general flow of our solution at a very high level. Please spend few minutes to go through the following flow diagram and understand it.

Automation Champion

Tag: Process Builder rakesh

Getting Started with Salesforce Flow – Part 44 (Auto Convert Marketing Qualified Leads)

Posted at 9:13 PM by Rakesh Gupta, on December 1, 2020

Big Idea or Enduring Question:

Objectives:

Business Use Case

Automation Champion Approach (I-do):

Guided Practice (We-do):

Step 1: Create an Apex class and Test class

Step 2.1: Lightning Flow – Define Flow Properties

Step 2.2: Lightning Flow – Call an Apex Class

Proof of Concept

Process Builder Approach

Formative Assessment:

Getting Started with Process Builder – Part 79 (Auto Remove Managed Package License from a Deactivated User!)

Posted at 10:20 AM by Rakesh Gupta, on November 21, 2017

Business Use Case

Solution for the above business requirement

Search

Upcoming Trainings

Sponsor #1

Sponsor #2

Sponsor #3

Sponsor #4

Order Now!

Buy My Book

Buy My Book

Recent Posts

Salesforce ID Converter Build on Lightning Flow

Blog Archives

Categories

Information

Top Posts

Social Media