Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
Excerpt | ||
---|---|---|
| ||
Publish content to a different space |
The {publish-page}
macro is used as an Action to publish content to a different space on the same Confluence Server or Data Center instance.
One space is set up as the source, where content is produced
Another space is set up as the destination, where content is published to
For more information, see: Different-space publishing
...
Where to use it?
Optional.
One {publish-page}
macro can be put in a {trigger}
macrotrigger macro.
If using the Comala Publishing {publish-page
} macro to publish content with metadata references to a different space, the {publish-page
} macro action and the metadata modification macro action need to be in separate triggers to ensure the metadata is updated on the published space page.
...
Basic example
Code Block | ||||
---|---|---|---|---|
| ||||
{workflow:name=Different-space publishing} {state:Editing|submit=Review} {state} {state:Review|approved=Published|rejected=Editing} {approval:Review} {state} {state:Published|update=Editing|final=true} {state} {trigger:statechanged|state=Published} {publish-page} {trigger} {workflow} |
Note: The final=true
parameter on the Published state is not required for different-space publishing, however it helps to clarify which versions of content are published in the source space.
All examples
Filter by label (Content by label) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
See also
External links
Comala Publishing app (Atlassian Marketplace)