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 15 Next »

Overview

Once a draft source space has been configured to publish to a target space and enabled for publishing you can

Both the source space and the target space must be in the same cloud site.

Comala Publishing Cloud does not support publishing the home page of a space and cannot be used to publish blog posts.

Publishing Actions

You can choose one of the following ways to publish your content.

As a standalone publishing app to

Together with an applied workflow from the Comala Document Management family of apps to

Although the Comala Document Management family of apps can be applied to both pages and blog posts, Comala Publishing can only publish page content. Any blog post with a Comala workflow applied will simply be ignored by the Comala Publishing app.

The first publishing action for a page will generate a copy of the source page content and properties in the target space.

Confluence version metadata is not copied from the draft page. The first publishing action will set the page version in the published/target space is set as v.1. Each subsequent publishing action for the page will increment the target space page version.

The published content in the target space will maintain where possible the page hierarchy in the source space. However, the order of the published pages in the target space may be different from that in the source space.

Related pages

  • No labels