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

Unknown macro: {repository-workflow}
Unknown macro: {repository-description}

This workflow performs publishing to a different space, which requires our Comala Publishing App.

  • This workflow implements a QMS workflow for document management.
  • The workflow works in pages with the "qms_approval" label. The label cannot be removed (stickylabel).
  • Remember to create a Confluence group for the approvers of the controlled document and ensure that the the source space is linked to a publishing space
  • Workflow can be amended to use workflow parameter for the approval group rather than creating a specfic Confluence group.
Unknown macro: {workflow-body}
Unknown macro: {workflow}
Unknown macro: {description}

Basic quality management workflow that includes states for both publishing and page obsolescence, and restricts the approval process to a specific Confluence group. Publishes approved pages to a separate space (Comala Publishing App required)

Unknown macro: {state}
Unknown macro: {approval}
Unknown macro: {state}
Unknown macro: {approval}
Unknown macro: {state}
Unknown macro: {state}
Unknown macro: {approval}
Unknown macro: {trigger}
Unknown macro: {set-state}
Unknown macro: {trigger}
Unknown macro: {set-restrictions}
Unknown macro: {trigger}
Unknown macro: {remove-restriction}
Unknown macro: {remove-label}
Unknown macro: {set-message}
Unknown macro: {trigger}
Unknown macro: {publish-page}
Unknown macro: {trigger}
Unknown macro: {set-restrictions}
Unknown macro: {set-label}
Unknown macro: {set-message} This page is obsolete
Unknown macro: {publish-page}

In the updated QMS workflow, e-signature process (if enabled) has been amended to require a user email and a one-time password token generated using a third party 2-Factor Authorization app.

QMS Workflow StateOutline Description

Draft

  • only members of the group controlled_documents_approvers can approve, using user email and a one-time password token (if enabled).
  • if more than one member assigned to the group, all they all must approve.
  • if approved, transitions to In Approval.
  • if rejected, transitions to Obsolete.
  • page can be edited.

In Approval

  • same approval, only members of the group can approve, using user email and a one-time password token (if enabled for the workflow).
  • if more than one user is assigned as members of that group, they all have to approve.
  • page cannot be edited.
  • if approved, transitions to Published.
  • if rejected, transitions to Draft.
  • editions transition to Draft.
  • tasks can be added.
Published
  • the page is published to the target space using Comala Publishing.
  • restrictions still apply.
  • editions transition to Draft.
  • it could transition to In Approval or to Obsolete.
Obsolete
  • qms_obsolete label is added.
  • page cannot be edited.
  • page is published to the target space using Comala Publishing to transfer the new Obsolete state to the published space.
  • restrictions and labels are copied to the page in the target space. 
  • tasks can be added.
  • on-screen message is displayed "This page is obsolete". 

An alternative to including an on-screen message also in the published page in the target space, is to use the macro include-segment.

  • No labels