Introduction

There can be situations when a given workflow should be processed by a single order only. Any additional orders should wait for the first order to complete and to leave the workflow. This mechanism is called order serialization.

Order serialization is different from job parallelism

• Job parallelism applies to the number of instances of a job that are executed by parallel orders.
  • For example, if a workflow includes a number of jobs for which parallelism is limited to 1 task then the following applies:
    • With 3 orders entering the workflow the first order will execute job1. The remaining orders wait in front of job1.
    • With job1 being processed then order1 moves on and starts to process job2.
    • At the same time order2 will start to process job1.
    • With job1 being processed then order2 to moves to process job2 and order3 starts to process job1.
  • This means that job parallelism allows any number of orders to be active in a workflow. It limits the number of orders that execute a job in parallel.
• Order serialization is intended to make any additional orders wait for a previous order to complete the workflow before entering the workflow.

Use of Lock Instruction

The Lock Instruction in this example is used to prevent any additional orders from entering a workflow:

• A Resource Lock is used that limits parallel

x

Use of Options Instruction and Lock Instruction