Inflight change/cancel

Gargichatterjee · ‎11-27-2023

Hi,

I have a scenario, wherein the order will take multiple days to complete. I want to implement inflight cancel/change on this order. These actions will not be through the UI, rather I need them to be implemented programmatically. In addition to this, I need to do undo transactions as well. To explain this, suppose the network is reserved, workforce appointment is booked and PONR is not yet reached. The customer can cancel the order. So the network reservation as well as workforce reservation needs to be rollbacked(undone). How can I achieve this, please suggest.

Thanks.

ShashankInamdar · ‎11-27-2023

Hi @Gargichatterjee ,

That is a good question. And here's how you can build it.

In the example below, I have two external system callouts - Reserve TN and Book Appointment.

Make use of the Order Task action to represent these.

Build a separate subflow for happy path + compensation actions as shown below.

Thus once the Order Task for 'Reserve TN' moves to In Progress, next step will be to call an extension subflow or a Flow (up to you) with the 3 different switch cases for the Revision Actions.

Within the Order Task, you have an option to configure the Inflight behaviour which will tell OM if the Order Task is to be re-executed or skipped based on the type of Inflight Change. If this is not configured, the Order Task will always be re-executed which will call the extension subflow and process the steps based on the Revision Operation (i.e. Happy path v/s Inflight Change v/s Inflight Cancel)

You can extend this logic further based on your requirements.

Hope this helps.

Regards

Shashank

View solution in original post

ShashankInamdar · ‎11-28-2023

Hard to troubleshoot only based on screenshots.

I did notice you have added an additional Input for Revision Operation, which is not required.

You should keep the OOTB inputs for Product Order Fulfilment Policy as is, and instead just add a column under conditions by dot walking on the Product Order table for the Rev operation field.

Also, unless the Cancel flow is very different from the original happy path one - you could have used the original flow (without the Revision Action as condition in the decision table) and controlled it using switch case as discussed earlier in the thread.

For a detailed view, best this is discussed over a call or via Support.

Gargichatterjee · ‎11-28-2023

In our case, we have a lot of logic in our inflight cancel and inflight change flows, that's why we need separate flows.

How can we have a discussion?

Gargichatterjee · ‎11-27-2023

In the training courses, the demo videos only show about the UI operations, what are the alternates available if we do not want to use the UI for a particular client, then it is difficult to dig up.