TDM Data Flux Tasks

Data Flux mode enables saving backup versions of data during Functional tests and to then reload the latest saved version to the target environment if it becomes corrupted. Once created, an extract task can be executed multiple times to create different backup versions where each version is saved in Fabric.

This functionality is useful when running a complex testing calendar in a testing environment. Backing up data every X steps or every X times enables testers to reload the latest version to their environment and repair data without returning to the original state and losing their updates.

Note that the testing environment is often used as a source and target environment for Data Flux tasks. Therefore, the Environment Type must be set to Both to enable Data Flux in an environment.

How do I Create a Data Flux Task?

Go to the Task window, select General tab and then check Entity Versioning.

Who Can Create a Data Flux Task?

The following users can create a Data Flux task:

  1. Admin users.
  2. Environment owner users who can create a Data Flux task for their environment.
  3. Testers who can create a TDM task for environments with Entity Versioning permissions that are attached to their TDM Environment role.

TDM Task Types and Modes - Summary Table

Task Type

Entity Versioning

Description

Extract

true

Extract the data of the selected entities from the source environment and save it as a separate version in Fabric.

The extracted data gets the execution datetime. Each entity gets the following Instance ID in Fabric:

<Source env name>_<entity id>_<task title>_<datetime>

For example, ENV1_100_extractTest3_20210218082453

Since the execution datetime is concatenated to the LUI, each task execution creates a different set of LUIs. 

Extract

false

Extract the data of the selected entities from the source environment and save it in Fabric.

Each entity is saved in Fabric with the following instance ID:

<Source env name>_<entity id>

For example, ENV1_100.

Note that each task execution may update the LUIs in Fabric.

Load

true

Load a selected version created on the task's LUs and source environment into the selected target environment. The required entities are deleted from the target and reloaded according to the selected version.

Load

false

Regular TDM load task.  Get a list of entities from a source environment and copy them into the target environment.

Previous

TDM Data Flux Tasks

Data Flux mode enables saving backup versions of data during Functional tests and to then reload the latest saved version to the target environment if it becomes corrupted. Once created, an extract task can be executed multiple times to create different backup versions where each version is saved in Fabric.

This functionality is useful when running a complex testing calendar in a testing environment. Backing up data every X steps or every X times enables testers to reload the latest version to their environment and repair data without returning to the original state and losing their updates.

Note that the testing environment is often used as a source and target environment for Data Flux tasks. Therefore, the Environment Type must be set to Both to enable Data Flux in an environment.

How do I Create a Data Flux Task?

Go to the Task window, select General tab and then check Entity Versioning.

Who Can Create a Data Flux Task?

The following users can create a Data Flux task:

  1. Admin users.
  2. Environment owner users who can create a Data Flux task for their environment.
  3. Testers who can create a TDM task for environments with Entity Versioning permissions that are attached to their TDM Environment role.

TDM Task Types and Modes - Summary Table

Task Type

Entity Versioning

Description

Extract

true

Extract the data of the selected entities from the source environment and save it as a separate version in Fabric.

The extracted data gets the execution datetime. Each entity gets the following Instance ID in Fabric:

<Source env name>_<entity id>_<task title>_<datetime>

For example, ENV1_100_extractTest3_20210218082453

Since the execution datetime is concatenated to the LUI, each task execution creates a different set of LUIs. 

Extract

false

Extract the data of the selected entities from the source environment and save it in Fabric.

Each entity is saved in Fabric with the following instance ID:

<Source env name>_<entity id>

For example, ENV1_100.

Note that each task execution may update the LUIs in Fabric.

Load

true

Load a selected version created on the task's LUs and source environment into the selected target environment. The required entities are deleted from the target and reloaded according to the selected version.

Load

false

Regular TDM load task.  Get a list of entities from a source environment and copy them into the target environment.

Previous