You can use tasks to set up the execution of:
Name | Responsible | Description |
---|---|---|
Create task |
Application Consultant |
You can use tasks to set up the execution of:
|
Add message to tasks |
Application Consultant |
For each task, you can define several messages. If you run a task, all defined messages are run. |
Add web service action to task |
Application Consultant |
For each task, you can define several outbound web service actions. If you run a task, all defined outbound web service actions are run. |
Add batch class to task |
Application Consultant |
For each task, you can define several (custom) batch classes. If you run a task, all defined batch classes are run. |
Add master data entity to task |
Application Consultant |
For each task, you can define several master data entities. If you run a task, all defined master data entities are run. For more information on master data entities, refer to Master data management studio. |
Define task dependencies |
Application Consultant |
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:
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. |