10 New Salesforce Flow Features to Shout About in Winter ’21

Share this article...

Every time the Salesforce release notes are published, I get straight to reading them because I know that there will be updates to Salesforce Flows.

The Winter ’21 release has new improvements – and plenty of them to shout about! Here is the summary of all that’s coming to Flows.

1. Flows Can Handle Deletions

I said this in my Winter ‘21 Treasure Hunt post, and it held the top spot there too – there’s a reason for that! The ability to handle deleted records is an ability held solely by programmatic developers…until now. Admins and click-to-code developers now have the power to handle functions triggered by a record deletion. I genuinely can’t put into words how excited I am by this!

One thing to note, you can’t run an ‘After Delete’ Flow, only ‘Before Delete’. This is different to Create or Edit Flows.

See the Release Notes.

2. Debug Flows as Other Users

Wooooww this is going to speed testing up a bit! Building a Flow is always so much un, but having to test it for every other pesky user in your org is a nightmare! I’m joking, of course, without our users there’d be no need for the rest of us – but this feature will definitely make the process of building new features for our beloved users.

3. Debug Autolaunched Flows from Canvas

No more opening a second tab just to see where you went wrong! Now you can debug an Autolaunched Flow and watch the path as it is tested (remind anyone of Pardot Engagement Studio?)

The best part – you never have to leave the Canvas! Simply click ‘Debug on Canvas (Beta)’ to debug inside your current tab, then click ‘Edit Flow’ when you’re done to resume editing. Simples!

See the Release Notes.

4. Auto-Layout… Enough Said!

This one doesn’t need a lengthy title – we all know what’s coming! I know a former colleague of mine, Troy, will be over the moon with this one (he HATES when the lines aren’t straight between two Flow elements). No more messy Flow Canvases, no more zooming out and selecting a chunk of your Flow and shifting it aaaalllll over just to fit in another Assign element, AND NO MORE WONKY LINES! NO MORE!

Flow now sports Auto-Layout functionality that allows you neatly slip new elements in where they belong. A very highly anticipated feature – thank you, Salesforce!

See the Release Notes.

5. Custom Condition Logic (AND/OR)

Now you’ll be able to specify custom entry criteria:

See the Release Notes.

6. Access Related Record Data

Now you can access related records through a drill-down rather than having to use a ‘Get Records’ element. This saves time for you when you’re building, it keeps the canvas cleaner, and overall creates a better experience when trying to maintain or update the Flow in the future.

See the Release Notes.

7. ALL The Global Variables!

Global actions are now available throughout Flows, not just in Formula variables! Another minor tweak with a BIG impact! The example in the screenshot shows a User’s Last Name is the default value for the Last Name field in a screen flow. Thanks again, Salesforce!

See the Release Notes.

8. Multiple Object Screen Components (Developers)

This is a neat one for Devs – when building out new Lightning Components for Screen Flows, you’re now able to use the sObject and sObject[] data types, meaning you don’t need to replicate your component for each object you want to use it for. This should save time during development, and make it MUCH simpler to maintain your Components.

See the Release Notes.

9. Configuration Panel for Custom Flow Components now Generally Available (Developers)

This one was previously in beta but is now generally available – developers can now create custom configuration components that allow for easier setting of variables on a screen component.

The screenshot below shows an example of a slider as opposed to a number input field.

See the Release Notes. Image from the Developer Guides.

10. See Triggers for Flows

I’ve left this one for last on purpose. At a glance, you can now see what triggers a Flow. My screenshot below shows that I’ve created a Flow called ‘Opportunity Trigger’ that runs before a record is saved. At a glance, this seems like one of those minor things that’s “pretty cool”, and taken for granted… but, and I’ve raised this debate before, is this one more nail in Process Builder’s coffin?

I know standard practice for myself and many other Salesforce professionals in the past was to create a Process for each Object and perform various actions off of that (email alerts, hand off to a Flow or Apex, etc.).

Looking at the changes Salesforce is making with Flows, I begin to wonder if we’re closer to a 100% Flow powered Salesforce org than we think (in a declarative sense). I’d LOVE to hear your responses to this idea – there’s a comments section at the bottom of this article. Let me know what you think!

See the Release Notes.

Honourable Mentions

Here are a few I’m SUPER excited for, but I had a chance to really get my hands on yet. Now, you can add a new Section component and build a multi-column layout to your screens (pilot). You’ll also be able to trace Flow errors much easier with links in error messages, as opposed to having to search through your Flow to debug it manually.


There you have it! Those are my favourite features that have been uncovered so far. There are stacks more out there to be found, and I’d encourage you to see what you can find yourself.

Once more, I’d love to hear your thoughts on the concept I raised in point 10: a fully Flow powered Salesforce environment. Goodbye, Process Builder. Goodbye, Workflow Rules. Flows seem to be taking on the responsibilities of these tools AND has the ability to do things that were previously reserved for Apex only (handle deletions, handle before/after contexts, etc.)

16 thoughts on “10 New Salesforce Flow Features to Shout About in Winter ’21

    1. Hi Tony,

      It is possible to set a value for a Name field, yes, but I think you’ll find that the Name field requires a value before you can even push the record to be saved at all, meaning you’d be unable to trigger the Before Flow because you can’t press ‘save’. I’ve seen it done where the Name field has a single letter or number in it, and this allows save/auto renaming. Would that solve your issue?

  1. Would love to hear your thoughts on the final “nails” in the PB coffin? Ischanged is definitely on that list. Others?

    1. The biggest ‘missing feature’ that my clients complain about is the fact that you can’t really add time-based actions into Flow. Sure, there are ways around this (my personal favourite being a scheduled Flow that picks up on records that meet the time-sensitive criteria that would have driven then time-based action), but it’s still a fairly common complaint.

  2. Indeed this is great stuff, but still I am waiting for a feature where screen flow can be triggered from process builder

    1. I’m not sure we’ll ever see this come to fruition… what’s your use case? There may be another way around it. You can embed Screen Flows into your Lightning Page, and only have that particular component when certain criteria are met, for example. Would this work?

  3. It is true that almost every thing that supported by Process builder supported in Flow,
    however, the ability to check ISCHANGED on fields doesn’t exists in Flows currently.
    which make it impossible to move Process builders to Flows.

    1. Hi Avi, this is a painful one to deal with as Flows currently stands. You’re right, ISCHANGED is not yet supported as far as I’m aware. That said, there are a few ways around this… one I’ve seen done a lot comes from this blog post here: https://goravseth.com/ischanged-and-priorvalue-in-before-save-flows
      Essentially, for a before save, you can query the ORIGINAL record and see if it’s different to the record variable you’re updating. If it’s different, you know the value has been changed.

  4. On the Flow roadmap over the next 12 months is ISCHANGED, ISNEW and PRIORVALUE. This will effectively put the final nails in the coffin for both workflow and Process Builder. Salesforce have stated on several occasions that Flow is their main focus and workflow and process builder will continue to be supported but not further developed.

  5. Any recommendations for a resource to learn flow inside and out? As a non-dev, it can be confusing and overwhelming. Trailhead seems to be lacking on flow training.

  6. What I have found frustrating as an admin is the fact that you now need a test coverage to deploy a flow of prices builderas active. This really puts this click-not-code mantra that Salesforce has been on for years as no longer true. What is your thoughts on this change?

  7. Does anyone have data on the impact of #6 on query limits and performance? To date we’ve been designing flows to limit queries (and limit queries in loops, especially) based on the understanding that the “Get” component is where the query occurs.

  8. They desperately need record triggered flows to support launching autolaunched flows. Before that there is no way that we ever can move to record triggered flows since they simply get too big, too complex, no reusability and timeconsuming to move existing autolaunched flows inside record-triggered flows.

Add Comment