Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
The workflows bundled with the Comala Document Management for Cloud app have different functionality compared to the bundled workflows in

These cloud app workflows have different functionalities from the server/data center

app

workflow.

Please ensure

Ensure you review the

functionality

functionalities of these workflows

in cloud

.

Custom workflows

However, a 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
  • importing a workflow

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 . This translated code is then copied and pasted into the app JSON editor in a space in the cloud appsite.

Workflow translator for cloud

Excerpt
Table of Contents
maxLevel4
minLevel2
absoluteUrltrue
excludeSee also
typeflat
separatorpipe

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 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

  • manually create the Comala workflows in your Cloud

instance.
  • 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

Comala Document Management workflows in cloud

Currently, some Comala Document Management server app features are not available 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 JSON triggers in Cloud

  • space workflow application can not be filtered by content label

The breadth and depth of capabilities available in our Comala Document Management server was were developed over the last 15 yearstwo decades. 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 we are actively developing the cloud version to create the cloud app with a comparable feature set .

Current feature differences in our cloud app include

  • different events and action macros available for JSON triggers in Cloud

  • a space in cloud can only have one active workflow

to the server app.

Bundled workflows

There are a number of several workflows available in on installation of Comala Document Management for Cloud

Info
Status
colourGreen
titlev6.17.10+

In the server and data center app, a workflow can be is translated to cloud-compatible JSON code using the Workflow Translator for Cloud option in workflow builder.

Image RemovedImage Added

Server/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.

  • 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.

cdmc_documentmanagementdashboard_bundledworkflows_noneactive.pngImage Added
Info

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

cdmc_workflowbuilder_visualeditor_createnewoworkflow_emptyname.pngImage Added
  • choose the code editor icon { }

cdmc_codeeditor_cretenewworkflowschema_highlighted.pngImage Added
  • 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.

cdmc_documentmanagementdashboard_bundledworkflows_plus_newcustomworkflow.pngImage Added
Info

Some elements and parameters are not translated by the server Workflow Translator for Cloud tool can and, if available, must be created in the cloud within the limits of the cloud app functionalities. For example, for example triggers and workflow some parameters , as these have different features and functionality functionalities in the cloud platform.

Panel
bgColor#EAE6FF

Further functionality is planned to added to the Workflow Translator for Cloud during the remaining quarters of

Status
colourGreen
title2023

app.

Cloud workflow features 

Some 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

  • 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 workflow JSON triggers include a different range of

  • some parameters are not supported

    • workflow macro

      • header parameter

      • footer parameter

    • workflow state macro

      • hideselection parameter

      • hidefrompath parameter - current state cannot be hidden from the progress bar in the workflow popup

      • taskable parameter - manual addition of workflow tasks by a user in a workflow state

      • changeduedate parameter - a user, by default, can edit the due date for a state

  • e-signatures

    • when enabled for a workflow approval 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)

Migration data

In addition, due to Atlassian Confluence platform limitations,

  • custom content properties on a page are not migrated

from server to cloud. Only
  • only the last workflow state data is copied but the

document cannot be currently migrated
  • 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.

Tip

We recommend that you involve involving the process owners and other stakeholders in your organisation in the migration and recreating any workflows.planning including the recreation of a workflow in cloud.

Additional apps

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 Cloud Publishing for Cloud app to manage page development in a source space, then publish approved pages to a target space

    • adjust how the workflow works in your Cloud instance

if you require users to confirm reading content you will need to install

In the server/data center app, workflow builder Workflow Translator for Cloud (from v6.17.10+) will include any includes details of the server workflow that cannot be translated to cloud-compatible JSON code. These

Some of these features may be available in the cloud , for example app. For example, workflow triggers, but are available with different functionalityfunctionalities in the cloud app. You will need to must review the appropriate cloud app documentation and manually add the feature to your cloud workflow in using the cloud workflow builder visual editor or code editor.