A Load task contains the Load task type and loads (provisions) the task's entities and/or Reference tables to the target environment. A load task can also delete entities from target environments before loading them and/or reserve the target entities in the TDM DB. Note that the Reserve task type is also checked by default when the Load task type is checked.
An Load task contains the following tabs:
When checking the Set Task Variables setting, a new Task Variables tab opens.
When checking the Reference Data Type setting, a Reference tab opens.
The following execution parameters are set on Load tasks:
Check Entities and/or Reference to load them to the target environment selected in the Provision to Environment setting.
Note that the Entities must be checked in the task if it also includes an entity reservation (the Reserve task type is checked together with the Load task type).
Click here for more information about the reference handling.
This setting enables the user to change the default LUI sync mode (Sync ON). The following sync policy are available:
Notes:
Click for more information on how overriding the Sync mode and the Task Operation mode impact the task execution process.
The reservation period settings are displayed if the load task also reserves the loaded entities on the target environment (the Reserve task type is checked together with the Load task type).
Note that when the Reservation Period is set to zero, the entities are reserved for an unlimited period.
Only Admin and Environment owner users can reserve entities for an unlimited period. Users that are attached to the target environment as testers must set a reservation period. The maximum number of days of a reservation period is set in the tdm_general_parameters TDB DB table in the MAX_RESERVATION_DAYS_FOR_TESTER parameter.
The start date of the reservation period is the task's execution time. The reservation period can be set in minutes, hours, days or weeks.
This setting has been added by TDM 7.5.2. The user can populate it with a free text. The reservation note is displayed in the Reserved Entities window (Notes fields) and can be used for filtering the reserved entities display. The reservation note can be edited using the Reserved Entities window.
Check to open the Task Variables tab and set the variable value on a task level.
When checked, the task execution process replaces the IDs of all selected entities before loading them into the target. This option is required to avoid key duplications if the testing environment is not empty and contains entities.
Notes:
Select all, partial, or one post execution process of the selected BE.
This tab opens when the task's Data Type includes entities. This tab defines the subset of entities for the task:
The following selection methods are available on load tasks:
This is the default option. Populate the list of entities for the task with entities separated with a comma between them. Note that a warning is given if the entity list has entities that are reserved for another user.
Select a Broadway flow in order to get the entity list for the task and in order to set the maximum number of entities for the task:
TDM 7.5 supports creating external input parameters on a Custom Logic Flow. In this case, the TDM GUI displays the input parameters in the task window, enabling the user to send values for these parameters. See example:
Note:
Select entities from a predefined list of parameters. You should set the parameters and their values and the maximum number of entities for the task.
Note that entities reserved for another user in the environment are excluded from the task. You can select one or several parameters. In addition, you can add the same parameter multiple times with different values:
The list of parameters should be defined for each LU in the task BE in the Fabric project.
The Parameters selection has two modes:
When checked (default), TDM randomly selects the entities from the list of all entities, those that match the selected parameters whereby each task execution gets different lists of entities that match the selected parameters. The Selection Method displayed in the Tasks List window is Parameters - selection based on parameters with random selection.
Example:
When unchecked, it gets the first entities that match the selected parameters whereby each task execution gets the same list of entities that match the selected parameters. The Selection Method displayed in the Tasks List window is Parameters - selection based only on Parameters.
Example:
To add a parameter:
There are several types of parameters:
Combo, parameters with a limited number of values. The Task window displays a dropdown list of the parameters' values. Select a value from the dropdown list.
Click for more information about setting a parameter as a combo parameter.
Number, the TDM GUI displays the minimum and maximum values of this parameter. If the populated values exceed a parameter's range, an error message is displayed.
Date, populate the value using the following format: YYYY-MM-DD.
Notes:
The date format is defined in DATETIME_FORMAT parameter of the config.ini Fabric file. The default format is 'yyyy-MM-dd HH:mm:ss.SSS'.
The parameter's search may be based on either a Date (removing the time from the Date format) or a Datetime.
Examples:
The date value is set without quotation marks.
Text, populate the value using free text.
Click Add Group.
Note that nested groups of parameters can be added, for example, in order to define an inner group in an outer group.
Click Refresh next to the Entities Matched in order to calculate the number of entities that match the selected parameters. The Parameters selection supports the parent-child hierarchy relationship between the LUs of the selected BE. It can both crosscheck the matching entities of a selected combination of parameters and take into consideration parameters from different LUs in the same BE hierarchy. For example, if customers living in New York with scheduled visits (see the screenshot below) are selected, TDM checks the visits of each patient living in New York and then checks their status.
Click for more information about the TDM parameters tables and View created by TDM in the TDM DB to display a hierarchical view of TDM parameters.
Create X clones of the selected entity in the target environment. When selecting this method, the real Entity ID must be populated in order to be replicated.
For example, if the Number of Clones setting is populated with 10 and the Entity ID is set to 6559, the task creates 10 clones (replicas) of Entity ID 6559 in the target environment.
The task replaces the sequences of each replica in order to avoid duplicated sequences in the target environment.
Testers may select this option only if they are permitted to clone an entity in the task's target environment.
Get a random list of entities from the LU PARAMS table created in the TDM DB for the root LU of the task's BE. Entities that are reserved for another user are excluded from the selected entities.
Testers can select this option only if they are permitted to do so in the task's target environment.
A Load task contains the Load task type and loads (provisions) the task's entities and/or Reference tables to the target environment. A load task can also delete entities from target environments before loading them and/or reserve the target entities in the TDM DB. Note that the Reserve task type is also checked by default when the Load task type is checked.
An Load task contains the following tabs:
When checking the Set Task Variables setting, a new Task Variables tab opens.
When checking the Reference Data Type setting, a Reference tab opens.
The following execution parameters are set on Load tasks:
Check Entities and/or Reference to load them to the target environment selected in the Provision to Environment setting.
Note that the Entities must be checked in the task if it also includes an entity reservation (the Reserve task type is checked together with the Load task type).
Click here for more information about the reference handling.
This setting enables the user to change the default LUI sync mode (Sync ON). The following sync policy are available:
Notes:
Click for more information on how overriding the Sync mode and the Task Operation mode impact the task execution process.
The reservation period settings are displayed if the load task also reserves the loaded entities on the target environment (the Reserve task type is checked together with the Load task type).
Note that when the Reservation Period is set to zero, the entities are reserved for an unlimited period.
Only Admin and Environment owner users can reserve entities for an unlimited period. Users that are attached to the target environment as testers must set a reservation period. The maximum number of days of a reservation period is set in the tdm_general_parameters TDB DB table in the MAX_RESERVATION_DAYS_FOR_TESTER parameter.
The start date of the reservation period is the task's execution time. The reservation period can be set in minutes, hours, days or weeks.
This setting has been added by TDM 7.5.2. The user can populate it with a free text. The reservation note is displayed in the Reserved Entities window (Notes fields) and can be used for filtering the reserved entities display. The reservation note can be edited using the Reserved Entities window.
Check to open the Task Variables tab and set the variable value on a task level.
When checked, the task execution process replaces the IDs of all selected entities before loading them into the target. This option is required to avoid key duplications if the testing environment is not empty and contains entities.
Notes:
Select all, partial, or one post execution process of the selected BE.
This tab opens when the task's Data Type includes entities. This tab defines the subset of entities for the task:
The following selection methods are available on load tasks:
This is the default option. Populate the list of entities for the task with entities separated with a comma between them. Note that a warning is given if the entity list has entities that are reserved for another user.
Select a Broadway flow in order to get the entity list for the task and in order to set the maximum number of entities for the task:
TDM 7.5 supports creating external input parameters on a Custom Logic Flow. In this case, the TDM GUI displays the input parameters in the task window, enabling the user to send values for these parameters. See example:
Note:
Select entities from a predefined list of parameters. You should set the parameters and their values and the maximum number of entities for the task.
Note that entities reserved for another user in the environment are excluded from the task. You can select one or several parameters. In addition, you can add the same parameter multiple times with different values:
The list of parameters should be defined for each LU in the task BE in the Fabric project.
The Parameters selection has two modes:
When checked (default), TDM randomly selects the entities from the list of all entities, those that match the selected parameters whereby each task execution gets different lists of entities that match the selected parameters. The Selection Method displayed in the Tasks List window is Parameters - selection based on parameters with random selection.
Example:
When unchecked, it gets the first entities that match the selected parameters whereby each task execution gets the same list of entities that match the selected parameters. The Selection Method displayed in the Tasks List window is Parameters - selection based only on Parameters.
Example:
To add a parameter:
There are several types of parameters:
Combo, parameters with a limited number of values. The Task window displays a dropdown list of the parameters' values. Select a value from the dropdown list.
Click for more information about setting a parameter as a combo parameter.
Number, the TDM GUI displays the minimum and maximum values of this parameter. If the populated values exceed a parameter's range, an error message is displayed.
Date, populate the value using the following format: YYYY-MM-DD.
Notes:
The date format is defined in DATETIME_FORMAT parameter of the config.ini Fabric file. The default format is 'yyyy-MM-dd HH:mm:ss.SSS'.
The parameter's search may be based on either a Date (removing the time from the Date format) or a Datetime.
Examples:
The date value is set without quotation marks.
Text, populate the value using free text.
Click Add Group.
Note that nested groups of parameters can be added, for example, in order to define an inner group in an outer group.
Click Refresh next to the Entities Matched in order to calculate the number of entities that match the selected parameters. The Parameters selection supports the parent-child hierarchy relationship between the LUs of the selected BE. It can both crosscheck the matching entities of a selected combination of parameters and take into consideration parameters from different LUs in the same BE hierarchy. For example, if customers living in New York with scheduled visits (see the screenshot below) are selected, TDM checks the visits of each patient living in New York and then checks their status.
Click for more information about the TDM parameters tables and View created by TDM in the TDM DB to display a hierarchical view of TDM parameters.
Create X clones of the selected entity in the target environment. When selecting this method, the real Entity ID must be populated in order to be replicated.
For example, if the Number of Clones setting is populated with 10 and the Entity ID is set to 6559, the task creates 10 clones (replicas) of Entity ID 6559 in the target environment.
The task replaces the sequences of each replica in order to avoid duplicated sequences in the target environment.
Testers may select this option only if they are permitted to clone an entity in the task's target environment.
Get a random list of entities from the LU PARAMS table created in the TDM DB for the root LU of the task's BE. Entities that are reserved for another user are excluded from the selected entities.
Testers can select this option only if they are permitted to do so in the task's target environment.