Orchestration Scenarios

Industries Order Management uses orchestration scenarios to determine when an orchestration plan definition should execute. Define an orchestration scenario by specifying a product entity and an order action such as Add, Modify, Disconnect, or NoChange.

You can create multiple scenarios for each orchestration plan definition, which is the mechanism that enables you to reuse orchestration plans across many products. When you create an orchestration scenario, you associate the previously created commercial offer or technical product with the orchestration plan using rules that are applied at runtime. For example, execute this orchestration plan if the product = X and the action on the product is Add.

You can associate orchestration scenarios with commercial products as well as technical products.

Class-Based Scenario

Defining scenarios on a product class instead of individual products results in a considerably smaller list of scenarios. For example, A customer uses a catalog with a flat hierarchy but has a large number of products. The customer requires identical orchestration for all products, which can happen when using Order Management in a COM situation that only involves higher-level orchestration.

In that case, you would define an orchestration plan definition for the Assetization task, which must have a scenario expressed on the commercial products. Scenarios must apply to all products in the catalog. The alternative is to create a product class, assign the class to all the products in the catalog with a field setting, and then define a single scenario for the product class.

Using Complex Scenarios

You define Order Management scenarios with a minimum of Product and Action. You can add a sub action, but you can also create more complex conditions that are based on attribute values. This provides flexibility in conditions and is useful for controlling MACD scenarios.