Flow

Salesforce announced that Workflow Rules and Process Builder will be deprecated in the near future. Therefore, it is time to start converting your existing workflow rules and Process Builder to flows. For this purpose, Salesforce released a new tool called Migrate to Flow Tool (Beta).

It is obvious that before save flows run before the after save flows. But in some cases you can have multiple flows with the same trigger type (before or after save) and the same start criteria. Or you can have flows without even a start criteria. So, which one will run before?

Email messages play an important role in Salesforce environments. In some cases it is important to track the email opens. You can use a flow to calculate the email open rate of a specific recipient.

A picklist field in Salesforce lets you choose a value from a predefined list. Choices have two main attributes: Value and API Name. Value is the text that the user sees on the user interface. At the other hand, API Name is the value that is stored in the field.

Record-triggered flow is the only flow type that runs automatically when a record is created, updated, or deleted. Depending on what you want to perform, you can choose the flow to run before or after the record is saved.

Approval process is an automation tool that lets users approve records in Salesforce. You can add actions to initial submission, approval steps, final approval, final rejection, or recall. However, there are only four supported actions.

The standard Clone with Related button is available for Opportunity and Campaign objects. What if you want to clone another object with its related records? It is possible to achieve this with Salesforce Flow.

Although the official release notes of Spring '22 are not available yet, here is a sneak peek at some of the new flow features that you can expect.