States are distinct work areas in which certain activities can take place as packages move from creation to completion. A lifecycle can include any number of states. A state is typically associated with a view, which allows users to “see” the data stored in a CA Harvest SCM repository. All users in a state share one view. This setup means that they see the same items, and changes made to an item in a state are immediately visible to all other users in that state.
You can define a state without a view when access to items is not needed. For example, a lifecycle could have an initial state named Assigned Changes, which is simply a holding area for newly created change requests. This state does not have a view and its processes are limited to those processes that do not access repository data, such as approve, promote, and create package.
After you define a lifecycle, including states and views, the Workbench Explorer View shows the following objects:
|
Copyright © 2013 CA.
All rights reserved.
|
|