Task Execution
A task can be executed multiple times by either clicking 
or via a TDM scheduling process if the task's Execution Timing is defined as Scheduled Execution.
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.
Who Can Execute a Task?
The following users can execute a TDM task:
- Admin users.
- Environment owners of the task's environment:
- Extract tasks, the environment owner of the source environment.
- Load tasks, the environment owner of the target environment.
- Testers:
- The task's creator.
- Other testers that are related to the same role as the task's creator:
- Load tasks, testers that are related to the same role in the target environment as the task's creator.
- Extract tasks, testers that are related to the same role in the source environment as the task's creator.
Task Execution Order
A TDM task can include multiple LUs with a flat or hierarchical structure and post execution processes.
The execution of the related task components runs in the following order:
LUs, run the LUs from parent to child.
Click for more information about the execution order of hierarchical LUs.
Post Execution Processes, run the post execution processes 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.
Monitoring Task Execution
The TDM GUI displays a list of the task's LUs and post execution processes and the status of the currently running processes.
Example:
Execute and extract the task with the following LUs:
- Customer, the root LU.
- Billing and Orders, the children LUs of the Customer LU.
The Customer LU is executed before the Billing and Orders LUs:
The Billing and Orders LUs are executed after the execution of the Customer LU has ended:
The Logical Units Execution Summary window displays the summary execution details of each LU or post execution process:
Stop and Resume a Task Execution
A task can be stopped if the processed entities fail due to an error and can be resumed from the same point once the error has been fixed.
Click
in the right corner of the Running Execution window to stop the execution of the running or pending task's LUs or post execution processes and to set the status of the task to stopped.Click
next to a record in stopped execution status in the Logical Unit Summary to resume the execution of all stopped task LUs and post execution processes:
Holding Task Execution
Occasionally you may need to temporarily set a task to on-hold. For example, if the testing environment is temporarily down, to hold all task executions on an environment until the testing environment is up again and to then reactivate the tasks for this environment.
Hold or Activate task activities are enabled only for Active tasks. When a task is deleted (set to Inactive), its task execution status cannot be modified.
Tasks with an on-Hold task execution status cannot be executed.
Hold and Activate task buttons are displayed on the Tasks screen of each task:
- To set the task to on-hold (pause), click
. - To activate a task execution status, click
.
Who Can Hold or Activate a Task?
- Admin user, can hold or activate all active tasks.
- Environment owner user, can hold or activate all active tasks in their environment.
- Testers, can hold or activate their active tasks.
Notes:
To execute a scheduled task on demand, click
. Both the TDM GUI and TDM Scheduling processes initiate an execution request in the TDM DB. The TDM task execution process gets pending execution requests and executes the tasks.
Click for more information about the TDM task execution process.
A task cannot be executed several times in parallel. An additional execution can be initiated only if the previous execution has ended.
The TDM Scheduling process skips running tasks.
The TDM Scheduling process skips on-hold tasks.
Task Execution
A task can be executed multiple times by either clicking or via a TDM scheduling process if the task's Execution Timing is defined as Scheduled Execution.
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.
Who Can Execute a Task?
The following users can execute a TDM task:
- Admin users.
- Environment owners of the task's environment:
- Extract tasks, the environment owner of the source environment.
- Load tasks, the environment owner of the target environment.
- Testers:
- The task's creator.
- Other testers that are related to the same role as the task's creator:
- Load tasks, testers that are related to the same role in the target environment as the task's creator.
- Extract tasks, testers that are related to the same role in the source environment as the task's creator.
Task Execution Order
A TDM task can include multiple LUs with a flat or hierarchical structure and post execution processes.
The execution of the related task components runs in the following order:
LUs, run the LUs from parent to child.
Click for more information about the execution order of hierarchical LUs.
Post Execution Processes, run the post execution processes 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.
Monitoring Task Execution
The TDM GUI displays a list of the task's LUs and post execution processes and the status of the currently running processes.
Example:
Execute and extract the task with the following LUs:
- Customer, the root LU.
- Billing and Orders, the children LUs of the Customer LU.
The Customer LU is executed before the Billing and Orders LUs:
The Billing and Orders LUs are executed after the execution of the Customer LU has ended:
The Logical Units Execution Summary window displays the summary execution details of each LU or post execution process:
Stop and Resume a Task Execution
A task can be stopped if the processed entities fail due to an error and can be resumed from the same point once the error has been fixed.
Click
in the right corner of the Running Execution window to stop the execution of the running or pending task's LUs or post execution processes and to set the status of the task to stopped.Click
next to a record in stopped execution status in the Logical Unit Summary to resume the execution of all stopped task LUs and post execution processes:
Holding Task Execution
Occasionally you may need to temporarily set a task to on-hold. For example, if the testing environment is temporarily down, to hold all task executions on an environment until the testing environment is up again and to then reactivate the tasks for this environment.
Hold or Activate task activities are enabled only for Active tasks. When a task is deleted (set to Inactive), its task execution status cannot be modified.
Tasks with an on-Hold task execution status cannot be executed.
Hold and Activate task buttons are displayed on the Tasks screen of each task:
- To set the task to on-hold (pause), click .
- To activate a task execution status, click .
Who Can Hold or Activate a Task?
- Admin user, can hold or activate all active tasks.
- Environment owner user, can hold or activate all active tasks in their environment.
- Testers, can hold or activate their active tasks.
Notes:
To execute a scheduled task on demand, click
. Both the TDM GUI and TDM Scheduling processes initiate an execution request in the TDM DB. The TDM task execution process gets pending execution requests and executes the tasks.
Click for more information about the TDM task execution process.
A task cannot be executed several times in parallel. An additional execution can be initiated only if the previous execution has ended.
The TDM Scheduling process skips running tasks.
The TDM Scheduling process skips on-hold tasks.
