Publish Content

The publish action allows you to publish content to different places or spaces. This will create a copy of the content in specified spaces and/or with an existing page as its parent.

Currently this action only supports pages. It will not work on blogs or other content - if attempted it will silently fail. If publishing other content is interesting to you, please mention that as feedback so we can add this feature to our product roadmap.

The original spaces homepage will be excluded as an ancestor of the published page.

Name of Field	Type of Field	Description
Places to Publish to (Pages)	Page multi select	Search for and select spaces for content to be published under.
Places to Publish to (Spaces)	Space multi select	Search for and select pages for content to be published under.
Clone Page Ancestry	Boolean	Maintain the page hierarchy during publishing. This will copy all pages between the published page and it's current spaces homepage into the new space/place as its parentage.
Clear Attachments	Boolean	Don't copy attachments when publishing.
Clear Permissions	Boolean	Don't copy permissions when publishing.
Clear Labels	Boolean	Don't copy labels when publishing.
Copy Content Properties	Boolean	Copy pre-existing content properties when publishing.
Publish as Transitioner	Boolean	Publish the page as the user who transitioned the workflow instead of the Workflows for Confluence app.
Publish Source Page Workflow Metadata	Boolean	Copy workflow metadata from the source page and display the data within macros on the published page. Behaviour of individual macros on the published page is as follows: Workflows Metadata macros: Status: This macro displays the name of the status node directly prior to the publishing action on the source page, regardless of whether it is a logic node or an approval node. If this node is an approval node, a counter showing the number of approvers is appended. Approvers List: This macro shows a list of all approvers who approved the source page. Transition Date: This macro displays the timestamp of the publishing transition. Unique Page ID: This macro shows the Confluence page ID of the source page. Workflows Approvers Metadata macros: All Approvers for Current Workflow: This macro shows all the approvers that have been included in the approvals on the source page up until the page was published. Latest Approvals for Current Workflow: This macro shows all approvers who have made a decision (approved or rejected the page) on the source page until the point the page was published.

Pro Tip:

The original page that a published page clones is stored as a property on published pages. This can be searched in CQL to find pages that are published copies of a specific page. Use the field 'original' and search by ID of original page.

original=267893

original IN (267893, 309752)

Behaviour

When a space is selected as a place to publish, the action will clone the original page into the destination space immediately under that spaces homepage. If cloning ancestry, each parent page will also be cloned into the new space. The page order will be maintained and the upper most page will be immediately under the new spaces homepage.

When a page is selected as a place to publish, the action will clone the original page immediately under the specified page as a child. With clone ancestry enabled, each parent page will also be cloned under the destination page. The page order will be maintained and the upper most page will be immediately below the targeted page.

No other changes are made to the page. However, if a page with the same title already exists in a space, a number in brackets will be appended to the title name to make it unique (e.g. "Published Page" => "Published Page (1)")

If a page would be published as a sibling of a previously published version of the same page, that previous version will instead be updated. For example, if one uses the same configuration to publish the same page twice, the second time there will be a previous version. This feature will not look in other spaces or elsewhere in the same space for existing clones. This means that repeatedly publishing a page with the same settings will publish an initial copy, then update that page with future publishes. If a page is published, then the original is moved, a future publish will create a new clone based on the original pages new location. Likewise if the clone were moved, a future publish would create a new clone where the moved one used to be. Additionally, for a page to be considered an existing clone, it must have been created by the publish action previously.

Need support? We’re here to help 🧡

If you have any questions or would like to speak with us about Workflows, please don’t hesitate to reach out to our Customer Support team.