Update 14th May 2020 11:30 UTC: These issues have been resolved and the functionality has been re-enabled.
An issue has been identified in Chorus which causes the published specification to display REVISED instead of UNCHANGED labels.
This article sets out the issue. Whilst it is being fixed NBS have disabled the 'save to publish history' and 'compare' steps for the publishing routes which cause it.
This means that when you publish a selection of your spec you will not be able to save this to your publish history or compare it with a record in your publish history.
We apologise and are working hard to fix it.
We will be posting updates and answering queries on this issue in the Known issues forum. Please follow this if you want to receive update notifications.
Issue
When you compare a selection of the spec with a previous record in the publish history the sections/systems will appear as REVISED, even if they have not changed.
Sections/systems which were added/deleted will show the correct ADDED/DELETED labels. But the rest will show as REVISED instead of showing UNCHANGED.
This was identified when comparing your specification was released on 9th April.
Related article: How to publish your specification with revision labels
Cause
- When you publish a selection of your spec and save this to your publish history, we have found that Chorus is not recording that linked 'child' items are in the selection.
- Child items are articles or clauses in the sections or systems being published.
- When you compare against a publish history record saved for a selection of the spec, the child items are being identified as new and therefore the section/system is marked as REVISED. This happens even if there have been no edits.
How this impacts your specification
If you compare the spec you are publishing now with a record in the history affected by this issue, you will see change labels saying REVISED instead of UNCHANGED which is misleading.
The content of your specification is unaffected. This issue relates to the reporting of how the document has changed.
Publish history records that were saved with a selection of the spec since 18th February 2020, when saving to the publish history was introduced, will give inaccurate REVISED labels for sections/systems that have not changed.
We do not recommend that you compare against these records because you will get potentially inaccurate change labels in the spec.
We apologise and are working hard to fix this.
Here is a link to the Known issues forum where we will be posting updates and answering any queries you might have about this.
Related articles: