Page History

...

Explanation:

• In this workflow job1 and job2 are executed and finally an order is added for workflow jduSequenceReceiveOrder.
• The Boolean flag Remain When Terminated can be used to suppress the default behavior to make an order leave the workflow on completion. This does not change the order's behavior to process the workflow and to make its execution history available, 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.
• When adding an order then any arguments can be passed to this order that are specified with the receiving workflow's variables (see next chapter).
  • 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 this:
    • Assume the calling workflow to use a variable booking_code and the receiving workflow to use a variable bookingCode. 
    • For the assignment use the argument name bookingCode with a value $booking_code.

...

• 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 instructions such as JS7 - If Instruction, JS7 - Fork / Join Instruction etc.

...

The receiving workflow can be specified like this:

Explanation:

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

...