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. The breadth and depth of capabilities available in our Comala Document Management server was developed over the last 15 years. Development of our cloud app only started a couple of years ago and it will take us a few years to bring our cloud app up to a comparable feature set. Currently some Comala Document Management server app features are not available or have a different range of functionality in Comala Document Management for Cloud. For example there are a different events and action macros available for JSON triggers in Cloud a space can only have one active workflow 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 There are a number of workflows available in Comala Document Management for Cloud 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 Some Comala workflow server app features are not available or have a different range of functionality in the cloud app. 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. 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 use the Cloud Publishing for Cloud app adjust how the workflow works in your Cloud instanceOverview
Comala Document Management workflows in cloud
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.
If you require a custom workflow previously used in your Server or Data Center instance, the workflow must be reproduced manually in your Cloud instance byBundled workflows
Custom workflows
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
We recommend that you involve the process owners and other stakeholders in your organisation in the migration and recreating any workflows.
