A process is a command that executes an action.CA Harvest SCM includes a predefined set of process types. You can define a set of processes for each state in the lifecycle. The processes that are defined for a state determine what activities users can perform in that state. Administrators have complete control over which processes are available in each state of the lifecycle, and which users can execute these processes. For example, you can set up the lifecycle to allow check-in and check-out in the Development state, but only allow check-out in the Test state. You can add more than one process of one type to a state. For example, you can have one check-out process for updating items and another check-out process for read-only.
Each process has a type and a name.CA Harvest SCM predefines the process types. A process name is a more precise label that you can specify for added clarity and to distinguish between multiple processes of the same type. For example, promote is one of the predefined process types in CA Harvest SCM. A promote process that has been set up for promoting a package to a QA state could be named Promote to QA. If a name for the new process is not specified, it defaults to Process-nn (nn is the next process record number). The Processes menu in the States folder lists processes in alphabetical order.
You can define user-defined processes (UDPs) to invoke user-supplied programs fromCA Harvest SCM. This feature lets the administrator integrate the use of existing development tools into the lifecycle.
The properties dialog for a process displays associated Access, Pre-Links, and Post-links.
|
Copyright © 2013 CA.
All rights reserved.
|
|