How to single out a specific task even if there are multiple quantities on the order line

[Satoshi Abe]

In Sale and Order Management, when ordering multiple items, create and approve an order with a quantity of 1 to, say, 10 for the subject item in the catalog.

After approval, the order is broken down based on the configuration of the catalog and a task is generated for each domain order, but if the quantity is 10, 10 tasks are also generated.
Depending on the type of the tasks, it may be preferable to execute them one at a time. For example, if I have a task to “send a delivery email to a customer,” and the quantity is 10, 10 tasks will be generated and 10 emails will be sent, but one task is sufficient.
Is it possible to change the way ServiceNow generates tasks based on the task type and quantity?
I would like to use the OOB functionality as much as possible, so I want to do this in a way that does not require scripting.

[ShashankInamdar]

Hi @Satoshi Abe 

A potential solution for this is to invoke a flow at the Order Line Item level and have a single task for the 'n' quantity.

You will need to take care of any dependencies between this task and others as may be necessary.

[Satoshi Abe]

Hi @ShashankInamdar 

Thanks for the advice.

What would be a good trigger to use when calling a flow at the Order Line Item level?
In OOB, after the order is approved, the order line is decomposed and a domain order is generated. I think it is necessary to set up an Order Task Relation between the tasks generated by the domain order and the tasks generated by the flow at the Order Line Item level, and if the trigger is not set appropriately, inconsistencies will occur.

[ShashankInamdar]

I agree.

But this will depend on your specific orchestration flow.

Here's an approach that could work. W release onwards you can define Order Characteristics without them being tied to a Specification - so these are essentially Order Item level attributes that do not get stored in the inventory. All you need to do is define this before hand as a characteristic in the Catalog model that is not tied to a Specification.

In the solution, you could define the Characteristic as 'Ready for Delivery' (true/false)

So on Order submission, one of the first steps will be to create this Order Characteristic attached to the top level OLI with default value as 'false'.

Based on your orchestration flow, at the appropriate stage you can set this to true.

And this then can be the trigger for you to call the Flow at OLI level.