What it requires. CML source references pricing fields such as ListPrice or NetUnitPrice.
Why it matters. [doc] "Pricing fields, such as ListPrice, NetUnitPrice, and others, are not supported in CML and should not be used in constraint models" (CML Best Practices). The constraint engine does not evaluate pricing context, so such constraints silently fail to enforce - configurations pass that should not.
How to fix it. Remove pricing references from the model; express commercial limits through pricing procedures and adjustments where they are evaluated.
Source. Salesforce CML Best Practices (developer guide)
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.