Task Execution
A task can be executed multiple times. The Task Execution process can be initiated by either by the task execution window, by calling the start task execution API, or by the TDM scheduling process if the task's scheduler is defined.
The TDM Scheduling process checks the End Date of the task's scheduling parameters. If the End Date is earlier than the current date, the process cleans the task's Scheduled Execution parameters and skips the task execution.
A task cannot be executed several times in parallel with the same execution attributes. An additional execution can be initiated only if the previous execution has ended.
Task Execution Order
Entity-based Task
A TDM task can include multiple LUs with either a flat or hierarchical structure, and post-execution processes.
The execution of the related task's components runs in the following order:
Pre-execution processes, if they are added to the task. The pre-execution processes are executed according to their execution order as defined in the task's BE.
LUs - the execution order depends on the task's execution mode:
- Horizontal execution - execution of the task LU by LU from parent to child, where all entities are processed in one LU before moving on to the next system in the hierarchy.
- Vertical execution - execution of the entire LU hierarchy for each root entity before moving on to the next root entity. Note that this mode is not available for a task that generates entity clones and for synthetic entities generation.
Click for more information about the execution order of hierarchical LUs.
Post-execution processes, if they are added to the task. The post-execution processes run after the execution of the LUs ends. The post-execution processes are executed according to their execution order as defined in the task's BE.
Table-based Task
e execution of the related task's components runs in the following order:
Pre-execution processes, if they are added to the task. The pre-execution processes are executed according to their execution order as defined in the TDM implementation.
Post-execution processes, if they are added to the task. The post-execution processes run after the execution of the tables ends. The post-execution processes are executed according to their execution order as defined in the TDM implementation.
Monitoring Task Execution
The TDM App displays the task execution process.
Click for more information about the task execution monitoring.
Disabled Tasks
A Task that contains disabled systems on its source and/or target environments, cannot be executed. In such case, these tasks are displayed for view only in the Task Management window, but cannot be executed.
Task Execution
A task can be executed multiple times. The Task Execution process can be initiated by either by the task execution window, by calling the start task execution API, or by the TDM scheduling process if the task's scheduler is defined.
The TDM Scheduling process checks the End Date of the task's scheduling parameters. If the End Date is earlier than the current date, the process cleans the task's Scheduled Execution parameters and skips the task execution.
A task cannot be executed several times in parallel with the same execution attributes. An additional execution can be initiated only if the previous execution has ended.
Task Execution Order
Entity-based Task
A TDM task can include multiple LUs with either a flat or hierarchical structure, and post-execution processes.
The execution of the related task's components runs in the following order:
Pre-execution processes, if they are added to the task. The pre-execution processes are executed according to their execution order as defined in the task's BE.
LUs - the execution order depends on the task's execution mode:
- Horizontal execution - execution of the task LU by LU from parent to child, where all entities are processed in one LU before moving on to the next system in the hierarchy.
- Vertical execution - execution of the entire LU hierarchy for each root entity before moving on to the next root entity. Note that this mode is not available for a task that generates entity clones and for synthetic entities generation.
Click for more information about the execution order of hierarchical LUs.
Post-execution processes, if they are added to the task. The post-execution processes run after the execution of the LUs ends. The post-execution processes are executed according to their execution order as defined in the task's BE.
Table-based Task
e execution of the related task's components runs in the following order:
Pre-execution processes, if they are added to the task. The pre-execution processes are executed according to their execution order as defined in the TDM implementation.
Post-execution processes, if they are added to the task. The post-execution processes run after the execution of the tables ends. The post-execution processes are executed according to their execution order as defined in the TDM implementation.
Monitoring Task Execution
The TDM App displays the task execution process.
Click for more information about the task execution monitoring.
Disabled Tasks
A Task that contains disabled systems on its source and/or target environments, cannot be executed. In such case, these tasks are displayed for view only in the Task Management window, but cannot be executed.
