Add a destination (target) space for publishing
Overview
A chosen source space must be configured to publish pages to a selected target space using the Target space dropdown menu in the space settings publishing dashboard.
A space that has an existing publishing configuration as a source space or a target space cannot be added as a target space. Selecting a space with an existing publishing configuration disables the Change button and displays a warning message.
Add or edit a target space for publishing
Choose the space settings publishing dashboard in your source (draft) space.
For a space with no current target space configured, space administrators can choose the Configure Publishing button to use the space publishing configuration setup tool to add the target space
Choose the Target space dropdown menu to display options for your target space (the published space).
The Target space dropdown menu automatically displays spaces where the current spaces where you have space administrator permission. These are limited to a maximum of 10 spaces:
the last 10 spaces accessed by the current user
if less than 10 spaces have been accessed, the menu list includes the last created spaces (to display up to a maximum of 10 in the list)
A space can also be searched by name.
The current user also needs to have view and edit permissions for the target space.
Select the target space and choose Save.
On change of the target space, an on-screen message confirms the target space is saved.
Adding a target space to the source space publishing dashboard enables the space for publishing and single-page publishing by default. It also displays the option to publish all the pages in the space.
Any changes in the space publishing configuration are confirmed in an on-screen message.
The target space publishing dashboard also displays confirmation of the successful configuration.
An information dialog box is displayed to users when editing a page in the configured target space, warning that any changes can be overwritten the next time the page is published (synced) from the source space.
Once publishing features are enabled and the target space added, pages can be published
individually by a page editor as a standalone publishing action using the publishing byline to open the publishing popup (single-page publishing)
as a whole space by a space administrator using the Publish space option in the space settings Publishing dashboard.
Pages can also be published using an applied Comala Document Management workflow:
The space administrator can also choose to limit a space publish action to pages in the final state of the workflow.
Selecting a target space already configured as a publishing source space or target space
On selecting a target space in the dropdown menu that is already configured as a source space for publishing or is a target space for another space
the Change button is disabled
a warning message is displayed
If the selected space is required as the target space for the current space, the existing publishing configuration must be cleared from this space.
The following dialog box is displayed when the selected space has an inactive publishing configuration.
If the selected space was previously a target space but the publishing and sync have been removed, by choosing the dialog box link to the selected space publishing dashboard, you can
fix the publishing configuration on the previous source space
clear the publishing configuration on this selected space
Comala workflow applied in the target space
On publishing a page from the source space to a target space page with an applied workflow, the workflow state on the target space page ONLY changes when the target page workflow state has an Updated transition.
If the target space has an active space workflow, pages published for the first time are set to the workflow's initial state.
Workflow activity on a target space page does not change the publishing status, for example:
assigning reviewers
approving page content
changing workflow state
For the publishing status to change, the action on the page must cause an updated event on the Confluence page.