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

Version 1 Next »

Overview

Comala Document Management Cloud, /wiki/spaces/CAD/pages/13933903873 or Comala Document Approval can be added to pages in a space configured as a target space for publishing.

Publishing a page to the target space creates a new page version in the target space

  • a page published for the first time to a target space with an active space workflow will have a workflow applied with the page in the initial state of the workflow

  • publishing an existing page will cause the workflow to change only if the current workflow state includes an Updated transition

Target page applied workflow events will not cause any change in the publishing status for the page including

Publishing updates will not remove document activity on the target space page.

The content properties for any workflow applied to the source space page are not published by Comala Publishing - this means source space page Comala workflow and Comala Read Confirmation properties are not included in publishing.

Target space page workflow and sync status

For example: we have a source space A that publishes to an empty target space B.

Space B

  • has a workflow applied (this can be a workflow from any of the three Comala Document Management family of apps)

The following workflow is enabled at space level.

When publishing a page from A to B, we are initialising the state of the target page to the initial state of the workflow applied to that target page.

For each subsequent publishing of a source page, the workflow state of the target page will remain as it was when publishing, unless the current workflow state has an Updated transition.

In our example workflow the Review state and the Approved state each have an Updated transition.

Action

Target space page workflow activity and publishing status

New page created in source space A named Page and published to target space B

  • the page publishing status is Synced in both the source space and the target space CHANGED

  • workflow state of newly created target Page in space B is set to initial state of the workflow applied to the target space page. In our example, the Draft state CHANGED

Target space page Page in target space B is submitted for review to workflow state Review

  • Page publishing status remains Synced in both spaces NO CHANGE

  • workflow state of target space page Page is Review (with one approval-check mark) NO CHANGE

Target space page Page in target space B in workflow state Review is approved by one assigned user (out of three assignees)

  • Page publishing status remains Synced in both spaces NO CHANGE

  • workflow state of target space page Page is Review with one approval-check mark NO CHANGE

Edit source space page Page in space A

  • Page publishing status is Out of sync in both spaces CHANGED

  • workflow state of target space Page remains in the Review state with one approval-check mark NO CHANGE

Publish source space page Page from space A to target space B

  • Page publishing status changes to Synced in both spaces CHANGED

  • workflow state of target space Page is changed to Draft CHANGED

Publishing is recognized as a page update in the target space, the workflow has an Updated transition in the Review state that listens for this event and transitions the workflow.

Publishing the target space page only causes a change in the workflow applied to a target space page when the current applied workflow state includes an Updated transition.

Changes in the applied workflow do not change the current publishing sync status

  • changing state

  • assigning/unassigning reviewers

  • approving/rejecting the page

  • expiry of workflow state







  • No labels