Universal Containers (UC) is rolling out a new offer, which must be fulfilled using Industries Order Management. During fulfillment, the…

The most efficient design that minimizes configuration is to use a single Orchestration Plan Definition. This plan would contain two separate Orchestration Item Definitions—one for activation and one for deactivation. Each item would have a mutually exclusive condition based on the order item's action (Actionc = 'Add' or Actionc = 'Disconnect'). This approach reuses all common steps in the orchestration plan and isolates only the parts that differ (the callouts), which is a core principle of scalable and maintainable orchestration design.

A: Creating two separate plan definitions is redundant if the overall process is similar, which violates the "minimize unnecessary configurations" requirement.

B: This option illogically combines two separate plans with internal conditions, which is an inefficient and confusing design pattern.

C: A single scenario cannot map multiple actions to different plans; it would require two separate scenario definitions, adding to the configuration.

1. Salesforce Help, Industries Order Management, "Conditionalizing an Orchestration Item Definition". This document explicitly describes setting conditions on orchestration items based on fields from the order item, such as the action.

2. Salesforce Help, Industries Order Management, "Orchestration Plan Definitions". This documentation explains that a plan is a reusable template, and best practice is to make them generic and control logic via conditional items rather than creating many similar plans.