Task Execution

A task can be executed multiple times. A Task Execution process can be initiated either from the TDM Portal by clicking , a direct call to the start of a task execution API, or via a TDM Scheduling process in case 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.

Who Can Execute a Task via the TDM Portal?

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.
  • Generate tasks - the environment owner of the Synthetic environment.
  • Load, Reserve, or Delete tasks - the environment owner of the target environment.

• Testers:

  • The task's creator.
  • Other testers that are related to the same TDM Environment permission set as the task's creator:
  • For Load, Reserve, or Delete tasks - testers that are related to the same TDM Environment permission set in the target environment as the task's creator.
  • For Extract and Generate tasks - testers that are related to the same TDM Environment permission set in the source environment as the task's creator.

Task Execution Order

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:

1. 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.

2. 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 or synthetic entities generation.

   Click for more information about the execution order of hierarchical LUs.

3. 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.

Monitoring Task Execution

The TDM Portal displays a list of the task's LUs and pre and post-execution processes, as well as the status of the currently running processes.

Example 1 - Horizontal Execution:

• Execute and extract the task with the following LUs:

  • Customer - the root LU.
  • Billing - this is the children LU of the Customer LU.

• The Customer LU is executed before the Billing LU:

  

• The Billing LU is executed after the execution of the Customer LU has ended:

  

  Example 2 - Vertical Execution:

  • Execute and extract the task with the following LUs:

  • Customer - the root LU.

  • Billing - this is the children LU of the Customer LU.

  • The Customer LU is displayed as this is the root LU. The related Billing entities are executed behind the scenes for each executed customer before moving to the next customer ID. Both LUs are marked as running:

  

• The Logical Units Execution Summary window displays the execution summary details of each LU, pre-execution processes and post-execution processes.

Open the Batch Monitoring Window

Click the information icon next to each LU to open the Batch Monitor window for the execution in order to get additional information as well as better tracking of the task execution.

Stop and Resume a Task Execution

A task can be stopped if the processed entities fail due to an error; the task 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 with a stopped execution status in the Logical Unit Summary to resume the execution of all stopped task's LUs and post-execution processes.

Set a Task Execution to be On Hold

Occasionally, you may need to temporarily hold a task (i.e., set it 'On Hold'). This status can be used - for example, if the testing environment is temporarily down - for holding all task executions on an environment until the testing environment is up again, and to then reactivate the tasks for this environment.

The 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 on a Hold task-execution-status, cannot be executed.

The Hold and Activate task buttons are displayed on the Tasks screen of each task:

• To hold a task (i.e., set it '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 Portal and the TDM Scheduling process 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 tasks that are 'On Hold'.