I’m still pinching myself. My new book Mastering Salesforce CRM Administrationwas out yesterday (03/27/2017). Salesforce.com is one of the fastest-growing and demanding technologies at the moment. Mastering Salesforce CRM Administration is a hands-on guide that will help Salesforce newbies (who have a basic knowledge of Salesforce), new or experienced Salesforce administrators, and developers who want to take their knowledge to the next level to become a Salesforce certified advanced administrator. As you go through the content, you will notice that this book focuses on real-world examples. This book builds upon these examples to help you understand and use the features of the Salesforce.com platform.
This book is all about mastering the Salesforce admin part, taking your skills as an administrator or developer and tuning them for the unique features of the Salesforce platform. I have discussed many complex topics in this book, such as territory management,forecasting,quota,escalation rule,knowledge base,Visual Workflow, Process Builder, deployment using Force.com Migration Tool and more. This book covers almost all the topics mentioned in Salesforce certified advanced administrator examination study guide.
Here’s a taste of what you’ll uncover:
Adopt Lightning Experience to improve the productivity of your organization’s sales team
Create and maintain service entitlements and entitlement processes
Process Builder basic and advanced concepts
Implement Customizable Forecast and quota management
Implement Knowledge base management to improve support reps productivity
Implement territory management
Exploring different ways to deploy application between environments including Force.com Migration Tool
Best practices for improving and enriching data quality
And yes, so much more.
I would like to take this opportunity to thank both of you (Jitendra Zaa and Vinay Chaturvedi) for the effort and expertise that you have contributed to reviewing, without which it would have been impossible to maintain the high standards of the book.
Vinay Chaturvedi is a Salesforce MVP, currently working as a principal consultant. He has been loving and living Salesforce since 2011.
Jitendra Zaa is a Salesforce MVP, author, and a Dreamforce speaker with more than 9 years of experience in web technologies and cloud platforms.
How do you automatically create a record using Process Builder?
After reading this blog, you’ll be able to:
Understand the basic components of Process Builder
Learn how to auto-create a record using Process Builder
Business Use case
Corey Eridon is working as a System Administrator at Universal Containers (UC). He received a requirement to build a process that would automatically create a child case whenever a new case is created with the Case Reason – Breakdown.
Automation Champion Approach (I-do):
Because we need to create a new record, a workflow rule would not meet the needs of this requirement. Therefore, in order to automatically create a child case, Corey should use Process Builder.
Before we dive into the solution to help Corey, though, we need to first understand what is Process Builder and its components.
You can think of Process Builder as a happy medium between workflow rules and flow — it allows more automation than a workflow rule, without the advanced complexity of a flow — all with the ease of point-and-click.
However, unlike workflow rules, Process Builder allows more functionality, such as:
There are four basic components that should be considered when using Process Builder — a trigger, criteria, immediate action, and scheduled action.
Indicates when the action should fire – only when a record is created or anytime a record is created or edited
Set conditions to execute the process
The action is fired immediately
The action is fired at a scheduled time
To better understand Universal Containers’ requirements, let’s break down the use case by Process Builder component. This will help us conceptualize the process by defining each node and action first.
When a new Case is created
Case Reason – Breakdown is selected
create a Child Case.
Before diving further, 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 4 steps to solve Corey’s business requirement using Process Builder. We must:
Define process properties
Define evaluation criteria
Define process criteria
Add action – create a record
Step 1: Define Process Properties
In the Quick Find box, type Process Builder.
Select Process Builder, then click New.
Name the Process and click the Tab button. The API Name will populate.
As a best practice, always input a description.
The process starts when A record changes.
Step 2: Define Evaluation Criteria
Click on the Add Object node to begin selecting the evaluation criteria.
Select the Case object from the dropdown list.
Start the process only when a record is created.
Step 3: Define Process Criteria
Click the Add Criteria node to begin defining the process criteria.
Name the criteria.
The criteria should execute actions when the conditions are met.
Field: Case | Reason
Select All of the conditions are met (AND).
Step 4: Add Action – Create a Record
Below Immediate Actions, click Add Action.
For Action Type, select Create a Record.
Name the action.
Select the Case record type.
Set Field Values:
Click Add Row
Field: Case Origin
Click Add Row
Field: Parent Case ID
Type: Field Reference
Value: Case | ID
Almost there! Once everything looks good, click the Activate button. Moving forward, a child case will be automatically created whenever the Case Reason – Breakdown is selected.
Note:- Before you activate your process, you will want to make sure that you have assigned data in the correct format because Process Builder obeys validation rules. If some fields are required by using validation rules, then make sure you have added those fields. Conversely, if some fields are required on the page layout, you can ignore those fields.
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?