...

• The AddOrder Instruction is used in a workflow to create a new order for a different workflow.
• Such orders are running independently from By default added orders run asynchronously and in parallel to the current order in a separate workflow, i.e. their execution result has no is not synchronized and does not have an impact on the current order.
• If the execution of the added order is to 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 which should always be executed after workflow1 and that and which can be executed independently from of 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

...

A workflow can include an AddOrder Instruction. Consider the workflow properties to holdfor holding, for example, two variables booking_code and flight_destination.

...

AddOrder Instruction Properties

The AddOrder Instruction is available can be added from the panel icon icon  and can be added to any position in a workflow like thisas shown here:

Explanation:

• In this workflow job1 and job2 are executed and finally an order is added for the jduSequenceReceiveOrder workflow jduSequenceReceiveOrder.
• The Boolean flag Remain When Terminated can be used to suppress the default behavior to make where an order is made to leave the workflow on completion. This does not change the order's behavior to process of processing the workflow and to make making its execution history available, it . It simply means that the order remains in a COMPLETED state and has to be manually forced to leave the workflow. The latter operation is available from the JS7 - Dashboard view and JS7 - Workflows view views.
• When adding an order then any arguments Arguments can be passed to this order that are the order being added. These have to be specified with the receiving workflow's variables (see the next chaptersection).
  • Individual arguments (names and values) can be added. Constant argument values can be used such as strings and numbers.
  • All variables of the current workflow can be added by using the Add All Arguments function.
  • If argument names of the calling workflow and of the receiving workflow do not match then arguments can be added like thisas follows:
    • Assume the calling workflow to use uses a variable booking_code and the receiving workflow to use uses a variable bookingCode. 
    • For the assignment use the argument name bookingCode with a value $booking_code.

...

The AddOrder Instruction can occur be located at any position in a workflow.

...

• 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.
• Uses can include the The AddOrder Instruction can be used within any other block instructions such as as JS7 - If Instruction, JS7 - Fork / -Join Instruction, etc.

Configuration of the receiving Workflow

The receiving workflow can be specified like thisas shown:

Explanation:

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

Resources

• JS7 - Notice Boards