FL-001MediumMaintainability
What it requires. Every Flow must have a populated description field explaining its purpose, the objects it touches, where it is invoked from, and the business process it supports.
Why it matters. Without a description, the next person to maintain the flow has no context for what it does, why it exists, or what it touches. This significantly increases debugging and handover time.
How to fix it. Populate the description field with: what the flow does, which objects it touches, where it is invoked from, and its entry criteria.
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.