Replication of generic and release-specific processes

About this task

A process is a collection of generic process rules. The process rules are for some set of purposes that together control how the update (also called update members and reconfigure) operation includes changes in projects or project grouping. They control how those 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 in Rational® Synergy 6.5 and later supports the replication of processes and generic process rules. It supports the replication of releases and their associated release-specific process rules. Two separate mechanisms are supported:

Procedure

  1. Processes and process rules can be explicitly added to a DCM transfer set. When a process is added, it also includes the process rules used by that process. When a process rule is added, either directly or indirectly through adding a process, the folders and folder templates of the process rule are also indirectly added.
  2. Release definitions and their associated process rules can be automatically added as indirect query members through the use of a Release Scope and a Release Query. The scope and query define which releases are automatically added, and for each such release, its process rules are also automatically added.

Results

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