- Created by Robert Alexander Marshall, last modified on Jul 03, 2024
- Mentions
- 0 Associations
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 10 Next »
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, the migration tool does not include the migration of existing Comala workflows from the server instance. You must install and license the Comala Document Management for Cloud and either manually create the Comala workflows in your Cloud site import JSON cloud-compatible workflows from another space or Confluence site translate your server workflows using the server Workflow translator for Cloud and import the workflow using the code editor Currently, some Comala Document Management server app features are unavailable or have a different range of functionality in Comala Document Management for Cloud. Current feature differences in our cloud app include different events and action macros available for workflow triggers application of a space workflow cannot be filtered by content label creating, editing, and importing custom workflows is limited to a space administrator The workflows available on installation of Comala Document Management for Cloud These workflows are added to the document management dashboard in all the spaces in the cloud site. These cloud app workflows have different functionalities from the server or data center workflow. Ensure you review the functionalities of these workflows. Custom 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 manually creating the workflow in the cloud translating the server workflow to cloud-compatible JSON code using the workflow translator for cloud and copying and pasting the JSON code into the cloud code editor in a space Only a space administrator can create, edit, or import a workflow in Comala Document Management Cloud. V6.17.10+ The Workflow Translator for Cloud option (from Comala Document Management for Server and Data Center v6.17.10+) translates the server workflow into cloud-compatible JSON. The translated code is then copied and pasted into the JSON code editor in a space in the 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. Server/data center workflow features that cannot be translated are displayed in the Messages dialog box. use the Copy button to copy the cloud-compatible JSON code Navigate to a space in the cloud site choose Space Settings>Apps>Comala Document Management The space document management dashboard is displayed. The document management dashboard is populated with three workflows bundled with the app. In the space document management dashboard choose Create New Workflow to open the visual editor add a temporary workflow name in the visual editor choose the code editor icon { } highlight the existing code and paste the copied code into the code editor (overwriting the existing code) choose Save choose Exit The imported workflow is added as an editable custom workflow in the space document management dashboard. Some elements and parameters are not translated by the server Workflow Translator for Cloud tool and, if available, must be created in the cloud within the limits of the cloud app functionalities. For example, triggers and some parameters have different functionalities in the cloud app. Some Comala workflow server app features are unavailable or have different functionalities in the cloud app. Differences in the cloud app include workflow triggers include a different range of available some parameters are not supported workflow macro does not include the following parameters workflow state macro does not include the following parameters when enabled for a workflow approval a user MUST use a third-party authentication app to generate a security token There is no authentication option using the user Confluence username and password. only user, group and duration parameter type values can be managed at a space level in the document management dashboard 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. Due to Atlassian Confluence platform limitations custom content properties on a page are not migrated only the last workflow state data is copied but the full document activity data for a page is not migrated 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. Based on your migration planning and needs requirements, you may also need to install and configure additional apps the Cloud Publishing for Cloud app manages page development in a source space, publishing approved pages to a target space the Comala Read Confirmations for Cloud app adds user read confirmationsOverview
Comala Document Management Cloud workflows
Bundled workflows
Custom workflows
Workflow translator for cloud
Cloud workflow features
header
parameterfooter
parameterhideselection
parameterhidefrompath
parameter - current state cannot be hidden from the progress bar in the workflow popuptaskable
parameter - manual addition of workflow tasks by a user in a workflow statechangeduedate
parameter - a user, by default, can edit the due date for a stateMigration data
Additional apps
- No labels