Transform Execution & Data Flow
Each integration is made up of one or more transforms which are executed in their specified order sequence.
Data is processed in batches, which are transformed sequentially.
When one transform completes, the resultant dataset becomes the input for the next transform in the sequence. In this way, all integration instances (i.e. transforms) are treated by IMan as autonomous units.
It is important to note that although IMan can run multiple batches of data through the transforms of an integration concurrently, these transforms are working independently of each other.
Priority
Parent transforms that have more than one output, require that a priority is set to tell IMan in which order to process the child transforms.
The transform priority drop down is displayed only when the parent transform in use has more than one output.
The priority sets the order in which the child transforms are executed.
If the priority of a transform is changed, the transforms related to it automatically adjust accordingly.
Example
In a sales order import from an external web system, the customer records and sales orders are both needed. However, the accounting system would need the customer records to be imported first, before it can record the sales orders.
In this situation the output for the customer records could be set as '1', while the sales orders could be '2'.
