Page Comparison

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 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 workflows available in Comala Document Management for Cloud

Excerpt

Table of Contents

maxLevel	4
minLevel	2
absoluteUrl	true
exclude	See also
type	flat
separator	pipe

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

You must install and license the Comala Document Management for Cloud and manually create the Comalatech 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. 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

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

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.

Info
The workflows bundled with the Comala Document Management for Cloud app have different functionality compared to the bundled workflows in the server/data center app. Please ensure you review the functionality of these workflows in 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

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

You can also use workflow builder Workflow Translator for Cloud option (from v6.17.10+) to translate the server workflow into cloud compatible JSON that can be copied and pasted into the app JSON editor in the cloud app.

Workflow translator for cloud

Status

colour	Green
title	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.

Image Added

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.

Info
Some elements and parameters not translated by the server Workflow Translator for Cloud tool can be created in cloud, for example triggers and workflow parameters, as these have different features and functionality in the cloud platform.

Panel

bgColor	#EAE6FF

Further functionality is planned to added to the Workflow Translator for Cloud during the remaining quarters of

Status

colour	Green
title	2023

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 Workflow History (the report that maintains all the approval data per page) full document activity cannot be currently migrated.

Tip
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

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

Image Removed

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

In server, workflow builder Workflow Translator for Cloud (from v6.17.10+) will include any details of the server workflow that cannot be translated to cloud compatible JSON code. These features may be available in cloud, for example triggers, but with different functionality. You will need to review the appropriate cloud app documentation and manually add the feature to your cloud workflow in the cloud workflow builder or code editor.