Salesforce Flow Best Practices : Salesforce Flow Design Patterns

Salesforce Flow Design Patterns from Fundamentals to Mastery. In this session we will talk about top 10 Salesforce Flow best practices. We will talk about how to Implement one Flow per object and build subflow(s) to enhance the original Flow’s scope.

[@apexhours]

Check more best practices here www.apexhours.com/salesforce-flow-best-practices/

[@xoeiie]

I have 1 question for 37:24
what if I want to get records, thenloop and update a status, and send email for each record?

[@kiranvrao9714]

Awesome session! I love the fact that he was able to give examples from his experience for every slide! Superb Thanks a lot

[@apexhours]

Glad you liked it!

[@djamburere]

18:30 - best tip for me today. I came to the conclusion but it's good to have it confirmed by an expert ❤

[@apexhours]

Glad you like it

[@anands8511]

great session once again!

[@apexhours]

Keep watching

[@ragulhm]

Thanks for the session ♥

[@apexhours]

Thank you too!

[@javedmanoor2126]

Awesome session!

[@apexhours]

Glad you enjoyed it

[@ragulhm]

Flows need lot more way to go compared to powerful trigger.
But it will definitely replace trigger one day.

[@apexhours]

I totally agree with you

[@jaredalwyn553]

Let's say we want to update a record that meets criteria when created or edited. If we have a node for new records and a separate node for after update we would have to either duplicate the update logic or put it into a subflow. We could also just have the criteria in the first decision, but that seems messier then what you have shown, especially if we also have records that only need to update on create. Do you have any recommendations or is duplicate logic something we just have to consider?

[@aslambagwan6032]

Thanks

[@piyushsinha1659]

Awesome :)

[@apexhours]

Thanks 😁

[@SalesforceUSA]

Good video

[@apexhours]

Thanks for the visit

[@sachinchavan-me]

If we don't use entry criteria and use decision element inside flow then it will create unwanted flow interview instance for the all records which we don't want to run the flow. Is my understanding right?

[@akashjadhav10]

yes

[@apexhours]

Enjoy

[@kiryuha721]

To replace SF Workflows' "Time-Dependent Workflow Actions" (e.g. send a task 4 hours after trigger date, send an email 90 days after trigger date) - we have to use Flows' Scheduled Path.
How does "Scheduled Path" fit into the framework proposed in this video?
The Handler flow is a Sub-flow, and cannot have Scheduled Path added to it.

[@supercooltechy]

recordtypeid was hardcoded in process builder for adding condition before action is fired. There was no option to select Recordtype Name instead of value.

[@ragulhm]

Just wanted to inform that subflows are not possible in before trigger, we might want to use trigger Metadata handler pattern.

[@apexhours]

Yes we covered that in our session

[@ragulhm]

@@apexhours yes, just telling an alternative way to use subflows

[@mohitk4683]

I haven't used it. But I know what are Custom Permissions & how to use

[@apexhours]

We will create one session soon

[@jaiaswani8039]

you cannot call a subflow on a record-triggered before save flow

[@user-gg1yw2zj5y]

Can any one post complete syllabus of admin , just topic names I need

[@AbhiRam-ii6rh]

Apps, Tabs, Objects, Fields and Relationship, Field dependencies, Page layout, Users, Permission sets, OWD, sharing rules, Roll-up Summary, Validation rules, Approval process, Advanced approvals and Automation tools(Flows, Process builder & Workflow),

[@user-gg1yw2zj5y]

@@AbhiRam-ii6rh thank you so much

[@apexhours]

Here is FREE Training and Agenda too

[@user-gg1yw2zj5y]

@@apexhours sir i need training on aura components

[@chethelesser]

Salesforce flow best practices: use Apex

[@apexhours]

:)

[@mjlewis86]

Why code when you don’t have to? That then makes the org unsupportable without code developers, which isn’t sustainable or scalable without significant financial investment. Pretty tone deaf response