Locking change labels
If a change label is locked, no further changes can be booked to this label. For example, change labels can be locked and closed after they have been transported with the Database Transporter.
To lock a change label
-
In the Manager or the Designer, select the Database > Change management menu item.
-
In the Change management dialog next to the Change labels menu, click .
-
Select a change label from the list and open the edit view using .
-
Select the value True for the Locked property.
-
Click the button.
-
Click OK.
Related topics
Deleting change labels
You can delete a change label if you do not need it anymore.
To delete a change label
-
In the Manager or the Designer, select the Database > Change management menu item.
-
In the Change management dialog next to the Change labels menu, click .
-
In the Change label dialog, select the change label and click the button .
-
Confirm the security prompt with Yes.
-
To close the Change label dialog, click Cancel.
-
To close the Change management dialog, click OK.
Related topics
Release management
You can combine several change labels into one release. There is a report that provides you with an overview of the changes in a release.
To combine change labels into one release
-
In the Designer, select the Base data > General > Release management category.
-
Select the Object > New menu item.
-
In the edit view, enter a minimum of the following information in the edit view of the Properties tab.
-
In the edit view, select the Change label tab and assign the change labels you want to combine into one release.
To display a report about a release
-
In the Designer, select the Basic data > General > Release management > <name of release> category.
-
Select the Show report task.
This opens the Change management release overview report.
Related topics
Checking data consistency
The consistency check provides different tests for analyzing data objects and to ascertain the current state of their data. In addition to predefined tests, you can define your own tests and, if necessary, run a repair.
You should run a consistency check at regular intervals, as well as after significant changes to the system configuration.
You can run consistency checks in the Manager and in the Designer. The following special cases apply:
-
Database tests are run in their entirety in the Manager and the Designer.
-
Table tests and object tests in the Manager check the application model data.
-
Table tests and object tests in the Designer check the data of the system data model.
Detailed information about this topic