Defining Regions |
DEVELOPER |
 |
|
Defining Regions |
DEVELOPER |
|
You must define regions to be managed before you confirm the configuration. This is a single user process and all users in this development region and all the regions defined as the migration path need to be logged off before you confirm the configuration. Confirming configuration will perform validation checks (that all regions are 'V' + two digit current version (as found from &$@~PROPATH) and have not been already been included in another Change Management migration path). Assuming the validation process finds no errors then the configuration process concludes (it may take a few minutes depending on the number of source code objects in the development region and how much existing PROIV Developer history updates Change Management files). All the regions are now controlled by CM. On re-entering the CM console all the regions are enabled. However, you can no longer modify any of the configuration information. If you realise that you have misconfigured CM then the only option is to uninstall and install again. This is to ensure the level of control that is required.
Open the Administration Console and click the Regions tab.
Click Add Region.
The Region Maintenance window.
In the Region box, enter a name for the region.
In the Description box, enter a description of the region.
In the Region Order box, enter the display order number. The Region Order defines at what point in the migration path the region is placed.
In the Region Path box, enter the path for the region.
On the Transfer Status (Import) list, select either "Work in Progress" or "Available" as required. it determines whether the objects contained within a ‘Release’ can be modified in the development region whilst the release is currently in the region being defined.
Click OK to create the new region.
 |
To modify the region, select the required region and then click Change Region. To delete the region, select the required region and then click Delete Region. |
Topic ID: 550038