This site has moved to the integrated Appfire documentation and information site for our apps.

From February 2024 this site is no longer updated.

Take a look here! If you have any questions please email support@appfire.com

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

Overview

Comala Publishing for Confluence Cloud is a separate app that enables publishing of pages between spaces in the same Confluence site - content can be published from a draft space to a public space.

Comala Publishing can be used to publish your draft pages from one space to another space in the same Confluence site

The publishing action copies each page content from the source (draft) space to the target (public) space maintaining the content hierarchy where possible.

To publish pages a user requires view and edit permissions on both the draft space and the public space content.

Enable Comala Publishing for a space

Publishing must be configured for a space via the space tools Publishing dashboard in the source (draft) space.

When a target space is selected in the space settings Publishing dashboard and publishing is enabled the app can publish a page from the current space to a target (public) space. 

By default, on adding the target space the following options are available

Publishing Setting

Default - on adding the target space

Notes

Enable Publishing

(tick) (Enabled)

  • the app can publish content from your source space to your target space

Enable single page publishing

Displayed as (tick) (Enabled)

  • adds a Publish button is added to the pages in the source space to allow a user to publish each individual page to the target space

Space publishing

Displayed with Publish space button

  • a space administrator to publish all the source space content at one time

Publishing Pages

Once a space is configured for publishing you can publish pages using standalone publishing or together with an applied workflow from one of the Comala Document Management family of apps.

These publishing actions can be:

Single-page publishing

A user can publish each page manually using the publishing byline added to the page.

Space publishing

A space administrator can publish all the content from a source space to a target space in a single publishing action using the Publish space option in the space settings Publishing dashboard.

You can also choose to publish pages together with an applied Comala Document Management workflow by

Publishing on the added workflow transition to a final state

The workflow can invoke the publishing action to a specified target (public) space when the workflow reaches the final state on the page in the source (draft) space.

Publish pages using a workflow JSON trigger

Comala Document Management for cloud provides the option to edit a workflow event trigger publish a page.

  • [{"event":"_transition/change-state","conditions":[{"state":"In Approval"}],"actions":[{"action":"publishing/sync-page"}]}]

The successful copy of the page to the target space is confirmed in an on-screen message.

When using space publishing the successful copy of the page in a space is confirmed in the space settings Publishing dashboard.

What is copied from the draft pages to the target space?

Each published page will include

  • the content title

  • the content body

  • attachments

  • content properties

  • content labels

When publishing the page

  • links to local pages in the source space will be replaced with the links for the content in the target space

When publishing a previously published updated page

  • Comala Publishing deletes the previously published page and copies the updated page as a new page in the target space

What is not copied?

Comala Publishing Cloud does not support publishing

  • the home page of a space and cannot be used to publish blog posts.

  • custom content properties for Comala Read Confirmations app and Comala Document Management Family of apps

  • the source space Confluence version

Page hierarchy

The content will maintain the page hierarchy where possible (but in some instances the order of the content may not necessarily be maintained). If the copying of the hierarchy is not possible then the copy is made to the root of the destination space.

  • the hierarchy will be maintained as long as the parent page exists in the destination space

  • if the hierarchy cannot be maintained the page will be copied into the root of the destination space and a warning message will be shown to the user

If you had previously published a page that had resulted in the page being published into the root of the destination space then any subsequent publishing of the source space page will simply copy the page but not any changes in the page tree parent.

Draft and target space user permissions

You need to have the following permissions in the target space to publish a draft page:

  • View All

  • Add and Delete Pages

  • Add and Delete Attachments

Also ensure that in the target space, the page you are publishing does not have any page restrictions limiting your access.

When publishing a space, the space administrator requires view and edit permission for all the pages in the source space.

If the space administrator does not have view/edit permission for a page, Comala Publishing will not publish that page. The page will also not be included in the list of 'Pages not published'  in the source space Publishing dashboard when the space publishing action is complete.




  • No labels