Overview
Creating effective product configurations requires establishing rules that guide the selection process. The Lighting Exchange product configurator offers a flexible rules engine designed to accommodate various types of constraints to meet different configuration needs. Rule constraints are the first step in creating a rule and ensure that products are configured accurately and efficiently.
The Lighting Exchange currently supports four primary constraint types:
- Required
- Not Compatible
- Only Compatible
- Explicitly Compatible
Each constraint type serves a unique purpose in ensuring accurate product configurations. Below is a detailed explanation of each type.
Required Constraint
The Required constraint ensures that a particular code/value, attribute group, or entire attribute is necessary for another code/value to be selected. This type of constraint enforces dependencies between selections, ensuring that all necessary components are included.
Example:
- If “Dimmable Driver” is selected, then a “Control Type” must also be selected.
Not Compatible Constraint
The Not Compatible constraint prevents the selection of a particular code/value, attribute group, or entire attribute when another specific code/value is chosen. This type of rule helps avoid conflicting selections and ensures that incompatible components are not configured together.
Example:
- If “Canadian Voltage” is selected, then “Emergency Battery” cannot be selected.
Only Compatible Constraint
The Only Compatible constraint means that a specific code/value, attribute group, or entire attribute can only be selected if another particular code/value is also chosen. However, it does not restrict the dependent code/value from being compatible with other options.
Example:
- If “RGBW Color” is selected, the “DMX Control” must also be selected, but “DMX Control” can be used with other attributes as well.
Explicitly Compatible Constraint
The Explicitly Compatible constraint ensures that a code/value, attribute group, or entire attribute can only be selected when another specific code/value is chosen, and it also restricts the dependent code/value from being compatible with any other codes/values.
Example:
- If “Outdoor Rated” is selected, then “Weatherproof Housing” must also be selected, and “Weatherproof Housing” cannot be used with any other code.
Conclusion
Understanding and applying the correct rule constraints in The Lighting Exchange product configurator ensures a streamlined and error-free product configuration process. By leveraging the flexibility of the rules engine, manufacturers can guide users toward accurate selections while preventing incompatible or incomplete configurations.