Introduction

In some cases, because of business/functional reasons/ some products / services / component cannot live together in the same context (Account, Order Item or Order), or the opposite, you may want to force a Product B to exist in order to be able to select a Product A.

This is where the Compatibility Rules comes in place. With the Compatibility Engine you can specify which Products excludes or requires other ones and the Configurator would validate those rules when setting up an order.

Setup

The Compatibility Rules are defined at Product level. This is, the compatibility rules apply to any Product Version of that specific Product.

When you create a compatibility Rule you need to specify the following fields:

Scope

The Scope defines what Assets or Order Items should be considered when checking if a Target product exists or not.

For instance:

• Make Product A excludes Product B if it’s in the current order or it’s already contracted by the customer.
• Make Product A excludes Product B it it’s in the same order item.
• Force Product A to have Product B as a sibling in an order item.
• etc

You can pick one of the following values when defining the scope: