Rules for Mutually Exclusive Service Plans

General rules

  1. Conflicts between service plans originate from conflicts between resources. 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 those resources which are already included in some subscriptions. Such configuration will trigger system errors in several scenarios such as, 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 be in 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. Namely, the following states do not trigger resource conflicts:
    • Subscriptions in the status Terminated
    • Services in the status Removed or Not Provisioned
  6. When you configure a resource conflict, only future conflicts will take effect. Those 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. OA Billing will issue a warning message when you try to do so, but will not disallow this.
  8. Only the conflicts involving Resources that are listed on the Resources tab of service plans take effect. If you configure a conflict involving a child OA Operations resource that has not been added to the Resources tab of a given service plan, the conflict will not take effect during the order placement process to buy this service plan.

Resource dependency rules

  1. Dependency between 2 resources is two-sided. If Resource A conflicts with Resource B, that means that Resource B conflicts with Resource A as well.
  2. If it is necessary to configure a conflict between more than two resources, then you must configure the conflict between each pair of resources.
  3. OA 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 via 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 Odin Automation account) which contains this resource.

Online Store rules

  1. When a customer selects some service plan in Odin Automation Online Store (or another integrated online store), the Online Store checks the possibility to buy this plan and the selected resources (using the API methods GetBasketPrices_API and PlaceOrderAndAuthorize_API). If there is a conflict, the system returns a warning message and prohibits such purchase.
  2. If a customer is not logged in, only the conflicts between the service plans and resources in the basket are checked.
  3. If a customer is logged in, both the conflicts within the basket and the conflicts between the basket and the already purchased subscriptions are checked.