Replication of releases, processes, and folder templates

A process is a collection of generic process rules. The process rules are for a set of purposes that together control how the update members operation includes changes in projects or project groupings. The process rules control how changes flow from development through one or more testing stages to release.

A generic process rule is a pattern that is independent of release and that defines how changes are gathered when an update operation is performed.

When a release definition is created, the generic process rules are used to define how the specific process rules for that release are formed. The resultant release-specific process rules are then used for controlling the process for that release. The process rules control which changes are included when a project or project grouping for that release is updated. The release definition and the set of process rules it uses defines the valid purposes that can be used for the release. They also control how a project or project grouping with that release and one of those valid purposes is updated.

DCM supports the replication of processes and generic process rules. It supports the replication of releases and their associated release-specific process rules. The following separate mechanisms are supported.

Built-in predefined generic process rules and folder templates are always excluded from DCM transfer packages by built-in exclusion rules. These built-in process rules and folder templates cannot be modified or deleted and they always exist identically in each database. They therefore do not need to be replicated.

Note: When a folder is added indirectly to a transfer set because of a process rule, the tasks of that folder are not added. If you want the tasks of that folder to be included, you must explicitly add the folder as a direct member of the transfer set.

Feedback