You are here:
OM Plus: Queued Orders
When orders are submitted from CPQ to Order Management Plus, they are placed in a persistent queue. If Order Management Plus is down, or a catalog synchronization is in progress, the order is held in the queue until communication is restored.
After communication is restored, the order is then processed for fulfillment. Manual intervention is not required when attempting to submit orders to the system. To set up automatic order-submit queuing, see Configure Automatic Order-Submit Queuing.
Order-submit queuing can be achieved successfully under the following conditions:
-
Order Management Plus is enabled for the org but a full catalog sync has not been performed. Orders cannot be submitted to Order Management Plus until the full sync is complete. Orders are queued until the full sync is done.
-
There were changes in catalog that have not yet been synced to Order Management Plus.
-
The AWS region is down.
If the submit fails due to an application error (for example, if the submit API is pointing to the wrong place), then the order is moved out of the queue and marked as Failed or Rejected.
On the Orders page, the Fulfillment Status is Queued and the Processing Log field stores the reason why the order was queued, for example, Catalog changes pending or non operational.
To cover combinations of the above scenarios, Order Management Plus tracks the version of the catalog from which the order was created. The names of Sync Delta Object records increase in numerical sequence. Therefore, Order Management Plus uses the highest Sync Delta Object index as the version of the catalog from which the order was submitted. If there are no Sync Delta Objects in the system, then any order can be submitted as soon as Order Management Plus is available.
After a full catalog sync is completed, the org is transitioned into Operational state. In this state orders and catalog changes are passed to Order Management Plus. On the Orders page, the Fulfillment Status is In Progress and the Processing Log field stores the reason why the order was queued.
- Configure Automatic Order-Submit Queuing
When orders are submitted from CPQ to Order Management Plus, they are placed in a persistent queue. If Order Management Plus is down or a catalog synchronization is in progress, the order is held in the queue until communication is restored. - Order Object Model Components for Submitting Queued Orders
To track the catalog version, the order data model contains the Max Sync Delta Index field. This field is equal to the maximum index of Sync Delta Objects, if any. Otherwise, this field is empty.
