Using Comala Publishing Cloud with Comala Read Confirmations Cloud

Owned by Robert Alexander Marshall
Last updated: Feb 15, 2024
2 min read
1 Overview | 2 How does this work in each space?

Overview

Comala Read Confirmations for Confluence Cloud can be added to pages to assign team members to read Confluence pages, and keep track of who has confirmed.

When using Comala Publishing Cloud to publish a source (draft) space page with a read confirmation added, in the target space published page

  • the read confirmation is included as part of the published page content

  • the read confirmation history is not copied with the read confirmation (assigned user requests; read confirmation history)

Publishing the page to the target (published) space creates a new page version in the target space

  • readers can be assigned readers to the target page read confirmation

  • previous read confirmation history and assigned users on the target space page are not overwritten or removed

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 space page are not published to the target space page

  • draft page read confirmation history (pending, user confirmations) is not published

The publishing action of Comala Publishing Cloud

  • does not remove any assigned readers added to the target space page

  • does not overwrite any read confirmation history created on the target page

This allows the retention and maintenance of a separate read confirmation history for the draft page and the target published page.

What happens if the target space page has a read confirmation and a draft page update is published without an added read confirmation?

The publish action

  • will remove the read confirmation and read confirmation byline from the target page

but

  • WILL NOT remove the read confirmation history from the target page

If required, adding a read confirmation using the page tools menu to the target space page restores the target page

  • read confirmation

  • read confirmation byline

  • read confirmation history

These are also restored if a read confirmation is added to the source page and published.

Read confirmation history is NOT restored if the read confirmation macro is added by editing the target page.