This article gives a tip on closing domain orders if there is no orchestration plan attached to it.

Feature: Closing Domain Orders

Application: Order Management

Release: All applicable

DYK (Did You Know) is a series of articles that introduces simple and basic concepts of the working of ServiceNow TMT Applications.

On receipt and approval of an Order, ServiceNow OMT decomposes the order and creates Domain Orders corresponding to each decomposed domain entity – i.e., Product, Service, Resource – subject to the Catalog model.

Against every domain order one may invoke a Subflow for orchestration activities related to that specification. But often, there are such specifications which are only for representation or to create an inventory record but without any specific orchestration activity.

It is a good practice to close all the domain orders and, in a bottom-up fashion.

For such domain orders that do not have a specific orchestration plan, this article describes a best practice on closing it with a generic Subflow.

The pseudo logic is very simple –

Set the Domain Order in an ‘In Progress’ state.

Look Up for Records in the Domain Order table where the current order is a parent.

For each record found,

Wait until it is closed.

Set the Domain Order in an ‘Closed Complete’ state.

Doing so will avoid any unnecessary system generated fallouts and close the line items and order cleanly.

The below is an example of a Subflow set up for a Service Order. The same principal follows for the Product or Resource Domain Order as well.

Create input for Service Order

Select reference.sn_ind_tmt_orm_service_order

Set State to In Progress and Look up for Child Domain Order records

Wait for each Child Order (if any) to complete