If a task depends on one or more other tasks, define the dependencies. So, the task is not done before the other tasks are done. The dependencies are only taken into account if you run a project.
You can use task dependencies to schedule data import or export in batch. The main reasons to use task dependencies are:
  • Sequence of data: For data migrations or in complex integration scenarios, often it is required that data is imported in a specific sequence.
  • Performance: Tasks that are scheduled at the same level, can be processed in parallel. This improves the performance of the data import or export. Also, the messages, as defined for a task, are run in parallel.
Before you set up the task dependencies, define data levels for the data to be imported or exported. You can do so, for example, in Microsoft Excel.
For each data level, you can set up one or more tasks.
To define the level of a task, add a dependency to a task of the applicable previous level. As a result, the task level is automatically assigned. For example, if you add a dependency to a level '2' task, automatically, level '3' is assigned to the current task.
To each task, assign the messages that process the data for the task. You can group messages in tasks as desired.
The next picture gives an example of a data migration project. The project is run using the defined task dependencies. As a result, the data is migrated in the required sequence and with a better performance.

Example: A sales order can only be imported if the related customer and item are already available. So, the customer and item must be imported first. In the previous picture, the customer is imported in level 2 and the item in level 3. This is done before the sales order header is imported in level 4 and the sales order line in level 5.


Standard procedure

1. Click Connectivity studio Integration Design.
2. Click Tasks.
3. In the list, find and select the desired task.
4. Expand the Dependencies section.
5. Click New.
6. In the Dependent on task field, enter or select a task.
 

Note: You can only add tasks that belong to the same project as the current task.

7. For each task dependency, set the applicable condition. You can choose from these conditions:
- Ended or Error: The current task is always run when the 'dependent-on' task is finished. This is the default condition.
- Ended: The current task is run only if the 'dependent-on' task is finished without an error.
- Error: The current task is run only if the 'dependent-on' task is finished with an error.
  In the Expected status field, select an option.
8. Close the page.
9. Close the page.

See also

Provide feedback