If you were in a situation that you are managing a Salesforce organization that is many years old, you might run into the issue of being overwhelmed with locating the correct flow to update from a long list of flows. Not only short names, irrelevant names, it is also that many of these flows are inactive. Things get worse when you inherit an org and flows are named by different persons. It is even likely that you will not be able to locate a flow that you created yourself, and the reason is simple, you did not have the time to think of a name of your flow. It is like searching for a needle in a hay stack, and while you are very busy.
A good name is important to the flow quality as much as what it does inside, choosing a self-descriptive name is important for you as an admin and important for other team members to locate it easily.
Path Technologies suggest the following convention when creating a flow:
On flow trigger that optional condition: main action
Examples of flow triggers are:
- An account is created
- An opportunity is updated
- The status of a lead is changed
And for scheduled flows:
- On daily basis at 20:00
- On monthly basis on first Monday
Main action is what the flow is doing after the trigger happens, for example:
- Create a task and assign it to the sales representative
- Notify the customer on the change
- Iterate on cases and close them
An optional condition can be added to the name, such as:
- Ticket with high priority.
- Opportunity amount > 100,000 USD