Rules for Mutually Exclusive Service Plans

General rules

1. To make service plans mutually exclusive, you must configure a conflict between resources included in these service plans. The provider (or reseller) can configure conflicts only between resources the provider (or reseller) owns. All such conflicts are immediately translated into service plan conflicts.

   Important: It is not recommended to configure conflicts between resources which are already included in subscriptions. Such configuration will trigger system errors in several scenarios, for example, when a change order is placed to alter the amounts of the conflicting resources in an existing subscription. When it is necessary to create a conflict between such resources, it is strongly recommended to make the necessary changes to the existing subscriptions first.

2. All these conflict rules apply to the customer account level, that is, to the subscriptions created (or attempted to be created) by or for each individual customer. Subscriptions of different customers will not conflict with each other.
3. The delegated service plans inherit all resource conflicts from the provider.

4. You can configure a Resource to conflict with another Resource or with itself.

   Important: Configuring a resource conflict with itself may be useful when you want to allow customers to purchase only one subscription containing this resource. For more information see Scenarios of Mutually Exclusive Service Plans.

5. Resource conflicts only take effect for active Subscriptions and Services. If a Subscription is disabled, any potential conflict involving this Subscription will not take effect. The following states do not trigger resource conflicts:
   • Subscriptions with the status Terminated
   • Services with the status Removed or Not Provisioned
6. When you configure a resource conflict, only future conflicts will take effect. Subscriptions which already have this conflict are not affected.
7. You can configure a service plan which contains a conflict between its included resources, if necessary. Billing will issue a warning message if you try to do so, but will not disallow it.
8. Two service plans are mutually exclusive only if in the Resources tab of one service plan there is a resource conflicting with a resource in the Resources tab of the other service plan. If you set a child Operations resource as conflicting and the resource has not been added to the Resources tab of the required service plan, mutual exclusiveness will not apply buying this service plan.

Resource dependency rules

1. Dependency between 2 resources is two-sided. If Resource A conflicts with Resource B, Resource B conflicts with Resource A.
2. If it is necessary to configure a conflict between more than two resources, you must configure the conflict between each pair of resources.
3. Billing detects and displays information about resource conflicts for both composite and non-composite resources. If Resource A, which is embedded in Resource B, has a conflict with Resource C, then Resource B will automatically have a conflict with Resource C.
4. If a resource has a conflict with itself on the account level, and a customer purchases a service plan which contains this resource either as included or as additional, the customer can upgrade or downgrade this resource using a subscription change order. The customer also can purchase an additional amount of this resource in the same sales order. However, the customer cannot create another subscription (under the same CloudBlue Commerce account) which contains this resource.