Managing Packages in the Life Cycle › Promote Process

Promote Process

The promote process lets you send one or more packages in the current state to the next state in the life cycle. If you select multiple packages for promotion, they are promoted as a unit. When you promote a package to a state with another view, all its changes become visible in that view.

These conditions affect whether you can promote a package:

• If a user has rejected a package, you cannot promote the package until that user executes the approval process.
• If one or more approval processes exist in a state, you cannot promote a package until all approvals have been given for at least one approve process.
• If a package is part of a bound package group, all packages in the group must be promoted together. To promote a package that belongs to a bound package group, you must first unbind the package.
• If the promote properties does not allow unmerged packages to be promoted, the latest change for a package must not be on a branch.
• If the promotion includes a change in view, the package being promoted cannot include reserved items.

  Note: For the purpose of this restriction, promoting from a state with a view to a state without a view is considered changing views.

The promote process also performs the following verifications if you promote packages from a state with a view to a state with a different view.

• A version of an item cannot be promoted unless its path version is also being promoted or the path version has already been promoted to the destination view.
• Items in packages being promoted may not have an item name conflict with items in the destination view. An item name conflict occurs when the latest versions of two different items in the same path have the same name.
• If the Verify Package Dependency option is selected, you cannot promote a package with a higher item-version without also promoting the packages with the lower item-versions in the current view, unless the lower item-versions already exist in the destination view. The lower item-version causes a dependency error only when it is on the trunk.