| Excerpt | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
OverviewDue 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 /wiki/spaces/CDML/pages/6674974106. 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. ComalatechComala Document Management workflows inCloudDue to limitations of the Atlassian Confluence Cloud platform, some Comalatech workflowcloudCurrently some Comala Document Management server app features are not available or have a different /wiki/spaces/CDML/pages/6674974106 in Comalatech range of functionality in Comala Document Management for Cloud workflows. For example there are aThe 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
Panel | | ||||||||||||||
|
| Info |
|---|
The workflows bundled with the 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. |
| Panel | ||||
|---|---|---|---|---|
| ||||
|
Bundled workflows
There are a number of Comalatech workflows available in Comala Document Management for Cloud
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
You can also use workflow builder /wiki/spaces/CDML/pages/14257225774 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
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.in the cloud app.
Workflow translator for cloud
| Status | ||||
|---|---|---|---|---|
|
In server, a workflow can be translated to cloud compatible JSON code using the /wiki/spaces/CDML/pages/14257225774 option in workflow builder.
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 /wiki/spaces/CDML/pages/14257225774 tool can be created in cloud, for example triggers and workflow parameters, as these have different features and functionality in the cloud platform. |
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Further functionality is planned to added to the /wiki/spaces/CDML/pages/14257225774 during the remaining quarters of
|
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 /wiki/spaces/CDMC/pages/13929644370, /wiki/spaces/CDMC/pages/13929152981 and /wiki/spaces/CDMC/pages/13929938950 available for /wiki/spaces/CDMC/pages/13928824953
there is no difference in workflow draft and final state content visibility - see Additional app installation
if /wiki/spaces/CDMC/pages/6916310577 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 full /wiki/spaces/CDML/pages/6832983086 (the report that maintains all the approval data per page) 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
adjust how the workflow works in your Cloud instance
if you require users to confirm reading content you will need to install the /wiki/spaces/CRCCL/pages/6915689572 app. In server, workflow builder /wiki/spaces/CDML/pages/14257225774 (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. |
