What it requires. Business logic values that are subject to change – such as discount thresholds, SLA days, numeric limits, queue developer names, and owner IDs – must not be hardcoded as literals in Decision or Assignment elements. They should be stored in Custom Labels or Custom Metadata.
Why it matters. Hardcoded values require a developer to edit, test, and deploy the flow every time a business rule changes. Custom Metadata and Custom Labels allow business users or admins to update values without a deployment. Note: stable, infrequently changed values such as fixed product names or business unit identifiers carry lower practical risk than high-churn values such as discount thresholds or SLA targets.
How to fix it. Move business-owned values into Custom Labels (simple text and numbers) or Custom Metadata (structured, multi-field configurations). Reference these in the flow rather than literal values.
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.