Master Templates and their revisions get outdated

A Master Template can be outdated for two reasons:

If it contains an [in development] Master Template revision based on a Master Template script set, usually a Master Template script revision and one or more Includes revisions, of which one ore more do not exist anymore because they have been changed.
If it is based on a Data Backbone revision that does not exist anymore because it has been changed.

A Master Template revision can be outdated for two reasons:

If it is based on a Master Template script set, usually a Master Template script revision and one or more Includes revisions, of which one or more revisions do not exist anymore because they have been changed.
If it is based on a Data Backbone revision that does not exist anymore because it has been changed.

Not all changes in a Data Backbone result in outdated Master Templates. Additions to the Data Definition component of a Data Backbone can be made without consequences.

Creating the Master Template revision makes it up-to-date again, reflecting the changes to the Data Backbone revision or the document revisions.

The outdated [in development] Master Template revision cannot be recreated exactly as it is in the current state.

If KCM encounters errors during Master Template creation, an error message is generated and KCM Repository is opened showing a copy of the Master Template script with error messages marked in red. A [in development, failed] revision is added to show that the revision is not a valid Master Template.

When an [in development, failed] revision is unlocked, it is changed into a proper revision but that revision is not set as the [draft] revision.