Inclusion rules determine whether a parameter is an active part of the configuration model or not. When a parameter is excluded by these rules, it is automatically hidden from the user interface and disabled in the background. A parameter whose inclusion is controlled by these rules is excluded by default and is only included (and made visible) once one or more of the rules are triggered.
Definition of trigger and parameters to include
An inclusion rule contains an optional trigger and one or more parameters whose inclusion is controlled by the rule.
The trigger is defined by first selecting the parameters to include, and then selecting the specific values for each parameter that will trigger the rule. For multi-choice parameters, individual multi-choice values are selected to trigger the rule, rather than the parameter as a whole. An inclusion rule is triggered when all triggering parameters match their defined values.
See Disallowed combination rules for details on how triggering values are defined for different types of parameters.
For lookup parameters, you can define non-triggering values instead of triggering ones by selecting the Check non-triggering values option. Consequently, any unselected values act as triggers, and any newly added values will trigger by default.
The parameters whose inclusion is controlled by an inclusion rule are selected in the Inclusion parameters list. Selected parameters become active and visible when the rule's triggering condition is met. If multiple inclusion rules or inclusion expression rules affect the same parameter, it is sufficient for just one of these rules' triggering conditions to be met for the parameter to be included (and made visible).
Parameters that always shall be hidden
By creating an inclusion rule without a trigger, the parameters selected as Inclusion parameters will always be excluded, unless they are made active by another inclusion rule or inclusion expression rule. This can be used, for example, when introducing new parameters that should not yet be available to set, but are required to prepare other parts of the configuration model, such as prices, bills of materials, or visualizations. By also setting the site effectivity for the rule, the new parameters can be made available for testing in the administration site while remaining excluded (and hidden) in the production site.
Excluded parameters are disabled
A parameter that is excluded via inclusion rules is also disabled. This means that the parameter is not an active part of the configuration model.
To prevent errors when the system evaluates expressions elsewhere - such as in bills of materials (BOM), reports, or graphics - the excluded parameter must still provide a value. Therefore, it automatically receives the default value of its data type during expression execution.
Additionally, the parameter will not retain any saved value; even if the user had manually set a value before the parameter became excluded, that value is discarded. Note the difference compared to a parameter on a hidden tab, which is still included in the model and can hold its value even though it is invisible to the user.
Restoring values upon reappearing
If a parameter that has been assigned a value becomes excluded and is later included again during the same editing session, the system will attempt to restore its previous value. However, if this value is no longer allowed due to other rules, the parameter value is cleared.
