Salesforce Flows – 26 Features Introduced in Spring ’23 Release

Salesforce Flows Spring '23 Features

Flows is the present and future of Automation in Salesforce and continues to take more and more Centre stage. Every Salesforce release contains tens of enhancements to Flows. In Spring ’23 Release of Salesforce, we could find about 26 enhancements related to Salesforce Flows.

And here is our top pick from these enhancements:

  1. Make HTTP Callout from Flow (Beta)
  2. Flow Limit of 2000 Elements Removed
  3. Select a Value from a List of Choices with the Choice Lookup Component
  4. Data Table now in GA
  5. Convert Processes to Flows with the Migrate to Flow Tool
  6. Run Flows in User Context via REST API
  7. Add Lookup Fields to Your Flow Screens with Ease

To make it easier for you to understand these new features and enhancements, we have created a presentation with screenshots and link to the related Spring ’23 release note articles.

Introducing Mastering Salesforce Flows Training Course

Liked this post? We are now offering a complete self-paced, video-based training course on Mastering Salesforce Flows. The course comes with downloadable step-by-step PDF guides, unlimited access, free upgrades, area to ask questions, free preview & 100% money back guarantee. For more details, please click here.

Need Help with Flows?

Need advice on Flows? I also offer advisory & consulting services on Salesforce Flows. So, whether you want to create new Flows or migrate existing automations (Workflow Rules, Process Builder, Triggers) to Flows, I can help you analyze, design, plan & review. To initiate a discussion, please submit the contact form here stating your requirement or book a 30-minute free discovery call at this URL.

References & Useful URLs

2 thoughts on “Salesforce Flows – 26 Features Introduced in Spring ’23 Release”

  1. Charles Thompson

    Hi Ashish.

    Thanks for this excellent summary.

    I’m particularly happy to see the 2000-element limit go away finally. As the product team says, “it was somewhat arbitrary”. Of course, other recent improvements such as batching in Scheduled Flows and the collection processing elements have made it easier to avoid 2000 runtime steps, but I’m very happy to no longer have to deal with this limit.

    1. Thanks Charles as always great to hear from you.

      I completely agree with you. This limit was too limiting and one of the major concerns in using Flows (at least for me). Now Salesforce has taken care of it!

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Don't Miss Our Pre-Launch Offer on "Mastering Salesforce Flows"

27% Off + FREE Premium Membership

Expires In

:
:
: