Have you heard that you can have “One stream for each object”, however, is this standard still pertinent? Over the long haul, the message has changed. There is seldom a clear response with regard to Salesforce flow configuration designs.
There are many variables to consider, all in regard to your association and business processes.
Salesforce changed its message when it became apparent that the exhortation could not be so obvious, all things considered, it needed to think about the broader customer picture. Besides the fact that customers need to move their Robotization, there are also new highlights and rules to follow while working with flow.
There is no doubt that Salesforce has considered this, resulting in relaxed information.
By the way, it is impractical to do only single object-triggered logging, you may have some activities that must be performed before the dataset is updated, and others that must be continued. Your registry can be run in one of two configurations, so you may need to do a before-and-after flow to meet your business needs.
On that equivalent note, a registration flow can be enabled under Create, Update, Create or Update, OR Delete. You can design it when flows should be executed in Create or Update, however, Delete should once again be handled independently.
The real magic number when building record-triggered by flows is three:
- Before creating or updating;
- After creating or updating;
- Before deleting.
The Right Number of Record-Triggered Flows Per Object
- Assuming you’re a more small association, and you can fit everything inside one stream for that thing, then, do attempt to fit everything for that object inside one flow.
- In the event that you’re starting in another association, start with no than three streams for each thing, a single before-update, an after-update, and a deleted* stream for each object.
It is not possible to have one flow for each item.
Based on the fact that it will probably require a prior upgrade, and after the upgrade, you have to delete the flow.
Adding More Flows Per Object
The situation starts to get complicated where organizations build a ridiculously large flow that is supposed to handle everything. Regression testing needs to be performed on the entire flow after every update, creating more technical debt.
Rebuilding Salesforce Automation into Flows
To build new flows or move other types of automation into the flow, you have to plan for the long term, rather than building flows that solve the requirement that exists right now but may not be able to accommodate future requirements.
It also depends on the history of your Salesforce organization, for example, If we are moving directly from workflow to flow, you will be further behind than organizations that have been using Process Builder or Apex.
Salesforce has recently performed some enhancements to the structure of flows, they have allowed admins and developers to set a lot more of the key properties from within the Start Element (the green element at the beginning of all flows, containing key information about the Flow and how it should begin).
So to have both a “preceding” creation or update and a “later” creation or update, you can’t deal with both inside a similar stream. You will likewise require a different stream to deal with erased records, yet recollect that erased streams are constantly run previously, with no choice to pursue. Flow Builder is designed so that each flow begins with a single trigger condition.
