Reproducing your Comala server workflows in Cloud
Overview
Due to functional differences between the cloud and server platforms, we are not able to deliver 1:1 feature parity between the environments. But we are committed to a cloud experience that offers the same end result as that found in server - effective control and management of documentation.
For this reason, it is not possible to use the migration tool to migrate your existing Comala workflows from server.
You must install and license the Comala Document Management for Cloud app and manually create the Comala workflows in your cloud instance.
Reproducing a Comala workflow
A Comala workflow used in your server or data center instance must be added manually to your cloud instance
You will need to recreate each workflow in Confluence Cloud manually using workflow builder or the code editor.
You can also use the server app workflow builder Workflow Translator for Cloud option (from v6.17.10+) to translate the server workflow into cloud compatible JSON. This code can then be copied and pasted into the app code editor in the cloud app.
There are also a number of Comala Document Management workflows available in Comala Document Management for Cloud
Cloud features and functionality
There will be some functional and feature differences between a Comala workflow in the cloud app and the workflow in the server app.
In the Atlassian Confluence Cloud platform, some features found in the Comala workflow server app workflow are not available or have a different range of functionality in the cloud workflow
for example, there are a different range of events, conditions and action macros available for JSON triggers in cloud
When using the server Workflow Translator for Cloud tool to translate your server workflows into cloud compatible JSON code, feature differences that are not in cloud or have different functionality will not be translated and are listed in a Messages dialog box in Workflow Translator for Cloud.
Some workflow elements and parameters, for example triggers and workflow parameters that are not translated can be created in cloud but have different features and functionality in the cloud platform.
Data migration
When migrating to cloud there is only limited migration of Comala Document Management data.
For example, only the last workflow state data is copied but the document Document Activity (the report that maintains all the approval data per page) cannot be currently migrated.
Additional app installation
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 instance
Read Confirmations will require the installation of the Comala Read Confirmations for Cloud app
If you are using Comala Document Management for Server together with other vendor third party apps, you will need to check with the vendor for the availability and features of the app in Atlassian Cloud.
Maintaining auditable history
If your organization is in a Compliance/Regulatory industry and you periodically get audited, then you will be required to keep Confluence on a server instance so auditors can review your previous document activity/page activity and/or page status.
You cannot migrate the full workflow document activity and page status to cloud.
Current usage of Comala Document Management in server
For help in analyzing your server instance use of Comala Document Management, you can use the server app support console to capture helpful information on your current usage of the Comala Document Management app.
copy and save the Usage data from the Comala Document Migration Assessment global configuration
create an Appfire Comala support package for each space using the Comala support console option in space tools
Please add both the Usage data and the Support package to any support request to the team.