Skip to end of metadata
Go to start of metadata

Use of Orders

  • Orders are triggers that will cause a job chain to start. Jobs can be started by calendar events, file events and by programmatically created events.
  • Orders can be used with parameters that allow the same job chain to be used with different parameter sets.
  • Workflows are regulated by orders. An order can be thought of as a directive that is processed in a chain of jobs. An order is assigned to a job chain with an identifier which is valid for that particular job chain. The order also has a status that changes after the processing of each job node and can have a payload of parameters.
  • Orders are persistently stored during processing. If a job, job chain or order is stopped during processing and then restarted, it will be continued at exactly the point where it was stopped.

Read more on the features of Order objects in the order and job chain documentation.

Order Processing Patterns

Job chain with multiple orders and multiple start times

  • Three orders start the same job chain at different points in time:
    • Order 1 includes two start times for workdays.
    • Order 2 starts on Saturday.
    • Order 3 starts on Sunday.
  • Order 1 and 2 start the job chain at its beginning, order 3 starts the job chain with Job 2.
  • Each order carries a different parameter set for the jobs of the job chain.



Job chain with multiple orders executing in parallel

  • Three orders are executed in the same job chain at the same point in time:
    • Order 1 and Order 2 are executing the same job node 2. 
    • Job 2 is therefore executed in two independent tasks for each order.
    • Order 3 is executing job node 3.
  • Each order carries a different parameter set for the jobs of the job chain.