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

Due to functional differences between the Cloud and Server platforms, we are not able to deliver 1:1 feature parity between the environments. These differences are listed in a feature matrix comparing Comala Document Management Server and Cloud apps.

For this reason, it is not possible to use the migration tool to migrate your existing Comalatech workflows from Server.

You must install and license the Comala Document Management for Cloud and manually create the Comalatech workflows in your Cloud instance.

Comalatech workflows in Cloud

Due to limitations of the Atlassian Confluence Cloud platform, some Comalatech workflow server app features are not available or have a different range of functionality in Comalatech Document Management for Cloud workflows. For example

(blue star) Comalatech workflows bundled with Comala Document Management for Cloud app will have some different functionality compared to those in the Server/Data Center app. If choosing to use one of these bundled workflows, please review its functionality in the Comala Document Management for Cloud app.

(green star) If you require a custom workflow used in your Server or Data Center instance, the workflow must be reproduced manually in your Cloud instance by

  • editing the JSON markup in the markup editor in the Comala Document Management for Cloud app
  • creating a new custom workflow using workflow builder in the Comala Document Management for Cloud app

Bundled workflows

There are a number of Comalatech workflows available in Comala Document Management for Cloud

Custom workflows

However, a custom workflow used in your server instance must be added manually to your cloud instance

You will need to recreate each custom workflow in Confluence Cloud using either the

(warning) Ensure that state names match in both cloud and server. Otherwise the state name in cloud will default to the initial state in the applied cloud workflow.

Cloud workflow features 

Some Comalatech workflow server app features are not available or have a different range of functionality in a Comalatech Document Management for Cloud workflow. The differences in cloud include

  • different trigger events, conditions and action macros available for JSON triggers
  • there is no difference in workflow draft and final state content visibility -  see Additional app installation 
  • if e-signature is enabled for an approval in a workflow a user MUST use a third party authentication app to generate a security token (there is no option to choose to authenticate with their Confluence username and password)

In addition, due to Atlassian Confluence platform limitations, custom content properties are not migrated from Server to Cloud. Only the last workflow state data is copied but the document Workflow History (the report that maintains all the approval data per page) cannot be currently migrated.

(info) We recommend that you involve the process owners and other stakeholders in your organisation in the migration and recreating any workflows.

Based on your migration planning and needs requirements, you may also need to install and configure additional apps. For example, if you require the capability to direct view users to approved content you will need to

  1. use the Cloud Publishing for Cloud app
  2. adjust how the workflow works in your Cloud instance

  • No labels