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
Confluence PDF and Word Export
- Robert Alexander Marshall
Overview
This page describes how Comala Document Management app integrates with the native PDF and Word Export features of Confluence when using same-space publishing.
Page-level export
When exporting pages and blog posts as PDF or Word the current state of content will be published, respecting workflow Published vs. Draft if using same-space publishing.
| Workflow state type | Notes | |
|---|---|---|
| No workflow | Latest version of content is exported | |
| Unrestricted workflow state | Latest version of content is exported |
| Draft workflow state | Draft version being viewed is exported |
| Published workflow state | Published version is exported |
The published version is the content version created the last time a transition to the final state occurred.
In same-space publishing, if the final state content is edited and there is no transition to another state
- the version in the final state will change
- but the published version will not change until another transition into the final state takes place
To ensure that content in the final state is always the published version simply add the updated transition to the final state.
See State Status Indicator Circles and Publishing for more information.
Draft content export
When exporting draft content, the associated workflow state will be shown in the output, under the page title, as shown below
By default, only users with Edit or Admin permissions can view draft content.
When we exported this page as a PDF
- the content was considered draft content
- it was still in the workflow state named Draft
- there was no workflow history of a previous transition to the final state (no published version had been created)
Once a published version has been created on a transition to the final state
- the native export options default to exporting the published version
- the state name does not appear in the export
Space-level export
At the space level, we only integrate with the PDF export.
- for pages without workflows applied, the latest version will be exported as usual
- for pages with workflows, but where there is noÂ
final=truestate in the workflow, the latest version will be exported as usual - for pages with workflows that have aÂ
final=truestate, only the published content version will be exported; draft content will not be exported.
There is no way to export a draft version of content with the space-level PDF export.
If the space is exported as HTML or XML, the latest versions of all pages will be included.
See also
