Static rule
Rule type – Abstract
Purpose: Is considered as 'passed' or 'failed' depending on the 'switch position' statically defined in the configuration.
The Static rule is considered as 'passed' or 'failed' depending on the 'switch position' statically defined in the configuration.
Configuration
Configuration |
Effective effect |
Purpose |
|
|
A Static rule that is always considered as 'passed' is often used as the only rule in an association criterion with very low priority. This association criterion can then be used for assignments that are to define the 'fallback' in the case of an association via the best matching principle, which is always assigned if no other association criterion (with higher priority) applies in a context. The Static rule can also be used to define an association criterion that is used as a Sub criterion rule in other rules. Then the configuration of this association criterion can act as a 'central switch' for the logic in many places in the system. A use case would be an association criterion 'BETA_MODE', which can be specifically set to 'ON' or 'OFF' by configuration, in order to temporarily switch a bundle of additional functionalities active or inactive in an existing system. Within a more complex rule, a Static rule with the switch set to 'ON' acts as a vertical bypass, which means that any disjunction rules to the right are no longer evaluated. With the switch set to 'OFF', the Static rule acts as a horizontal bypass (to the right), so that any conjunction rules below it are no longer evaluated. The Static rule can therefore be used when developing and testing more complex rules to be able to set logical 'aggregates' temporarily active or inactive. |
|
|