3 New Salesforce Flow Features to Shout About in Summer ‘20

Share this article...

Flow Designer was replaced by the new Flow Builder back in Spring ‘19. It was a welcome upgrade for those who were used to building in any of the new Lightning Builder tools (Process Builder, Lightning App Builder, even the Community Builder) and felt quite familiar from the moment it launched. With its simplified toolset and cleaner UI, it had laid the foundations of what would become the most powerful declarative automation tool that Sales Cloud had to offer.

Every time the Salesforce release notes are published, I get straight to reading them because I know that there will be new features for Salesforce Flows – the Summer ’20 release, of course, has new improvements that I want to shout about!

1. Before/After Handling in Flow Triggers (‘Record Changed’ Flow)

We recently saw Flows inherit an ability from Apex: the ability to act as a Trigger. You could select criteria which a Flow would be called automatically, and handle data.

With Summer ’20, we’re seeing yet another step in Flow becoming a fully-fledged declarative alternative to Apex: the ability to handle before and after events. This is a huge step for Flow and will grant even more power to declarative users.

Instead of being an Auto-Launched Flow, this will now be known as a ‘Record Changed’ Flow (one of a number of new Flow Types).

2. Flow Loop Variables are Automatically Created

This is a huge personal peeve of mine! In every iteration of Flow Builder and Designer to date, we’ve had to create our loops, then create a separate loop variable resource. It’s just an extra step that felt so unnecessary.

Salesforce has addressed this by creating this resource automatically when you create a loop. Let’s say you had a loop called ‘lead_loop’, Flow Builder will automatically create a resource called ‘Current Item from lead_loop’. The result? It will save you a ton of time, and make it much easier for new Flow users to learn how to use the tool.

3. Rollback Mode in Flow Debugger

With rollback mode enabled in your Flow Debugger, any changes that are executed by your Flow won’t be saved while you test it. This helps to keep your data clean and tidy while you create and test your Flows. This is one of those tiny changes that will have a huge impact.

Simply check the box on the first screen of the debugger to enable it, and your database will remain 100% intact.


There you have it! Those are the new Flow features that wanted to let the world know about!

3 thoughts on “3 New Salesforce Flow Features to Shout About in Summer ‘20

  1. LOL Why would point 2 “save you a ton of time”? It will save you at most the 30 seconds (tops) it took to put a name in the loop variable name box and will likely cost you a lot of inconvenience when you actually use that variable in other steps, looking for a really long variable name that you didn’t create. This is particularly annoying if your flow has multiple loops and you’re using things like templates to handle display screens later on. The worst part about it is that Salesforce didn’t bother to make it backward compatible, so if, heaven forbid, you have to edit a loop that was created in an earlier release, it will kill your variable and force you to go change every reference elsewhere in your flow. Oh, and if you made that change in an org with the Summer ’20 release and have to deploy it to a Spring ’20 org, guess what? You can’t! Unless, that is, you go into the xml and change everything back to the way it was without being able to actually see what you’re doing, which, let me tell you, is *extremely* stressful and unpleasant.

  2. Hi Pavan, you’re very right! It looks more and more like Salesforce are moving towards a world where Flows are the all-powerful declarative tool that does everything. Time will tell!

Add Comment