...

• The AddOrder Instruction is used in a workflow to create a new order for a different workflow.
• Such By default added orders are run independently of run asynchronously and in parallel to the current order in a separate workflow, i.e. their execution result is not synchronized and does not have an impact on the current order.
• Should the execution of the added order be synchronized then JS7 - Notice Boards can be used, see JS7 - How to make a job wait for completion of a workflow.
• Strong Dependencies: Consider a workflow2 that should always be executed after workflow1 and that can be executed independently from workflow1. In this situation the AddOrder Instruction represents a strong dependency that guarantees execution of workflow2 for any execution of workflow1.
• Weak Dependencies: If you are looking for workflow dependencies that will apply under certain conditions only, then please check the JS7 - PostNotice PostNotices Instruction and JS7 - ExpectNotice ExpectNotices Instruction.

Workflow Instruction: AddOrder

...

• This example makes use of an AddOrder Instruction in the middle of the workflow. This translates to the fact that the receiving workflow will be started in parallel to the current workflow after job1 has been executed.
• The AddOrder Instruction can be used within any other instructions such as JS7 - If Instruction, JS7 - Fork / -Join Instruction, etc.

Configuration of the receiving Workflow

...

• This workflow specifies two variables booking_code and flight_destination.
• As neither variable specifies a default value it is necessary for the calling workflow to add both arguments when using the AddOrder Instruction.

Further Resources

• JS7 - Notice Boards