Getting Started with Comala Publishing for Confluence Cloud

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

as a standalone app
together with an added Appfire Comala workflow

The publishing action copies each page’s 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 enabled and configured for a space via the space tools App links Comala Publishing dashboard in the source (draft) space.

Publishing setup wizard

In the Comala Publishing dashboard

choose Configure Publishing to open the space publishing set-up configuration wizard to enable Comala Publishing in the space

The publishing set-up tool is only available if the space is being setup for the first time or any publishsing configuration has been cleared using the Clear Publishing Configuration option.

Publishing dashboard

When a target space is selected and saved in the 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 displayed.

Publishing Setting	Default - on adding the target space	Notes

Publishing Setting	Default - on adding the target space	Notes
Enable publishing	(Enabled)	the app can publish content from your source space to your target space must be enabled to allow both single-page publishing and space publishing of pages must be enabled to allow publishing with a Comala Document Management family of apps workflow
Copy content Properties	Displayed as (enabled by default)	page content properties are copied when publishing a page in the space using single-page publishing and space publishing can be disabled by the space administrator may want to disable this option if there is a 3rd party app in the target space and do not want to override the page properties when publishing a page, for example, if you have applied a Comala workflow on pages in both the source space and the target space
Enable single page publishing	Displayed as (enabled by default)	adds a Publish button to each page in the source space to allow a user to publish each individual page to the target space can be disabled by the space administrator so only whole space publishing can be undertaken
Space publishing	Displayed with Publish space button	a space administrator can 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 are

1 Single-page publishing
2 Space publishing
3 Publish content on an applied Comala workflow event
4 Publishing on the added workflow transition to a final state
5 Publish pages using a workflow JSON trigger

Single-page publishing

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

Single-page publishing can be disabled for a space by the space administrator. This can be useful if you want to limit publishing to whole space publishing by the space administrator or publishing on an applied Comala workflow event.

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.

A progress bar displays the space publishing action progress.

Successful publishing is confirmed in the dashboard. The confirmation includes the date, time and the user who actioned space publishing.

If the space publish action was unable to publish all the source pages, the space publishing dashboard will display a listing of the unsuccessful pages.

If the space has no pages (except the home page), space publishing will not occur. This will be confirmed in an on-screen notification.

Publish content on an applied Comala workflow event

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

Publishing on the added workflow transition to a final state

A Comala workflow can invoke the publishing action to a specified target (public) space when the workflow reaches the workflow 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"}]}]

Publishing confirmation

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

A message is displayed on a page for successful single-page publish action or a successful publish action using a Comala workflow.

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

On each page published page in the source page, a successful publishing confirmation message is displayed on viewing the page.

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

The following is also not published from the source space

inline comments
page-level permissions
comments
archived pages

The publishing status is copied but is not visible on the content for users with view-only permission.

Content properties are copied by default when publishing a page. This can be disabled for a space in the space settings publishing dashboard.

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.

Publishing user permissions

To configure publishing a user needs to have space administrator permission in both the source space and the target space.

When publishing space pages

a space administrator requires view and edit permission for all the pages in the source space and target space
a user publishing an individual page needs view and edit permission the page in the source space and target space

A user also needs 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.

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