What it requires. Update Records elements should reference a record variable rather than setting fields individually using the Set Fields Manually option. Field-by-field assignment in the Update Records element requires manual maintenance whenever the set of fields to update changes.
Why it matters. When fields are set manually in an Update Records element, each field must be individually added, removed, or modified in the flow builder as requirements change. Using a record variable that is populated by Assignment elements before the Update Records call centralises the field population logic, makes the flow easier to read, and reduces the risk of fields being accidentally omitted during maintenance.
How to fix it. Refactor Update Records elements to use a record variable. Create a record variable of the appropriate object type, use Assignment elements to set the required field values, then reference the variable in the Update Records element.
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.