Learning Salesforce Visual Workflow and Process Builder

By : Gupta

5 (2)

Buy this Book

Learning Salesforce Visual Workflow and Process Builder

5 (2)

By: Gupta

Buy this Book

Overview of this book

Salesforce Management System is an information system used in CRM to automate the business processes like sales and marketing. To implement this, Force.com developed a powerful tool called Visual Workflow to automate business processes by creating applications also called Flows. Learning Salesforce Visual Workflow, Second Edition is a practical guide on Flows that will enable you to develop custom applications in Salesforce with minimized code usage. The book starts with an introduction to Visual Workflows that teaches all the building blocks of creating Flows and use it efficiently. You will learn how to easily automate business processes and tackle complex business scenarios using Flows. The book explains the working of the Process Builder so you can create reusable processes. The book also covers how you can integrate existing or newly created Flows with the Salesforce Lightening Experience. By the end of the book, you will get a clear understanding on how to use Flows and Process Builder in your organization to optimize code usage.

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

Getting Started with Visual Workflow

Business problems

The benefits of Visual Workflow

System requirements for using Visual Workflow

An overview of the Visual Workflow lifecycle

An overview of the Cloud Flow Designer

An overview of the building blocks of Visual Workflow

The various ways to invoke a Flow

Visual Workflow outcome behavior

Creating an Admin playground account

Summary

Creating Flow through Point and Click

Creating the building blocks of Flow

Allowing users to pause Flows

Designing the Flow

A few points to remember

Exercises

Summary

Manipulating Records in Visual Workflow

Creating the building blocks of a Flow

Creating a constant

Creating a Text Template

Manipulating the data

A few points to remember

Exercises

Summary

Debugging and New Ways to Call a Flow

Debugging your Flow

Debug log

Who can run the Flow and how

Automating your business process

A few points to remember

Exercises

Summary

Developing Applications with Process Builder

An overview of Process Builder

Differences between Process Builder and other tools

Creating applications with Process Builder

A few points to remember

Exercises

Summary

Building Efficient and Performance Optimized Processes

An overview of process management

Hands on 2 - using custom labels in Process Builder

Hands on 4 - calling an Apex class from Process Builder

Hands on 5 - bypass processes using Custom Permission

Hands on 7 - scheduling multiple groups of actions

Hands on 8 - executing multiple criteria of a process

Hands on 9 - creating reusable processes using invocable process

A few points to remember

Exercises

Summary

Building Applications without Code

Distributing or deploying Flows and Processes

Hands on 2 - displaying messages after login

Hands on 4 - understanding Subflow and the Wait element

Hands on 6 - using custom metadata types in a Flow

Hands on 7 - creating scheduled jobs using a Flow

A few points to remember

Exercises

Summary

Enabling Flows to Work with Lightning Experience

Lightning runtime experience for Flows

Hands on 4 - embedding a Flow into a Lightning Record Page

Hands on 6 - displaying a two-column Flow through a custom button

A few points to remember

Exercises

Summary

Customer Reviews

5 (2)

5 star

100%

4 star

3 star

2 star

1 star

A few points to remember

The following are some noteworthy points regarding Process Builder:

A Process's API name must be less than, or equal to, 77 characters, and it's always associated with a single object.
Using Process Builder, you can't delete records. If you want to do that, you have to use Flow with Process Builder.
To set Text data field to blank, you can use {!$GlobalConstant.EmptyString}.
The Process owner will receive an e-mail from Salesforce. If the Process failed at runtime or if any fault occurs, the error or warning messages might refer to a Flow instead of a Process.
The process follows all the governor limits that apply to Apex.
You can have a maximum of 50 active rules and processes on any object. Rules include Workflow Rules, Escalation Rules, Assignment Rules, and Auto-assignment Rules.
Process actions are executed in the same order in which they appear in the Process Builder...