What it requires. Relations carry no cardinality in CML AND the catalog's component rows carry no Min/MaxQuantity or required flags - nothing bounds the solver anywhere.
Why it matters. [doc + practitioner: Khaled McGonnell, 27 Aug 2026] Cardinality belongs in product master data (ProductRelatedComponent, ProductComponentGroup), which the configurator enforces; CML should not duplicate it. Where NEITHER declares bounds, the solver enumerates combinations it cannot bound ("specify the smallest required cardinality... to avoid testing unneeded combinations" - CML Best Practices), and an empty or gutted bundle is a legal configuration.
How to fix it. Set Min/MaxQuantity and required flags on component rows and group minimums in the catalog; reserve CML cardinality for what master data cannot express.
Source. Salesforce CML Best Practices; practitioner mechanism attributed (Khaled McGonnell, 27 Aug 2026)
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.