Automation

Salesforce added an option to control the transaction in Screen Flows in the Spring '21 release. It is possible to configure actions to let the flow determine whether it requires a new transaction to successfully execute the action.

With the new Flow features of the Spring '23 release, Salesforce convinced us that Flow is really giving us the powers of developers. Now you can make an HTTP Callout from Flow without any code!

Since Screen Flow supports the screen element, it doesn't run in the background and it can be considered as the only visible flow type. However, should they always be visible?

Spring ’23 release is approaching and it will be in our environments soon. Just like the last few releases, also this release has many exciting features for Salesforce Flow.

In order to delete multiple records from a list view, it is possible to build a flow and create a custom button that calls it from a list view. After selecting multiple records and clicking this button, flow will run for the selected records and perform the actions.

Using the In and Not In operators, you can get related records without using a loop. These operators make the flow use less SOQL queries and DML statements.

It is possible to build a screen flow with some questions and use it as a customer satisfaction survey. Salesforce users can use flows, but how can you make a flow public so that your customers can use it as well?

Just like in Lightning pages, it is possible to add active Screen Flows to pages of Experience sites. This way, you can let the external users run flows.

When you upload a file to Salesforce, it can be viewed internally. However, what if you want to create public URLs and share them outside of Salesforce?