Flow naming conventions
Why is this an issue?
Inconsistent flow naming makes flows difficult to find and understand:
Administrators spend more time searching for flows.
The purpose of flows is unclear from their names.
Related flows are not grouped together in lists.
Maintenance becomes harder as the organization grows.
Examples
Example of incorrect naming:
Flow names:
- flow1
- UpdateAccounts
- my_test_flow
- Account automation
Example of correct naming:
Flow names:
- Account_Before_Insert_SetDefaults
- Account_After_Update_SyncToExternal
- Contact_Screen_UpdateAddress
- Opportunity_Scheduled_SendReminders
A good naming convention includes:
Object name
Trigger type or flow type
Description of what the flow does
How can I fix violations?
Adopt a naming convention: Establish a standard format for your organization.
Include the object: Start with the object the flow operates on.
Include the type: Indicate if it's a record-triggered, screen, scheduled, or autolaunched flow.
Describe the action: End with what the flow does.
When should I disable this rule?
You may dismiss specific violations for utility flows that do not relate to specific objects.
Resources