Vasim (OSI)
Vasim
Salesforce Flow is an automation tool that
allows you to build workflows, automate
repetitive business processes, and manage
data operations with clicks, not code.
Flows can be used to collect, update, delete,
or create records in Salesforce,
Flows provide a user-friendly interface for
creating complex business processes.
Vasim
Supports complex business logic, allowing for
more advanced scenarios like loops, decision
trees, and multiple record updates.
Flows can include user screens, enabling
interactive processes that gather input
directly from users, unlike Process Builder,
which operates in the background.
Efficient in handling bulk processing,
reducing the number of transactions and
improving performance.
Vasim
Screen Flows: Flows that include screens for user
input.
Auto-launched Flows: These flows run in the
background without user interaction. Triggered
when a record being created or updated, or called
from Apex, Process Builder, or another flow.
Scheduled Flows: These flows are set to run at
specific time or intervals.
Record-Triggered Flows: Triggered when record
changes occur (like creation, updates, or deletions).
Platform Event-Triggered Flows: Triggered when
platform events are published, allowing for real-
time processing when events are published in
Salesforce.
Vasim
Record-Triggered Flows: Initiated by creating,
updating, or deleting a record.
Auto-Launched Flows: Triggered by:
1. Process Builder: Called from a process.
2. Apex: Invoked from Apex code.
3. Custom Buttons/Links: Launched via custom buttons
or links.
Screen Flows: Started by users through Lightning pages
or quick actions.
Scheduled Flows: Run at defined times or intervals.
Platform Event-Triggered Flows: Triggered by platform
events in real-time.
Vasim
A screen element is used in a Screen Flow to
display fields, messages, or collect inputs
from users. It is the primary way to interact
with users in a flow.
Vasim
Vasim
A variable in Salesforce Flow is used to
store and manipulate data within a flow.
You can store data from fields, user inputs,
or system-generated values in variables.
Vasim
Fault handling in Salesforce Flow ensures
that the flow does not fail silently when an
error occurs.
You can add fault paths to handle
exceptions, such as by displaying an error
message or creating a record of the error.
Use “Fault Connectors” on flow elements to
define alternate paths when an element
fails.
Vasim
Use clear naming conventions: Label
elements and variables descriptively.
Avoid hardcoding IDs: Use variables for
flexibility across environments.
Add fault paths: Handle errors gracefully to
improve troubleshooting.
Limit data usage: Fetch only the records you
need for better performance.
Avoid DML in loops: Place data operations
outside loops to prevent errors.
Use sub-flows: Break complex Flows into
smaller, reusable sub-flows.
Vasim
A subflow is a flow that is invoked from
another flow.
It helps break down large, complex flows into
smaller, manageable pieces, improving
reusability and maintenance.
You can call a subflow using the “Subflow”
element in the Flow Builder.
Vasim
A Flow Interview is an instance of a Flow that
is running for a particular user or operation.
Each time a flow runs, a new Flow Interview is
created.
In the case of an error, the flow interview is
paused, and you can view and debug these
paused interviews.
Vasim
Copyright: OSI. Not to be used for distribution
“Decision” elements in Salesforce Flow are
used to handle branching logic.
By defining criteria, you can direct the flow
through different paths based on record data,
user input, or system conditions.
Multiple “Outcomes” can be added to a
decision, allowing for complex conditional
flows.
Vasim
Before Save: used to update fields on the
triggering record before it is saved to the
database, thus improving performance by
avoiding DML operations.
After Save: used when you need to perform
actions that depend on the record being
committed to the database, such as creating
related records, sending notifications, or
making updates to unrelated records.
Vasim
A collection variable is used to store a list of
records or values in Flow.
Useful when working with multiple records in
batch processing.
Vasim
You can integrate Salesforce Flow with
external systems using:
Platform Events: to send and receive
asynchronous data.
Apex Actions: to call Apex code that
integrates with external services.
External Services: using Flow’s declarative
approach to call REST-based APIs for
outbound integrations.
Vasim
