TDM settings are saved in the TDM PostgreSQL DB.
TDM tasks update the following TDM DB tables:
This table holds all TDM tasks defined in the TDM Portal.
A new record is created for each task.
Each task record gets a unique task_id sequence which is the table's PK.
### Task Status
task_status: each task is created in Active task_status. Deleted tasks have an Inactive task_status and are not physically deleted from this table.
task_execution_status:
selection method: populated based on the selection method in the Requested Entities tab. This column can be populated by either:
selection_param_value: populated when the task selection method is either Entity List, Parameters, Custom Logic or Entity Clone:
This column is used by the TDM task execution process to create the entities list of the root LUs for each task.
### Data Versioning Parameters
version_ind - populated by true in a Data Versioning task.
selected_version_task_name, selected_version_datetime, and selected_version_task_exe_id - the selected entities when creating a load Data Versioning task to reload a selected version of entities into the target environment.
selected_ref_version_task_name, selected_ref_version_datetime, and selected_ref_version_task_exe_id - the selected Reference's version when creating a Data Versioning task to copy a selected version of Reference tables into the target environment.
source_env_name
source_environment_id
This table holds the LUs list of each task. A separate record is created for each LU.
This table holds a task's post execution processes. A new record is created for each post execution process.
This table holds the following columns:
This table holds all variables that are overridden by the task. A separate record is created for each variable.
This table holds a list of the task's Reference tables. A separate record is created for each Reference table.
TDM settings are saved in the TDM PostgreSQL DB.
TDM tasks update the following TDM DB tables:
This table holds all TDM tasks defined in the TDM Portal.
A new record is created for each task.
Each task record gets a unique task_id sequence which is the table's PK.
### Task Status
task_status: each task is created in Active task_status. Deleted tasks have an Inactive task_status and are not physically deleted from this table.
task_execution_status:
selection method: populated based on the selection method in the Requested Entities tab. This column can be populated by either:
selection_param_value: populated when the task selection method is either Entity List, Parameters, Custom Logic or Entity Clone:
This column is used by the TDM task execution process to create the entities list of the root LUs for each task.
### Data Versioning Parameters
version_ind - populated by true in a Data Versioning task.
selected_version_task_name, selected_version_datetime, and selected_version_task_exe_id - the selected entities when creating a load Data Versioning task to reload a selected version of entities into the target environment.
selected_ref_version_task_name, selected_ref_version_datetime, and selected_ref_version_task_exe_id - the selected Reference's version when creating a Data Versioning task to copy a selected version of Reference tables into the target environment.
source_env_name
source_environment_id
This table holds the LUs list of each task. A separate record is created for each LU.
This table holds a task's post execution processes. A new record is created for each post execution process.
This table holds the following columns:
This table holds all variables that are overridden by the task. A separate record is created for each variable.
This table holds a list of the task's Reference tables. A separate record is created for each Reference table.