Knowledge Base Academy Community My Tickets
Fabric 8.4
Fabric 8.4 Fabric 8.3 Fabric 8.2 Fabric 8.1 Fabric 8.0 Fabric 7.2 Fabric 7.1 Fabric 7.0 Fabric 6.5

Task Execution - Overriding Parameters

A task execution can override execution parameters by:

  • setting the active environment based on the task's environments.
  • setting key-value parameters on a session level.
  • overriding Globals' values on a session level.
  • overriding the Sync Mode of the task execution.
  • overriding additional execution parameters without changing the task itself.

Setting Active Environments

Extract Tasks

The task execution process sets the task's environment as the active environment on the executed task.

Load Tasks

The task execution process sets the active environment as follows:

  1. It first sets the task's source environment as the active environment and gets the LUI from Fabric.
  2. After the LUI sync, it sets the task's target environment as the active environment and runs the delete and/or load flows on the target environment.

Overriding Globals' Values

A project's Global can be overridden on either a TDM environment or a TDM task level.

The task execution process sets the values on the Globals on a session level.

Note: Task-level variables have a higher priority than TDM environment-level variables. That is, if a variable (Global) is set on both - the task and the related environment levels - the task's Global value gets the higher priority.

Overriding the Sync Mode on the Task Execution

When executing a TDM task, set the Sync mode according to the following table:

Source env -  Override Sync Mode

Task - Source env - policy for fetching data

Execution Sync Mode

Results

Empty
  • Available data from the Test data store, new data from <source env> 

On

LUIs are synced according to their sync method. See the Sync Behavior Summary table.

Empty
  • All data from <source env>

Force

LUIs are synced from the source.

Empty
  • Available <source env> data in the Test data store 
  • Selected snapshot (version) 

If the task includes a delete => On

Else => Off
  • If this is the first sync, return an error.
  • If the LUIs exist in Fabric:
    • Source LU tables:
      • Get the data from Fabric.
    • Target LU tables (populated for a delete activity):
      • Sync the data from the target environment.

Always sync
  • Available data from the Test data store, new data from <source env> 

Force

LUIs are synced from the source.

Always sync
  • All data from <source env>

Force

LUIs are synced from the source.

Do Not Sync
  • Only the following options are available in the task:
    • Available <source env> data in the Test data store 
    • Selected snapshot (version) 

If the task includes a delete => On

Else => Off
  • If this is the first sync, return an error.
  • If the LUIs exist in Fabric:
    • Source LU tables:
      • Get the data from Fabric.
    • Target LU tables:
      • Sync the data from the target environment.

Overriding Additional Task Execution Parameters

The TDM API that starts a task execution can get a list of parameter-value pairs to override the original values of these parameters on the task execution without changing the task data.

This way, various users can use a task as a template and change (override) the execution parameters without changing the task itself: Each user can run the task on their environment and update the execution parameter according to their needs.

Click here for the list of task attributes that can be overridden at runtime.

Task Execution Process

Overriding task execution parameters does not update the task itself, but rather impacts the given task execution:

The task execution process gets the overridden parameters from task_execution_override_attrs TDM DB table and executes the task based on the overridden parameters.

Previous

Task Execution - Overriding Parameters

A task execution can override execution parameters by:

  • setting the active environment based on the task's environments.
  • setting key-value parameters on a session level.
  • overriding Globals' values on a session level.
  • overriding the Sync Mode of the task execution.
  • overriding additional execution parameters without changing the task itself.

Setting Active Environments

Extract Tasks

The task execution process sets the task's environment as the active environment on the executed task.

Load Tasks

The task execution process sets the active environment as follows:

  1. It first sets the task's source environment as the active environment and gets the LUI from Fabric.
  2. After the LUI sync, it sets the task's target environment as the active environment and runs the delete and/or load flows on the target environment.

Overriding Globals' Values

A project's Global can be overridden on either a TDM environment or a TDM task level.

The task execution process sets the values on the Globals on a session level.

Note: Task-level variables have a higher priority than TDM environment-level variables. That is, if a variable (Global) is set on both - the task and the related environment levels - the task's Global value gets the higher priority.

Overriding the Sync Mode on the Task Execution

When executing a TDM task, set the Sync mode according to the following table:

Source env -  Override Sync Mode

Task - Source env - policy for fetching data

Execution Sync Mode

Results

Empty
  • Available data from the Test data store, new data from <source env> 

On

LUIs are synced according to their sync method. See the Sync Behavior Summary table.

Empty
  • All data from <source env>

Force

LUIs are synced from the source.

Empty
  • Available <source env> data in the Test data store 
  • Selected snapshot (version) 

If the task includes a delete => On

Else => Off
  • If this is the first sync, return an error.
  • If the LUIs exist in Fabric:
    • Source LU tables:
      • Get the data from Fabric.
    • Target LU tables (populated for a delete activity):
      • Sync the data from the target environment.

Always sync
  • Available data from the Test data store, new data from <source env> 

Force

LUIs are synced from the source.

Always sync
  • All data from <source env>

Force

LUIs are synced from the source.

Do Not Sync
  • Only the following options are available in the task:
    • Available <source env> data in the Test data store 
    • Selected snapshot (version) 

If the task includes a delete => On

Else => Off
  • If this is the first sync, return an error.
  • If the LUIs exist in Fabric:
    • Source LU tables:
      • Get the data from Fabric.
    • Target LU tables:
      • Sync the data from the target environment.

Overriding Additional Task Execution Parameters

The TDM API that starts a task execution can get a list of parameter-value pairs to override the original values of these parameters on the task execution without changing the task data.

This way, various users can use a task as a template and change (override) the execution parameters without changing the task itself: Each user can run the task on their environment and update the execution parameter according to their needs.

Click here for the list of task attributes that can be overridden at runtime.

Task Execution Process

Overriding task execution parameters does not update the task itself, but rather impacts the given task execution:

The task execution process gets the overridden parameters from task_execution_override_attrs TDM DB table and executes the task based on the overridden parameters.

Previous

© Copyright 2026 K2VIEW