Asynchronous order processing for large customer and consumer orders
Asynchronous order processing handles high-volume enterprise and consumer orders without waiting for immediate processing, improving system performance for communications service providers (CSP) using Order Management.
Overview of asynchronous order processing
CSPs support both enterprise customers and consumers. Enterprise customers typically place large multi-site orders, while consumers place high-volume orders. Asynchronous order processing enables you to create bulk or high-volume orders without waiting for each order to be processed immediately, improving efficiency and system performance.
When you submit an asynchronous order request, the system responds with a 202 Accepted status and an order ID. This indicates the order is received for processing but not yet created. This differs from
synchronous processing, which returns 201 Created when the order is immediately created.
- Order validation
- Order ingestion
- Order creation
How synchronous order processing works
With synchronous order processing, an order is received in the Order Management application through the API. Then, the order records are simultaneously created in a customer order table after the order validation.
As an administrator, you can activate or deactivate the order validation for synchronous order processing by setting the create_product_order_validation_sync and create_service_order_validation_sync system properties to True (Default) or False in the ServiceNow AI Platform. Synchronous order processing takes longer than asynchronous order processing when it comes to creating a large number of customer order records.
How asynchronous order processing works
In asynchronous order processing, high-volume orders or large numbers of order payloads are received through the Product Order Open API in the Order Management application from external Configure, Price, and Quote (CPQ) systems.
The order details are first validated and then inserted into the Inbound Queue [sn_tmt_core_inbound_queue] table. If validation errors occur, an error message is returned in the response. The actual order creation happens later when a scheduled job processes entries from this queue, allowing for bulk or delayed processing.
This validation is managed by the create_product_order_validation_async system property for product orders and the create_service_order_validation_async system property for service orders. These properties control the validation in the asynchronous processing of orders before the orders are inserted into the Inbound Queue [sn_tmt_core_inbound_queue] table. The default value is set to True.
When the order details are successfully validated, a scheduled job runs to pick up the records from the Inbound Queue [sn_tmt_core_inbound_queue] table and then creates entries in the customer order table as shown in the following diagram.
- You must activate the Product Order Open API. The new parameter mode enables the API to process orders synchronously or asynchronously. For more information about the API, see Product Order Open API.
- After you receive high-volume orders or large numbers of order payloads through the Product Order Open API in asynchronous mode, the system responds with a
202 Acceptedstatus and an order ID. The order details are validated first and include the product offering, order line items, order specifications, order line item characteristics, and the specification relationship of order line items. For more information on how the validation works, see Validating your orders through asynchronous order processing. - After the validation of the order details is complete, an entry for each order with a unique record ID is created in the Inbound Queue [sn_tmt_core_inbound_queue] table. To learn more about how the order entries are created, see Create order entries manually during the asynchronous order processing.
- When all the orders are captured in the Inbound Queue [sn_tmt_core_inbound_queue] table, a scheduled job runs to create the customer orders for the records in the New state. You can also manually trigger order creation from the Inbound Queue module by selecting the Create Order button, bypassing the wait for the automated job. After processing, you can verify the created orders in the customer orders section. To learn how a scheduled job creates orders, see ../task/running-scheduled-job.html.