Webinar: How to deploy Flows like a pro

Flows are an incredibly powerful type of metadata but they can also be a pain to deploy, causing bottlenecks, headaches on release day, and end-user frustration.

Join Ben McCarthy (Founder, Salesforce Ben) and Tom Smith (Product Manager, Gearset) to hear about common Flow deployment pains, best practices to avoid them, as well as a sneak peak at Gearset's Flow Navigator.

Learn more:

Chapters:
00:00 Introduction
02:09 What are Flows?
07:00 Don't work on the same Flows simultaneously
12:29 Check Flow differences before deploying
19:09 Automatically deploy Flows as active
21:38 Summary: best practices for deploying Flows
22:59 Gearset's Flow Navigator
29:29 Deploying Flows with Gearset
30:21 Questions

[joelemmer]

Thank you for this excellent video. One thing that does confuse me with the development process that you specified with Flows, where the Flows are *draft* until they are deployed to production, is that if the Flows are draft then the logic they contain won't be run by pre-deployment unit tests, which is surely very dangerous. If you had some unit tests that checked the state of an Account record after an account record is changed (because, say, you had some Apex Trigger logic) and you added additional on-Account-change logic via a record-triggered Flow then we want to be sure that we still get the expected Account end state, even with the additional Flow logic. But if the Flow is draft until after it is deployed to production, this surely won't be the case.