An overview of the building blocks of Visual Workflow
Flow has three major building blocks known as Element, Connector, and Resource. With the help of these blocks, you can easily develop Flows.

The Element
block represents an action that Flow can use to display or collect information from the Flow user, create or update records, delete records, or loop logic. The
Element
block
is used to manipulate the data. The Connector
block is used to establish the path between the elements. A Resource
block is used to hold the data that you can reference in your Flow.
Flow elements
Flow elements represent actions that Flow can execute such as Record
Update
, Record Lookup
, Fast Lookup
, Loop
, Screen
, and Decision
. This is used to read, write, or delete data. Using the element (Screen
), you can also display data and capture input from users. Use the Palette
tab to drag and drop new elements onto your canvas. Once you add elements, it will be available on the canvas and Explorer
tabs.
There are several types of elements available under the Palette
tab. They are as follows:
Flow element | Description |
| You can use this as a placeholder while designing your Flow. Later, you can convert |
| This will display a screen to the user who is running the Flow. The |
| This is used to evaluate conditions to determine which Flow path to take. |
| This is used to set or change values of variables, collection variables, SObject variables, and SObject collection variables. |
| This iterates through an SObject collection variable and assigns an item's value to an SObject variable. |
| If you want your Flow to wait for one or more defined events to occur, then use this element. |
| This is used to create one record using the field values that you specify separately. You can assign these values from Flow resources such as variables, SObject variable, and the screen fields. |
| This is used to update records using the field values that you specify separately. You can assign these values from Flow resources such as variables, SObject Variable, and the screen fields. |
| This is used to extract one record that meets the filter criteria you specify, and then assign the record's field values to separate, individual Flow variables or individual fields on SObject variables. |
| This is used to delete records from Salesforce that meet the filter criteria you specify in your Flow. |
| This is used to create records using the fields' value from an SObject collection variable or to create one record using the field's value from an SObject variable. |
| This is used to update records using the field's value from an SObject collection variable or to update one record using the field's value from an SObject variable. |
| This is used to extract records to assign their field values to an SObject collection variable or query one record to assign its field values to an SObject variable. |
| This is used to delete records using the ID value from an SObject collection variable or to delete one record by using the ID value from an SObject variable. |
| This is used to call an Apex class that implements the |
| This is used to invoke another Flow in the organization. |
| This calls an object-specific or global action, such as |
| This is used to send an e-mail using a Workflow e-mail alert to specify e-mail template and recipients. |
| Using this element, you can post a message to the feed for a specific record, user, or Chatter group. |
| This is used to send an e-mail using Flow with the specific subject, body, and recipients. |
| This is used to auto submit one record for approval. |
From Chapter 2, Creating Flow through Point and Click, we will start using these elements.
Flow resources
Resources are used to hold the data that you can refer in your Flow. The Explorer
tab displays the resources that you added to the Flow. To create new resources, double-click on this tab. Global constants and system variables are automatically provided by the system. There are several types of resources available under the Resource
tab. They are as follows:
Flow resource | Description |
| This is used to store a value that can be updated as the Flow is executed. It can be referenced throughout the Flow and can be used as the value of a field in a record. |
| These are system-provided variables that can be referenced as resources, such as an organization ID ( |
| This is used to store values with a single data type. You can use a collection variable as a container in the Flow to store and reference multiple values at once. |
| This is used to store a record for a specified object. Use an SObject variable as a container in the Flow to store, update, and reference field values for a record. |
| This is used to store multiple records for a specified object. Use an SObject collection variable as a container in the Flow to store, update, and reference field values for multiple records. |
| This is used to store a fixed value. |
| This is used to calculate a value from other resources in the Flow. |
| This is used to store formatted text with merge fields that refer to resources. |
| This represents an individual value that can be used in a variety of screen fields. |
| This looks up data from an object's record and dynamically generates a set of choices for screen fields at runtime. When referenced as a resource, a dynamic choice value is determined by the most recent user selection of a choice within the generated set. For example, display all contacts from an account if a user entered a valid account ID. |
| Any element that you add to the Flow is available as a resource with the visited operator in outcome criteria. An element is considered to be visited if the element has already been executed in the Flow interview. |
| This is used to store fixed system-provided values, such as |
| For the |
| These are system-provided values that are available as resources only in |
| This is used to store picklist or multi-select picklist values, those are generated from standard or custom object picklist or multi-select picklist field. |
| This is the field that you add to the Flow is available as a resource. |
| These are system-provided values that can be referenced as resources, such as |
|
|
From Chapter 2, Creating Flow through Point and Click, we will start using these resources.
Flow connectors
A connector is used to establish the path between the Flow elements. A connector looks like an arrow that points from one element to another. There are several types of connectors available. They are as follows:
Label | Sample | Description |
Unlabeled | ![]() | This is used to identify which element to execute next. |
Decision outcome name | ![]() | This is used to identify which element to execute when the criteria of a decision outcome are met. |
Wait event name | ![]() | This is used to identify which element to execute when an event that's defined in a wait element occurs. |
Fault | ![]() | This is used to identify which element to execute if the previous element results in an error. |
Next element | ![]() | This is used to identify the first element to execute for each iteration of a loop element. |
End of loop | ![]() | This is used to identify which element to execute after a loop element finishes iterating through a collection. |
From Chapter 2, Creating Flow through Point and Click, we will start using these connectors.