When you create a transfer set, you define its properties only (that is, the transfer set name, any excluded objects, and so on). Later, you can add members to the transfer set for each object. You can add projects, directories, and files with or without history. Adding a project, directory, or file with history adds all versions of that object to the transfer set.
When you add a project, task, or folder to a transfer set, DCM automatically adds all members of that object. You have the option to fully expand update properties during the Generate operation.
Adding an object to a transfer set does not guarantee that it will be sent. Some objects are excluded by built-in exclusion rules. The settings on the transfer set might also exclude some objects. Conversely, the predefined Entire Database transfer set automatically includes all projects, directories, files, tasks, folders and baselines. Only a DCM manager or an administrator can add objects to a transfer set.
The table shows what is included when you add each type of object to a transfer set, and you do not select the Fully Expand Reconfigure Properties option.
Object type |
Objects added to the transfer set |
History |
folder |
The folder itself, its member tasks, and all objects associated with the tasks. |
NA |
task |
The task itself and all objects associated with the task. If the task is a component task, including associated projects or products. If the Include associated baselines option is selected, any baselines that include the task are also included.
|
NA |
project |
The associated task of a project excluding any automatic tasks. If there is a component task or user-created task associated with this project, that task is included. For non-static projects such as prep projects, the following are also added: 1) Any project baseline that the project is using, 2) All folders and tasks in the update properties of the project, and 3) All tasks in the folders.
If the Include associated baselines option is selected, any baselines that include the project are also included.
The associated objects of tasks are not included unless they are members of the project hierarchy.
Subprojects of any project baseline are not included unless these subprojects are used as a baseline in the project hierarchy.
|
optional |
project grouping |
The project grouping itself, its member projects, and all tasks and removed tasks of the project grouping. The projects and tasks in a project grouping are expanded. Only project groupings for prep projects are eligible for replication. Project groupings for projects in other non-static states are not replicated since those projects are ineligible.
|
NA |
baseline |
The baseline object itself, any component tasks that were created from the baseline, the project members, and the task members of the baseline. The component tasks, project members, and task members of the baseline are further expanded. |
NA |
process rule |
The process rule itself, and the folder and folder template members of the process rule. |
NA |
process |
The process definition itself, and the generic process rules that are used by the process. Each generic process rule is expanded. |
NA |
product |
The object itself and any non-automatic task associated with the product, including any component task associated with the product. |
NA |
source |
The object itself and its associated tasks. |
optional |