Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Excerpt | |||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
OverviewDue to functional differences between the Cloud and Server platforms, we are not able to cannot deliver 1:1 feature parity between the environments. These differences are listed in a feature matrix comparing Comala Document Management Server and Cloud apps product comparison. For this reason, it is not possible to use the migration tool to migrate your the migration tool does not include the migration of existing Comala workflows from Serverthe server instance. You must install and license the Comala Document Management for Cloud and either
Comala Document Management Cloud workflowsin cloudCurrently, some Comala Document Management server app features are not available unavailable 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
Bundled workflowsThere are a number of The workflows available in on installation of Comala Document Management for Cloud
Custom workflowsHowever, 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 builderThese workflows are added to the document management dashboard in all the spaces in the cloud site. Image AddedThese cloud app workflows have different functionalities from the server or data center workflow. Ensure you review the functionalities of these workflows. Custom workflowsCustom workflows in Confluence Cloud are created or added to the document management dashboard in a space using either the A custom workflow in your server instance can be added to your cloud instance by
Workflow translator for cloud
The Workflow Translator for Cloud option (from Comala Document Management for Server and Data Center v6.17.10+) to translate translates the server workflow into cloud-compatible JSON that can be . The translated code is then copied and pasted into the app JSON code editor in a space in the cloud app. Workflow translator for cloud
site. In the server and data center app, a workflow is translated to cloud-compatible JSON code using the Workflow Translator for Cloud option in workflow builder. Image RemovedImage AddedServer/data center workflow features that cannot be translated are listed displayed 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.
Navigate to a space in the cloud site
The space document management dashboard is displayed. Image Added
In the space document management dashboard
The imported workflow is added as an editable custom workflow in the space document management dashboard. Image Added
Cloudduring the remaining quarters of
workflow featuresSome Comala workflow server app features are not available unavailable or have a different range of functionality functionalities in the cloud app. The differences Differences in the cloud app include
Workflow triggers and workflow parameters are available in Comala Document Management Cloud but have different functionalities. You must review the appropriate cloud app documentation and edit the feature using the cloud workflow builder visual editor or code editor. If using the Workflow Translator for Cloud (from Comala Document Management Server v6.17.10+) to create a cloud-compatible workflow template, the workflow translator reports details of the server workflow elements that the tool cannot translate to cloud-compatible JSON code and may need to be added in the cloud app visual editor or code editor. Migration dataDue to Atlassian Confluence platform limitations,
A full history of the workflow events and actions on a page can be migrated as an attachment on the migrated page. Before migrating a space, a space administrator needs to run the Attach Activity option for a space. This attaches a CSV file of the workflow history to the page for audit purposes. Additional appsBased 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
adjust how the workflow works in your Cloud instance
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. |
|
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|