Salesforce Flow

No admin should ever need to code! That was my early introduction when I initially caught wind of Salesforce Flow (Also called – Visual Flows, Visual Workflows). From that point forward in pretty much every necessity where customarily I would utilize Apex, Flows worked. Need to mass make/update/erase records dependent on the data that you need to get from absolutely disconnected records? Flow is the tool you need. Need to streamline your creation process without the need to code? Use Flow. The utilization cases for Flows are perpetual, but the ones we will cover are:

  • What are Flows?
  • What features does Flows include?
  • How Flows can be used.

What is Salesforce Flow?

Flow is a ground-breaking business mechanization apparatus that can control information in Salesforce in an assortment of ways. Such application can be created from the organization’s setup with simply drag-drop/point-click. The simplicity of making flows makes it the main go-to tool with regards to complex business requirements. It isn’t just simple to make, but it also doesn’t require any coding. Be careful! That does not mean you don’t have to understand the Salesforce platform’s object relationships and overall how Salesforce runs. You must have (at any rate) mid-level comprehension of SFDC and its highlights all together appropriately use flows.

To begin with, we are demonstrating how a flow is made and how it flows. Flows can be made from setup, enter Flows in the Quick Find box, at that point select Flows, and afterward click New Flow.

There are 3 main “building blocks” of flows:

  1. Elements represent actions that are executed in the flow;
  2. Connectors define which path the flow takes;
  3. Resources are the values that can be referenced anywhere in the flow.

We will talk about all these building blocks in more detail later.

What Features are included?

On the left side of the Flow Designer, we get 3 tabs: palette; resources; explorer.

Palette

Palette gives access to a number of elements that can be used to build the logic.  The main elements are as follows:

– User Interface element Screen – Users can interact with the Flow just through this component. It lets the flow gather data from the user and pass it to different components for processing.

– Logic Elements:

  • Decision – helps to determine the direction of the flow
  • Assignment – can set, change, add values of/to variables
  • Loop – iterates through the values of a collection variable
  • Wait – it becomes handy when the flow needs to wait for an event to occur and define exactly how the flow should behave in such event.

– DML operations:

  • Record Create/Update/Lookup/Delete – the names represent themselves. We can search for and delete records directly in here.
  • Fast Create/Update/Lookup/Delete – these are doing nearly indistinguishable things from components above yet by utilizing just subject factors. Utilizing fast components serves to bulk the exchange. For instance, on the off chance that there are 100 records that should be refreshed, at that point it is smarter to have Fast Update component to refresh 100 records without a moment’s delay, rather than having Record Update run multiple times, which builds API calls to the database.
  • At that point we have Flow components which list every one of the flows that we have in our organization. This puts flows inside one another.
  • Email Alerts – all email alerts that are being utilized in work process guidelines and procedure manufacturer in your organization are incorporated into this segment
  • Quick Actions – each and every quick action that has been made in your organization is accessible inside the flows
  • Toward the end we have Apex and Static Actions elements, in this piece of the story we can work with engineers to utilize Flows and Apex coding together to assemble some incredible applications.

Resources

Resources – these are utilized to gather, store, and pass the information inside or outside of the application. In view of the interest we can pick one of the assets beneath:

Variables – alterable assets that can be refreshed inside the flow, or from outside. Utilized for passing qualities all through the flow

– Collection variables – does the same trick as variables, except as many values within the same data type can be stored in this resource

Subject variables – alterable assets where we can store a record of a particular article type, when put away in subject variable every one of the fields of that record can be accessed to through a similar variable

Subject collection variables –stores various records of a predetermined object type, this asset can be utilized to fast delete, fast update, and fast create records

– Stage – resource that used to indicate the stage of the process/flow where the user is at

– Constant – fixed value, can be used throughout flow

– Formula – creates a value with the help of other resources in the flow

– Text template – Formatted text, html code can be used here

– Choice – individual choice option

– Dynamic-record choice – an incredible asset. Demonstrates a sifted rundown of Salesforce records to the user, and stores one record that the user picks

– Picklist choice – Salesforce picklist or multi-select picklist can be stored here for use in the flow;

Explorer

The Explorer is just a library that incorporates every one of the assets and components that are being utilized in the flow.

How are Flows run?

The greatness of the Flow does not finish there, another advantage is it very well may be kept running from all over the place. Be that as it may, to figure out where to run them we have to realize the flow types, there 2 principle sorts:

– Screen Flows – as the name recommends incorporates screen component to assemble data from a user, this implies the flow type requires a user cooperation. This kind of flow can be accessed in various spots: custom catch; custom link; direct URL, Visualforce Page, or Salesforce application.

– Autolaunched – keep running in the background with no need of user communication. Regardless it can run wherever that screen flows run, likewise, we can run it from procedure manufacturer and Apex. The official Visual Workflow Guide says Workflow activity is in pilot so it will be accessible for open use later on, and afterward we will almost certainly run auto launched flows even from workflow rules.

Conclusion

To summarize, flows incorporate a great deal of incredible highlights which would be helpful in each and every organization. This post is with the motivation behind acquainting you with Flows and to demonstrate what their capacities are.