States for Registry Objects
The registry stages are broken down into states for lifecycle-enabled objects like services. This way the lifecycle process can be split into smaller steps, each supported and controlled by its responsible stage registry. States are connected to each other by allowable transitions. An approval process can define the conditions and activities to set a service from one state to another. CentraSite comes with the following:
A set of object states, associated to each registry stage
A state-transition proposal to control the lifecycle
An example for collaboration management by roles, rights and notifications
By using stages and states, you ensure that the registry object always has one defined state, even if multiple registries exist. State transitions are restricted; this ensures that the registry object had passed the lifecycle process correctly and achieved the required quality.
When moving from one state to the next, the following situations can exist:
The required next state is in the same stage as the current state. In this case, the state change can be performed directly on the registry object from the user interface.
The required next state is not in the same stage as the current state. In this case, the object must be exported (where necessary, along with its associated objects). In the exported archive, the current state remains unchanged. On importing the archive to the new stage, the state is set automatically to the appropriate new state.
