3 New Features of Summer 22

Hello folks,

Summer 22 is arriving soon, and I am here to give you a quick tour of the new functionality coming your way.

But before I do that, I would like to share that I wrote a brand new post for Salesforce Ben. It was published a week ago, and it is still the number one post on the site. Please read my post titled “7 Foundational Skills Before Learning Salesforce Flows” here.

The format of this post will include pictures more than words. Let me show you screenshots of what is coming. This release is loaded again with flow enhancements:

1-Flow Trigger Explorer supports manual reordering of triggered flows. You can create a new flow right from this dialogue. This action will prefill the start element for you. RT Orchestrations are also supported, which I have not seen or tested yet. When you open Flow Details and Versions on the right-side panel, you see all flow versions. You can open each version via a link and activate the version you want on this side panel. This functionality is better than the existing alternative in my humble opinion.

2-RT Automation got some serious love in this release. Now we can build complex formulas in our start entry criteria. Let me test and tell you how debugging works later. We get assistance via field and function pickers when building the formula. You can go crazy now with field values, prior field values, and functions.

The formula builder checks syntax similar to the formula field builder of the object manager. If you are sloppy with your work, you will get a red error message when you check syntax via this button. The formula resource builder did not get any love though, as far as I know.

3-Low-code flow testing comes to life. On your flow canvas, you will see a “View Tests” button on the upper right side. You will have to agree to the terms when you click on it because the functionality is in beta as of Summer 22. Then, you click create, and you start building your test.

I played around with the test builder a little bit. Disclaimer: I don’t know anything about the functionality. I saw this error message very frequently. At least for now, I can easily say this functionality deserved the beta badge.

Next week, I will continue my preview with the new screen flow functionality.


P.S. Originally published on 04/18/2022.

Read the previous issue of the newsletter here.

Read the next issue of the newsletter here.

Subscribe to the weekly educational Salesforce Flow Tips newsletter here.


10 Things I Hate About Flows

Hello folks,

You can either read this post below or watch the embedded video on YouTube.

In January, I asked my Twitter followers what they hate about flows. In the start-up world, there is a famous saying: Your biggest source of learning is your dissatisfied customers. It is essential to shape your product based on customer feedback, especially in your start-up phase. I think the same principle applies to product management in big corporations.

What do flow users get most frustrated about? Salesforce flow product team, if you are listening, go to the whole thread by clicking here.

I gathered all the feedback to come up with one list.

Don’t get me wrong. I love building flows in the end.

The top 10 things I hate about flows are:

  1. Lack of wizards/configurators: Let’s say you need to create a task or opportunity in your flow. You need to remember the required fields and make sure that you pass values to all of them. Can’t we give the user a builder interface, a wizard, or a configurator? At least something that resembles the create task action in workflow rules.
  2. Error messages that are not understandable/actionable: Have you ever received an error message that does not mean much. You don’t understand what is going on and what you can do to fix it. If you get a GACK, your only option is to start deleting recent changes or going back in versions. Pro-tip: Check field-level security if you receive an error message around a get or update/create. 
  3. Validation Rules in Screen Flows: Have you ever wondered why the validation rule logic in screen flows is the exact opposite of what it is in Salesforce field builder settings? Unfortunately, I don’t think there is a good explanation. I guess this never made the idea prioritization list.
  4. You have a get in your flow that does not find a record. You will get an unrecoverable error if you reference that record variable in your flow after your get element. After the get element, you need to add a decision to check for that. But why? Can’t we build the null check inside the get element?
  5. Screen formatting options for screen flows: You can create a screen flow and run your flow on a community page. The user can access it on a mobile phone. You can also deploy and launch your flow on the Salesforce mobile app. If you have done that, you will know: The labels look gray, the letters are not big enough. The borders for the input boxes are in low contrast. You can use some workarounds for some components, but you are out of luck with some others.
  6. Choosing resources in screen flows: You must display some field and formula values and some static screen text messages to the user. You don’t have the option of displaying a screen field component that is read-only. You need to use a display text component and drop in those resources. Have you tried doing that with just mouse clicks? It is impossible. You click and drill down to get the field value under a record variable, and boom, your selector resets. You have to use your enter key instead of mouse clicks. But why? I don’t know. This issue has been there for years.
  7. Trigger entry criteria: When you are working with triggered automation, you don’t have access to many field values. And you cannot use a formula to evaluate the entry criteria either. Wouldn’t it be nice to use the created date and the last modified date here? How about the record-type developer name?
  8. Formula builder & formula debug: The resource picker is the only help you get when building a complicated formula. The functions are not available in a picker like in the Salesforce field builder. You have to remember or Google them. And when you have an error in your formula, you only find out about it when you save your flow. You cannot see the error messages in the formula builder dialogue.
  9. Deployment via button: You want to deploy and launch your flow on the record page via a button. Then you must create a quick action in object manager to do this. There is also a button option in the object manager, but that’s not it. And you need to remember to create an input variable in your flow exactly named as recordId. Why all that? Let’s make things a little simpler.
  10. Email: There are many ways you can send emails from your flow. None of them are great. Can we make this simpler?

Enjoy your flow-building journey.

P.S. Originally published on 02/27/2022.

Read the previous issue of the newsletter here.

Read the next issue of the newsletter here.

Subscribe to the weekly educational Salesforce Flow Tips newsletter here.