Directly publishing / rejecting
Apart from status changing, this dialog also offers the possibility of viewing the changes to a document. Each change is represented by its own line in the list. In addition, it is shown who made the change and when.
As well as offering pure information, this list also gives you the possibility of directly publishing or rejecting all changes or just individual ones.
“Publishing” means that the selected changes pass directly into the productive area without the complete ChangeSet having to be published.
In order to do this, either press the button “publish directly” or “reject” in the area “direct actions”.
A check box will appear beside each of the changes. You can use the check box to define whether the respective change is to be published or rejected.
Thanks to this mechanism, changes from the ChangeSet can go directly online without the complete document having to be published. Other changes which are intended for a later time stay in the ChangeSet as a change after publication. The exact same thing goes for the rejecting of changes. All other changes stay but the selected changes are deleted from the ChangeSet.
With this kind of publishing or rejecting it is possible for conflicts to arise however. The ChangeSets are always valid as a whole, but older changes in documents may contradict changes in other elements.
Example: In a navigation path there is a document with the name A and a document with the name B. Document A is renamed to “D” and then to “C”. Document B is now renamed to “D”. Following all editing steps, there is now a Document C and a Document D in the ChangeSet.
Using the “publish directly”function of Document D, an editor would now like to publish the change of name “from A to C”. This will cause a conflict however, since there is (now) another document with this name.
Working with “statuses”
