Overview
Comala Publishing Cloud provides between-space publishing to allow you to keep your draft space page content separate from finished work in a target space.
When using Comala Publishing Cloud to publish a draft page to a target space
- a read confirmation request added to the draft page will be retained on the page in the target space
Publishing the page to the target space creates a new page version in the target space
- the target space content will have a read confirmation with no readers
- you can assign readers to the target space content read confirmation
Publishing updates from the draft space to the target space will not remove the read confirmation history created on the target space page.
How does this work in each space?
Draft space
Read confirmation requests and assigned reader actions on the draft space page are retained only in the history of the draft space page.
Publishing the page only publishes the read confirmation request itself - the read confirmation history for the draft space page is not published to the target page.
Target public space
A draft space page with a read confirmation request is published with the added read confirmation
- users assigned as readers in the draft source space page are not published
- draft source space page read confirmation history (pending, user confirmations) is not published
Adding users as readers to the target space page read confirmation does not cause the content to be Out of Sync.
This allows the retention and maintenance of a separate read confirmation history for the draft source space page and the published target space page.
Publishing a draft source page update will require any confirmed reader confirmations for the target source page read confirmation to re-confirm reading the content.