remotepublish-page macro
Overview
The remotepublish-page macro is used as an action to publish content to a space on a different Confluence Server, Data Center, or Cloud instance.
content is developed in a space on the source server
published content is pushed to a space on a remote server
For more information, see: Remote-space publishing
Requirements
This macro requires the installation of the Comala Remote Publishing app for Comala Document Management.
Before using this macro, you must ensure both the source and target Confluence instances are properly configured.
For more information, see Remote-space publishing.
Where to use it?
Optional.
One or more remotepublish-page macros can be put in a trigger macro.
Parameters
Parameter | Required | Default | Notes |
|---|---|---|---|
| The name of the remote publishing configuration profile to use.
where config_name is the name of the remote publishing profile added in the remote space configuration in the Document Management dashboard. The configuration profile defines the remote server URL and destination space, as well as the username and password for an account on that server which has Edit Content permissions in the target space. |
Basic example
This example remote-publishes to a server defined by the "MyDestination" remote publishing configuration.
{workflow:Remote-space publishing}
{state:Editing|submit=Review}
{state}
{state:Review|approved=Published|rejected=Editing}
{approval:Review}
{state}
{state:Published|updated=Editing|final=true}
{state}
{trigger:statechanged|state=Published}
{remotepublish-page:MyDestination}
{trigger}
{workflow}The final=true parameter on the Published state is not required for remote-space publishing, however it helps to clarify which versions of content are published in the source space.
All examples
See also
External links