Overview
| Insert excerpt | ||
|---|---|---|
|
|
|
|
Remote space publishing is triggered by an action macro, {remotepublish-page} used in a {trigger} added to the workflow.
the trigger can be set for different events.
the
{final=trueparameter is not necessary for remote-space publishing, all the work is done by the
}remotepublish-pagemacro
The app also installs the
...
...
macro. This macro can be used in a
...
...
for example when the content becomes obsolete and needs to be removed from the remote published content.
Set up remote space publishing
Once the Remote Publishing app is installed there are three steps to set up remote space publishing:
set-up the remote Confluence instance space where the content will be published to and add a user account with user permissions to view, add, and delete content in the space for the published content
set-up the local Confluence instance in the space tools Remote Publishing tab
update your workflow to trigger the publishing process
When content is published into this remote space it will appear to be authored and edited by the user you have set up.
...
The remote instance can be a server or a Cloud instance.
| Info |
|---|
Using a Cloud instance as the remote instanceIf a Cloud instance is used as the remote instance then you will will need to configure an API token in the user account Atlassian administration. The API token needed for the user password field needs to be requested by the user who will appear to publish the articles. |
Remote Space Publishing
Remote Space Publishing - Set up local instance; set up remote instance; add remote publishing trigger
Macros
| Filter by label (Content by label) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Examples
| Filter by label (Content by label) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|