Designing an OMS Flow with Dynamic Mid-Process Entry for Omnichannel Features

[AGmint]

I’m designing an Order Management System (OMS) flow with omnichannel capabilities. Here’s the high-level architecture of the process:

Order Received

• Validate Order (call activity)
• Manage Payment (call activity)
• Order Fulfillment (call activity)

Some channels handle the “Validate Order” and “Manage Payment” steps independently on their side, but the “Order Fulfillment” step needs to enter the orchestrated OMS process flow.

I want to design this architecture so the process flow can be entered dynamically at the “Order Fulfillment” stage when the earlier stages are already completed externally.

Here are my questions:

1. Process Instance Creation: How can I start the OMS process flow dynamically from the “Order Fulfillment” step if the process instance does not already exist?
2. Process Instance Modification: Is it feasible to use Camunda’s process instance modification to move the token directly to the “Order Fulfillment” point in the process?
3. Process Design: Should I design separate process flows depending on the starting stage, or is there a better way to handle this in a single process flow?

Any advice or recommendations on the best approach to implement this in Camunda would be greatly appreciated.