There are no limits to how many child configurations a composite configuration can contain, nor are there limits on the number of nested configuration levels. Consequently, the scope of rule execution within a configuration tree is constrained for performance reasons.
Scopes for rule execution
The table below outlines the specific configurations where rules are executed as the result of a user or system operation. This same scope also applies to the recalculation of prices, bills of materials (BOM), and other logical outputs.
Operation |
Scope for rule execution |
|---|---|
Change of a parameter's value |
Only the active configuration. |
Addition of a child configuration |
The active configuration, parent configuration, and sibling configurations. |
Move of a configuration (in relation to siblings) |
The active configuration, parent configuration, sibling configurations, and child configurations (recursively) of all configurations that have received an updated order number. |
Delete of a configuration |
The parent configuration, sibling configurations, and child configurations (recursively) of all configurations that have received an updated order number. |
