Data generation or extract, provisioning, and entity reservation are implemented by creating and executing TDM tasks.
A TDM task is created in the TDM Portal. It holds a list of instructions and settings that define the data source, task actions, subset of processed entities and/or tables, the target environments and additional information. For example, extract 5 customers with small and medium business plans from Production and load them into the UAT target environment.
The actual data processing and/or entity reservation is performed by the task execution, where each task can be executed multiple times.
The following task actions are supported by TDM:
TDM 9.0 redesigns the task creation flow in order to simplify the task creation or edit and make it more intuitive. A graphic architectural widget guides the user on the task’s related component:
Source – defines the data source of task’s entities and/or tables. The data source can be either a source environment or a synthetic data generation.
Subset – defines the entities’ subset or the tables’ filter. For example, select 50 customers that live in NY and have a Gold status.
Test Data store – this is Fabric that can be used as a staging DB to save the task’s entities and/or tables.
Target – defines the target environment for the task, which can be either a testing environment or AI training to create a training model for an AI-based synthetic entities’ generation.
The task actions are set by components that are selected and set by the user. The Test Data Store must be set for all tasks.
Examples:
The user wishes to extract entities from Production and save them in the Test Data Store (Fabric) for a later use. The user needs to select the Source component:
The user wishes to extract entities from Production and load them into the UAT environment. The user needs to select both - Source and Target components:
The user can click on each one of the components to open its form and update its settings. The task also has Save task, Save & execute and Advanced settings icons.
The TDM Task List displays, by default, the list of all Active tasks in the TDM. It displays a list of settings on each task and these settings can also be used for filtering the displayed tasks.
The following screenshot shows an example of the Tasks window:
Click Show/Hide Columns to open a pop-up window, which displays the list of available fields for each task.
To display additional fields, click the fields.
To remove a field from the display, click the field.
To find a field, populate the Search box in order to filter the tasks by the searched value.
If the task has a description, an information icon is displayed next to the task name. Hover over the information icon to view the task description.
The TDM Portal displays a list of icons next to each task record:
When creating a new task or opening a task, the Task name form opens. Populating the Task name and Task description fields is optional. If no Task name is set, a default Task name is generated with some basic information about the task.
You can exit each form, including the Task name form, by clicking any task component. You can re-open the Task name form by clicking the Task name in the upper-left corner of the window.
Each task must include the Test Data Store (Fabric) and at least one environment: Source or Target. A task can include Source only, Target only, or both environments.
Click on each one of the components to open and update its form.
The Advanced settings include optional task settings:
The Save task icon saves the task in the TDM DB.
The Save & execute icon saves the task in the TDM DB and executes the task.
Data generation or extract, provisioning, and entity reservation are implemented by creating and executing TDM tasks.
A TDM task is created in the TDM Portal. It holds a list of instructions and settings that define the data source, task actions, subset of processed entities and/or tables, the target environments and additional information. For example, extract 5 customers with small and medium business plans from Production and load them into the UAT target environment.
The actual data processing and/or entity reservation is performed by the task execution, where each task can be executed multiple times.
The following task actions are supported by TDM:
TDM 9.0 redesigns the task creation flow in order to simplify the task creation or edit and make it more intuitive. A graphic architectural widget guides the user on the task’s related component:
Source – defines the data source of task’s entities and/or tables. The data source can be either a source environment or a synthetic data generation.
Subset – defines the entities’ subset or the tables’ filter. For example, select 50 customers that live in NY and have a Gold status.
Test Data store – this is Fabric that can be used as a staging DB to save the task’s entities and/or tables.
Target – defines the target environment for the task, which can be either a testing environment or AI training to create a training model for an AI-based synthetic entities’ generation.
The task actions are set by components that are selected and set by the user. The Test Data Store must be set for all tasks.
Examples:
The user wishes to extract entities from Production and save them in the Test Data Store (Fabric) for a later use. The user needs to select the Source component:
The user wishes to extract entities from Production and load them into the UAT environment. The user needs to select both - Source and Target components:
The user can click on each one of the components to open its form and update its settings. The task also has Save task, Save & execute and Advanced settings icons.
The TDM Task List displays, by default, the list of all Active tasks in the TDM. It displays a list of settings on each task and these settings can also be used for filtering the displayed tasks.
The following screenshot shows an example of the Tasks window:
Click Show/Hide Columns to open a pop-up window, which displays the list of available fields for each task.
To display additional fields, click the fields.
To remove a field from the display, click the field.
To find a field, populate the Search box in order to filter the tasks by the searched value.
If the task has a description, an information icon is displayed next to the task name. Hover over the information icon to view the task description.
The TDM Portal displays a list of icons next to each task record:
When creating a new task or opening a task, the Task name form opens. Populating the Task name and Task description fields is optional. If no Task name is set, a default Task name is generated with some basic information about the task.
You can exit each form, including the Task name form, by clicking any task component. You can re-open the Task name form by clicking the Task name in the upper-left corner of the window.
Each task must include the Test Data Store (Fabric) and at least one environment: Source or Target. A task can include Source only, Target only, or both environments.
Click on each one of the components to open and update its form.
The Advanced settings include optional task settings:
The Save task icon saves the task in the TDM DB.
The Save & execute icon saves the task in the TDM DB and executes the task.