Product Scoping Rules Now Supported in Configuration Exchange
Product Scoping Rules can now be imported via Configuration Exchange, both as direct selections and as automatic dependencies of journey schemes that reference them in a Manage Products task. Once imported, Product Scoping Rules behave consistently with other rule types — when a Manage Products task is triggered in a journey in the target tenant, it applies the latest available version of the rule.
Key Details
- Product Scoping Rules are selectable in the Configuration Exchange ADD modal under the Product domain, alongside Product Requirement Sets.
- When a journey scheme containing a Manage Products task with an assigned Product Scoping Rule is imported, the rule is captured automatically as a dependency. The dependency defaults to the latest version available at the Configuration As Of date and can be overridden if required.
- The version selected in the source tenant's Manage Products task is not carried into the target tenant. When the Manage Products task is triggered in a journey in the target tenant, it applies the latest available version of the rule.
- Product Scoping Rules now follow the same import behaviour as other rule dependencies in Configuration Exchange.
Implications
- When a Product Scoping Rule is updated, configurators should review the Manage Products task configuration in any journey schemes that use it and confirm the rule still returns the intended set of products. A warning message is displayed when scoping rule changes are made to support this.
- Journey schemes should reference the latest version of a Product Scoping Rule except where a specific version is required for A/B testing.