Packages

In CA Harvest SCM, all version changes must be made in reference to a package. A package is the basic unit of work that moves through the lifecycle. It typically represents a problem, a task, or an incident that needs to be tracked, the changes made in response to the problem, task, or incident, and any associated information. The create package process lets you create a package in the state defined by the administrator as the initial state.

Packages have the following characteristics:

Package Group—A package group consists of two or more packages. A package can belong to numerous package groups.
State—Promote and demote processes change a package's state.
Forms—A package can have a number of form associations. A form provides the link between CA Harvest SCM change management functions and problem tracking.
Versions—A package can include numerous versions. Double-clicking a package expands the package to show the forms and Versions root node. To see the package’s version, expand the Versions root node.

The Package Properties dialog lets you define a package and associate the package to one or more package groups.