| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
Due to functional differences between Because the cloud and server platforms , we are not able to deliver 1:1 work differently, they can't have the same features. Exact 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.
...
is not possible.
...
Because of these functional differences, the Atlassian Migration Assistant cannot migrate existing workflows from the server instance.
You must install and license the Comala Document Management for Cloud app and , use one of the bundled workflows, or manually create the Comala workflows a workflow in your cloud instance.
Reproducing a Comala workflow
Workflows bundled with the Cloud app
There are several Comala Document Management workflows available in Comala Document Management for Cloud
These workflows have some feature equivalence to the similarly named workflows found in the server app but have feature and functional differences in the cloud environment.
Custom workflows
A customized Comala workflow used in your server or data center instance must be added manually to your cloud instance You will need to recreate each as a custom workflow.
a custom workflow in Confluence Cloud
...
is created using the workflow builder visual editor or the code editor
...
...
a server workflow can be translated to a cloud-compatible JSON code template using the server app
...
...
tool (from v6.17.10+)
...
. This workflow template code can then be copied and pasted into the
...
code editor in the cloud app
...
There are also a number of Comala Document Management workflows available in Comala Document Management for Cloud
the included cloud workflows can be duplicated and the copy edited using the visual editor or the code editor to create a new custom workflow
Cloud features and functionality
There will be are 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 workflow 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.
...
.
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 in your Cloud instance
Read Confirmations will require Adding a read confirmation request requires the installation of the Comala Read Confirmations for Cloud app.
If you are using Comala Document Management for Server together with other vendor a third-party appsapp, you will need to check with the vendor for the availability and features of the app in Atlassian Cloud.
Maintaining auditable history
When migrating, there is limited migration of Comala Document Management app 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 migrated.
The full history
...
of workflow events and activity for a page and the page status cannot be migrated to the cloud and available within the applied cloud workflow.
For an organization in a Compliance/Regulatory industry
...
that includes a periodic audit, you can
keep Confluence on a server instance so auditors can review your previous document activity/page activity
...
or page status
...
...
use the server Attach Activity utility option in each space before migration to create and add the page workflow history as a CSV file attachment to each page. This record is not accessible by the cloud app
Current usage of Comala Document Management in server
| Excerpt | ||
|---|---|---|
| ||
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
...
|
...
|
...
 |
...
Add the Usage data and the Support package to |
...
a related support request |
...
. |