Recreate your Comala workflow in Cloud using workflow builder or the JSON editor

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 Comala workflows from Server.

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

Comala Document Management workflows in cloud

Currently some Comala Document Management server app features are not available or have a different range of functionality in Comala Document Management for Cloud.

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.

Current feature differences in our cloud app include

• different events and action macros available for JSON triggers in Cloud

• a space in cloud can only have one active workflow

Bundled workflows

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

• Basic Approval workflow

• Content Expiry workflow

• Quality Management Systems Workflow

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

• workflow builder

• JSON editor

Workflow translator for cloud

v6.17.10+

In server, a workflow can be translated to cloud compatible JSON code using the Workflow Translator for Cloud option in workflow builder.

Open

Server workflow features that cannot be translated are listed in the Messages dialog box.

The cloud compatible JSON code can be copied using the Copy button. This can be pasted into the cloud app Code editor in your cloud space.

Cloud workflow features 

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 full document activity 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

1. use the Cloud Publishing for Cloud app

2. adjust how the workflow works in your Cloud instance

if you require users to confirm reading content you will need to install the Comala Read Confirmations for Cloud app.