What it requires. Apex action calls, subflow invocations, and Decision elements must have a description field populated explaining their purpose. This is distinct from the flow-level description (FL-001) and applies to individual element annotations within the flow.
Why it matters. Complex elements – particularly Apex actions, which invoke external code, and subflows, which invoke separate automation – are opaque without descriptions. A reviewer looking at the flow canvas cannot determine what an Apex action does or why a Decision branches the way it does without opening and reading each element. Descriptions make flows readable without requiring element-by-element inspection.
How to fix it. Add descriptions to all Apex action, subflow, and Decision elements. The description should state: what the element does, what inputs it uses, and what it outputs or decides.
Source. Salesforce Admins: The Ultimate Guide to Flow Best Practices and Standards – Document every step
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.