Exclude Rule

The exclude rule has this syntax.

The type must be leaf type, a node without children.

In the exclude rule, if a user sets attribute values in Product Catalog Management (PCM) that violate the rule requirements, the constraint engine overrides the user input in order to validate the constraint. This behavior is different than other constraints, in which the constraint engine doesn't override user input, but displays an error if user input violates the constraint. See How User Input Order Affects Constraint Engine Behavior section in Logical Constraints.

In this example, the exclude rule automatically removes the Heater_120 heater from the type GeneratorSet if the Voltage3 is greater than or equal to 4160.

Exclude a Child Product Based on Another Child Product's Attribute

When a bundle contains multiple child products, you can exclude one child product based on an attribute value set on a sibling child product. To evaluate a child product's attributes from the parent scope, use the count() aggregate function on the parent's relation. The count() function inspects instances within a relation and counts those that match a given condition. When the count is greater than zero, at least one child instance satisfies the condition, and the exclude rule acts on that result.

Use this pattern.

In this example, the GeneratorSet bundle contains both Heater and StandardCooler child products. If any Heater in the configuration has an outputClass of High-Output, the StandardCooler is automatically excluded because high-output heaters require an industrial-grade cooler.