Flows in Salesforce

Learn All About Flows in Salesforce and Its Powers

What is a Flow in Salesforce? 

In Salesforce, a flow is an application that computes complex business measures. Basically, it gathers information and afterwards accomplishes something with that information. 

Flow Builder is the decisive interface used to construct individual Flows. Flow Builder can be utilized to construct code-like rationale without utilizing a programming language

Flow fall into five classes: 

1- Screen Flows: 

These are flows that have a UI component and require input from clients. These sorts of flows are either dispatched as an activity or inserted as a component on a Lightning page

2- Timetable Triggered Flows: 

These autolaunched Flows dispatch at a predefined time and recurrence for each record in a bunch, and they run behind the scenes. 

3- Autolaunched Flows: 

Run mechanized errands with this Flows type. Autolaunched Flows can be conjured from measure manufacturer, from inside an Apex class, from a set timetable, from record changes, or from stage occasions. 

dont miss out iconDon't forget to check out: Common Salesforce Flow Errors and How to Solve Them

4- Record-Triggered Flows: 

These autolaunched Flows run behind the scenes when a record is made, refreshed, or erased. 

5- Stage Event-Triggered Flows: 

At the point when a stage occasion message is gotten, these autolaunched Flows run behind the scenes.

When/for What Reason Would it be Advisable for Me to Utilize Flows? 

To respond to this inquiry, we truly need to investigate what robotization is required. As a rule, the sort of mechanization to use for a particular cycle is controlled by assessing where the information for the cycles starts from and where it needs to go. Consider whether what you need to achieve is best-taken care of by a Flows, work process field update, or an interaction. 

Flows can make, alter, and erase any record passed into the Flows. Records don't need to be connected to pass information in a Flow. Flows can likewise be planned to run on a set stretch with an assortment of records. 

The work process field update can set up information to the very account that summoned the work process rule, or to the expert record of an expert detail relationship on the record that conjured the standard. Work process rules can't make, alter, or erase records. 

Cycles, made in the Process Builder, can set up information to the very account that conjured the interaction, or to records related by one or the other query or expert detail connections. Cycles can likewise make records, however, they can't erase them. 

dont miss out iconCheck out another amazing blog by Rajesh here: Auditing Salesforce Org - Salesforce Security Guide

When Would it be Advisable for Me to Not Utilize Flows? 

By and large, you ought not to utilize a Flows in the accompanying circumstances: 

You're managing basic fields, email cautions, or record refreshes that can be better dealt with utilizing an interaction or a work process rule. By and large, Flows are utilized for more convoluted rationale, like what you may discover in Apex code, that can be refined in a definitive way. For instance, assuming you need a chance stage to be set to New whenever the chance is made, and you likewise need an email alarm to be shipped off to a project supervisor, you should utilize a work process rule or a cycle. 

There is a convoluted rationale included that is better made do with Apex code. An illustration of this is the Flows displayed in the Overview area. The rationale in this Flows is convoluted to the point that it makes investigating an aggravation, in addition to it makes archiving and dealing with the Flows troublesome. 

You need basic record creation. For instance, on the off chance that you might want to make a request whenever a chance is moved to Closed Won, it is smarter to utilize the Process Builder to finish this activity, as cycles are simpler to set up and oversee. 

Your Salesforce release restricts the number of Flows you can make. Basics and Professional versions have a constraint of five cycles (per measure type) and Flows (per Flows type) in every association. For most rationale in these releases, it is simpler to utilize a cycle.

Responses

Popular Salesforce Blogs