- 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 objects in the order and job chain documentation.