Page Comparison

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

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. Comalatech Comala Document Management workflows in CloudDue to limitations of the Atlassian Confluence Cloud platform, some Comalatech workflow cloud Currently some Comala Document Management server app features are not available or have a different range of functionality in Comalatech Comala Document Management for Cloud workflows. For example there are a 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 Comalatech workflows bundled with different events and action macros available for /wiki/spaces/CDMCD/pages/13929807873 JSON triggers in Cloud a space in cloud can only have one active workflow
Panel
borderColor #EDFEF9 bgColor #EDFEF9

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

• workflow builder

• JSON editor

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.

Workflow translator for cloud

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.

Cloud workflow features 

Some Comalatech Comala workflow server app features are not available or have a different range of functionality in a Comalatech Document Management for Cloud workflowthe 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 server to Cloudcloud. Only the last workflow state data is copied but the document Workflow History (the report that maintains all the approval data per page) 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