This site has moved to the integrated Appfire documentation and information site for our apps.

From February 2024 this site is no longer updated.

Take a look here! If you have any questions please email support@appfire.com

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Overview

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

Requirements

You must install the Comala Publishing app in order to use this macro.

Where to use it?

Optional.

One {publish-page} macro can be put in a {trigger} macro.

(info) 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.

Parameters

The macro has no parameters, it uses the publishing profile defined in the space tools Publishing dashboard if Comala Publishing is installed. For more information, see Different-space publishing.

Basic example

{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

See also


  • No labels