Environment Window - General Information
The General Information section in the Environment window holds the following information:
Environment Name
Mandatory setting.
Populate the following setting:
- TDM Environment Name - select the environments deployed to Fabric from the drop-down list.
Environment - Additional Information
Optional settings:
- Description
- Contact person setting
Environment Type
Mandatory setting.
Set the environment type to one of the following:
Source - this can only be defined as a source environment in a TDM task. For example, in a Production environment - a TDM task can extract entities but cannot insert entities.
Target - this environment can only be used as a target environment in a TDM task.
Both - this environment can be used as both the source environment and the target environment in a TDM task. This mode is useful for Data Versioning tasks.
Example:
- A tester backs up data in a testing environment before running functional tests by creating a data snapshot on the testing environment. The testing environment is set as a source environment. During the execution of the task, data is saved in the Test Data Store.
- During functional tests, the data in the testing environment becomes corrupt and needs to be replaced with the most recent backed-up version created in the testing environment. The tester creates a task to re-load the data snapshot (version) and sets the testing environment to be both source and target.
Override Sync Mode
Optional setting.
The Override mode can be set if the Environment Type is either Source or Both. This setting overrides the default Fabric Sync mode when extracting the selected entities from the source environment, and sets another Sync mode that can be overridden on both the environment and the task levels.
The following values can be set in the Override Sync Mode:
Do not Sync
Do not sync the entities from the source when running a TDM task with the environment as a source; instead, get the entities from Fabric. Note that if the entities do not exist in Fabric, the task's execution will return an error. This mode is required when access to the source environment has been limited by the organization.
Example:
- The Production team allocates a predefined window for extracting a subset of entities from Production. The access to Production is restricted to the predefined window in which a large subset can be extracted and saved into the Test Data Store (Fabric).
- The Override Sync Mode in the Production TDM environment must be set to Do not Sync, thus preventing additional access to Production. Other TDM tasks in the Production source environment get data entities from Fabric.
Always Sync
Always sync the entities from the source when running a TDM task with the environment as a source.
Click for more information on how overriding the sync mode impacts the task execution process.
Mask Sensitive Data
This checkbox, added by TDM 8.1, is displayed on any environment that can be used as a source environment (the environment type is Source or Both). When checked, this checkbox indicates that the environment contains sensitive data and it should therefore be masked before it is saved into Fabric.
Note: It is recommended to clear the Mask Sensitive Data checkbox in the Synthetic and AI environments in order to ensure that the data generation parameters, that are set by the user in the data generation task and that refer to PII fields, are not overridden by the Masking Actors in the LU populations.
Environment Owners
- Admin users can add or remove one or several environment owner users or user groups (Fabric roles) to/from an environment. An environment owner user or group can be added to several environments.
- Adding a user group to an environment enables the users that belong to the group to be the owners of the environment.
- An environment owner user or group can be attached to an environment with tester permissions. For example, a user is attached to ENV1 as the environment owner and is attached to ENV2 as a tester.
- The environment owner can edit an environment except for adding or removing environment owner users. Only Admin users can add or remove environment owners.
- The environment owner can create and execute TDM tasks on their environment without limitations, unlike tester users who can define a task on an environment based on their permissions.
Click for more information about environment permissions.
Click for more information about the Owner TDM Permission Group.
How Do I Add or Remove Environment Owners to/from an Environment?
Adding Environment Owners
Click the plus icon next to the Environment Owners setting.
A pop-up window opens:
Deleting Environment Owners
Click the X on an environment owner username(s) to remove it from the environment.
Note: Always click Save Changes after editing the General Information section in the Environment window.
Environment Window - General Information
The General Information section in the Environment window holds the following information:
Environment Name
Mandatory setting.
Populate the following setting:
- TDM Environment Name - select the environments deployed to Fabric from the drop-down list.
Environment - Additional Information
Optional settings:
- Description
- Contact person setting
Environment Type
Mandatory setting.
Set the environment type to one of the following:
Source - this can only be defined as a source environment in a TDM task. For example, in a Production environment - a TDM task can extract entities but cannot insert entities.
Target - this environment can only be used as a target environment in a TDM task.
Both - this environment can be used as both the source environment and the target environment in a TDM task. This mode is useful for Data Versioning tasks.
Example:
- A tester backs up data in a testing environment before running functional tests by creating a data snapshot on the testing environment. The testing environment is set as a source environment. During the execution of the task, data is saved in the Test Data Store.
- During functional tests, the data in the testing environment becomes corrupt and needs to be replaced with the most recent backed-up version created in the testing environment. The tester creates a task to re-load the data snapshot (version) and sets the testing environment to be both source and target.
Override Sync Mode
Optional setting.
The Override mode can be set if the Environment Type is either Source or Both. This setting overrides the default Fabric Sync mode when extracting the selected entities from the source environment, and sets another Sync mode that can be overridden on both the environment and the task levels.
The following values can be set in the Override Sync Mode:
Do not Sync
Do not sync the entities from the source when running a TDM task with the environment as a source; instead, get the entities from Fabric. Note that if the entities do not exist in Fabric, the task's execution will return an error. This mode is required when access to the source environment has been limited by the organization.
Example:
- The Production team allocates a predefined window for extracting a subset of entities from Production. The access to Production is restricted to the predefined window in which a large subset can be extracted and saved into the Test Data Store (Fabric).
- The Override Sync Mode in the Production TDM environment must be set to Do not Sync, thus preventing additional access to Production. Other TDM tasks in the Production source environment get data entities from Fabric.
Always Sync
Always sync the entities from the source when running a TDM task with the environment as a source.
Click for more information on how overriding the sync mode impacts the task execution process.
Mask Sensitive Data
This checkbox, added by TDM 8.1, is displayed on any environment that can be used as a source environment (the environment type is Source or Both). When checked, this checkbox indicates that the environment contains sensitive data and it should therefore be masked before it is saved into Fabric.
Note: It is recommended to clear the Mask Sensitive Data checkbox in the Synthetic and AI environments in order to ensure that the data generation parameters, that are set by the user in the data generation task and that refer to PII fields, are not overridden by the Masking Actors in the LU populations.
Environment Owners
- Admin users can add or remove one or several environment owner users or user groups (Fabric roles) to/from an environment. An environment owner user or group can be added to several environments.
- Adding a user group to an environment enables the users that belong to the group to be the owners of the environment.
- An environment owner user or group can be attached to an environment with tester permissions. For example, a user is attached to ENV1 as the environment owner and is attached to ENV2 as a tester.
- The environment owner can edit an environment except for adding or removing environment owner users. Only Admin users can add or remove environment owners.
- The environment owner can create and execute TDM tasks on their environment without limitations, unlike tester users who can define a task on an environment based on their permissions.
Click for more information about environment permissions.
Click for more information about the Owner TDM Permission Group.
How Do I Add or Remove Environment Owners to/from an Environment?
Adding Environment Owners
Click the plus icon next to the Environment Owners setting.
A pop-up window opens:
Deleting Environment Owners
Click the X on an environment owner username(s) to remove it from the environment.
Note: Always click Save Changes after editing the General Information section in the Environment window.
