Overview
Comala Publishing for Confluence Cloud is a separate app that enables single page publishing between spaces (from a draft to a public space).
Comala Publishing can be used to publish your draft content to another space
The publishing action copies the individual page content from the source (draft) space to the target (public) space maintaining the content hierarchy where possible.
To publish content a user requires view and edit permissions on both the draft space and the public space content.
Enable Comala Publishing
Publishing must be enabled for each space via the space tools Publishing dashboard in the source (draft) space.
When Comala Publishing for Cloud is enabled and a target space selected in space settings, the app can publish a page from the current space to a target (public) space.
The user publishing the content must have view and edit permission in both the source space and the destination space.
Publishing Pages
Once a space is configured for publishing you can
- Publish pages using standalone publishing
A user can publish each page manually using the publishing byline added to the page.
- Publish pages based 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 draft" space.
Publish pages using a trigger in a workflow added to the page
Comala Document Management Confluence 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.
What is copied from the draft content 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 destination 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?
- copying custom content such as GIPHY images is not currently supported
- custom content properties
- version
Comala Publishing Cloud cannot be used to publish blog posts.
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.
Related Links
- Comala Document Management for Confluence Cloud
- Comala Document Control for Confluence Cloud
- Comala Document Approvals for Cloud