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 schemas that reference them in a Manage Products task. Once imported, the Manage Products task in the target tenant uses the version of the Product Scoping Rule that was selected during the import.
Key Details
- Product Scoping Rules now follow the same import behaviour as other rule dependencies in Configuration Exchange.
- When a journey schema 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 latest version of the Product Scoping Rule available in the target tenant (i.e. likely the imported dependency) is the version applied the Manage Products task in the imported journey schema. This may not be the same as the version configured against that Manage Products task in the source tenant Journey Schema (i.e. if the dpendency version was different).
- We already warn users when a newly published Task Display Product Scoping Rule is linked to one or more Manage Products task in Journey Schemas that may need to be updated to the latest version.
- Journey schemas should reference the latest version of a Product Scoping Rule except where a specific version is required for A/B testing in lower tenants.