feasible to create additional Service Order through the decomposition rule during inflight cancel?

[Abinesh]

Our requirement is to create a seperate service order when a order is cancelled inflight (revision operation = cancel).
Tried staggering decomposition method to achieve this. Created a characteristics to trigger the decomposition, but attribute mapping and decomposition rule works when the order is in progress, but when the order goes into revision, both mapping and decomposition is not working. is this expected behaviour? 
Please anyone help on how to create a service order when order is in revision.
is it possible to create service order in runtime ? is it advisible?

[MolayD21]

Hi @Abinesh,

Could you please explain the business justification for creating a new service order during inflight cancel? Ideally, when an order/order line item is being cancelled, all the children domain orders should also be cancelled. But yes, we may have to perform some steps (say, freeing up the reserved resources). This kind of work can be achieved using a sub-flow which can be triggered from the respective order fulfillment policy decision table.

BTW, what would happen to the newly created service order when after the order is cancelled inflight?

Thanks,

Molay

[Abinesh]

Business is tracking theyre tasks using the service orders instead of OMTask. thats why we need to create a new service order a task that will be performed when we can an inprogress order.

Does staggering decomposition work on a disconnect order (delete action).

[ShashankInamdar]

Hi @Abinesh ,

@MolayD21 makes a valid point. Based on your description, the approach you are considering does not sound right. Also, even if you were to create a new Service Order, this will end up creating an inventory record for a Product/Service that has been cancelled. 

Staggered decomp will not work here.

An option you may have, is to create the required domain order in the subflow specifically for this scenario using conditions such as revision operation = cancel, etc.

But a word of caution that this is not an OOTB way of working.

Question back to you, what happens to this Domain Order that is planned to be 'added' as part of the Disconnect order? Will you then set it as 'Inactive' at the end of orchestration?

[Abinesh]

Hey @ShashankInamdar & @MolayD21,

so the a downstream system integration call is made when a disconnect order is raised. This downstream system sends a bag to return cpe. Basicallu the new service order will be used to track this return bag process. 

Ideally this should have been handled in an OMtask. But business wants it has a service order. 
Hence i opted for the staggering decomposition.