Change list
A “ChangeSet” can also be referred to as a “change list”. This means that editors’ work in a ChangeSet is automatically backed up in a change list. Each ChangeSet works independently of the other. This means for example that content in documents can be changed in a ChangeSet, while the same documents are adjusted in structure in another ChangeSet.
If the work in a ChangeSet has been completed to a satisfactory degree, these changes can be transferred to the productive area. That is to say, all activities in the ChangeSet have not yet had any effect on the productive area up to this point. These changes are applied to the productive area through the publication of a ChangeSet. Of course, ChangeSets can also be rejected. It makes sense to do this in order to safely try out changes on the data stock. For example, the documents in a ChangeSet can be completely re-sorted in order to test a new navigation structure.
Previews of the ChangeSets can be seen at any time if you need to check what the changes to the productive stock would look like. Moreover, previews from several ChangeSets can also be combined to test the interaction of tasks which have been worked on at the same time.
It is possible to make changes to the same documents in different ChangeSets as long as these changes are not conflicting. This would be the case for example if the name of a document had been changed in ChangeSet A and an editor wished to change the name of the same document in ChangeSet B. He gets a message stating that this is a conflict. Other changes to the document can be performed however, such as the re-sorting or changing of content fields which we have already talked about.
