Overview

Comala Document Management Cloud workflows have different features and functionality. When using the Atlassian Confluence Cloud Migration Assistant to migrate to Confluence Cloud or using the Workflow translator for cloud, some hosted workflow elements are not translated to a cloud-compatible workflow:

Workflow elements translated to cloud-compatible JSON

Workflow Translator for Cloud translates the following elements and their parameters of the hosted app workflow into cloud-compatible code.

• Workflow

  • name

  • description (if present)

  • workflow parameters 6.18.0+

  • state

    • name

    • description (if present)

    • final

    • color

    • due date 6.18.0+

  • state transitions

    • select*

    • approved

    • rejected

    • updated

    • expired

  • approval

    • name

    • description ((if present)

    • approve button label (if present)

    • reject button label (if present)

    • credentials 6.18.0+

    • minimum 6.18.0+

    • assignable 6.18.0+

    • user 6.18.0+

    • group 6.18.0+

    • selectedapprover and selectedapprovers 6.18.0+

  • trigger v7.6.3+

    • Workflow triggers are translated based on their designated events, even if some conditions or actions in the trigger are unsupported in the Cloud

    • A trigger is translated regardless of unsupported conditions or actions, which will be omitted from the translation

    • Triggers translated by the tool need to be reviewed in the Cloud environment. They can be adjusted using the Cloud visual editor or code editor to meet specific requirements

What is not translated to cloud-compatible code?

Unsupported workflow elements are not included in the cloud-compatible JSON code translation.

In the cloud, unsupported workflow parameters include

For the workflow

• header parameter

• footer parameter

For a workflow state

• hideselection parameter

  • Hiding a user state selection in the workflow state dialog box is not available in the cloud.

• hidefrompath parameter

  • A state cannot be hidden from the progress bar in the workflow state dialog box in the cloud.

• taskable parameter

  • Workflow tasks, including manual addition by a user, are not supported in the cloud.

• changeduedate parameter

  • By default, the user can edit the due date for a state in the cloud.

Other elements not translated include:

• Read Confirmations are not translated. In Confluence Cloud, read confirmations must be added by installing and using the Comala Read Confirmations Cloud app

The following are translated but have different functionalities in the cloud:

• Workflow parameters

  • Workflow parameters can be created and used in the cloud workflow, but have different functionality from those in the server app workflow.

• Approvals

  • Approvals are available in the cloud, but there are different options for managing reviewers.

• Workflow triggers

  • Workflow triggers are translated into corresponding workflow events in the cloud, but function differently compared to the hosted app.

  • Some trigger events are not supported as there are no corresponding events in the cloud, and they are omitted from the JSON code.

  • Triggers can also include conditions and actions not supported in the cloud. In such cases, while the trigger is translated, the unsupported conditions and actions are omitted.

• Workflow final state

  • The workflow final state has a different functionality from the final state in the cloud workflow. The final state does not add or change restrictions on who can view the workflow draft version content or the workflow approved version content.

• Metadata macros used in triggers

  • Only the set-metadata macro is translated into a cloud-compatible JSON workflow. The get-metadata macro is not translated when included in a workflow trigger, but it is available in the cloud as a page macro to display page metadata values on the document.

Translation of workflow triggers

v7.6.3+

Workflow triggers are available in a cloud workflow, but have different functionality from the hosted app workflow trigger. The Workflow Translator for Cloud translates data center workflow triggers based on their events to their corresponding Cloud trigger event.

However, some data center workflow trigger conditions and actions are unsupported in the Cloud. This does not prevent the trigger translation, but the translated workflow does not include the unsupported conditions and actions. These are omitted from the cloud workflow template. In these cases, you need to review the use of the workflow trigger in the Cloud and the conditions and actions that support your process needs.

This approach simplifies migration while allowing flexibility for future customization and functionality expansion:

In addition, the workflow visual editor in the Confluence Cloud app now includes an option to add and edit a workflow trigger:

Open

Cloud app visual editor - add trigger

Translation of workflow trigger events

The following workflow trigger events are translated into their equivalent Cloud events to align with the Cloud interface and future functionality:

Translation of workflow trigger conditions

Three workflow trigger conditions are available in the cloud.

All other trigger conditions are ignored when translating the workflow to cloud-compatible JSON.

Translation of workflow trigger actions

The following workflow trigger actions are translated into their equivalent Cloud actions to align with the Cloud interface and future functionality:

New workflow trigger actions in the cloud

The following workflow trigger actions are new in the Cloud app and have no equivalent data center workflow trigger action:

• "assign" - assign a Confluence user or Confluence user group as a reviewer for an approval

• "unassign"- unassign a reviewer from an approval

• "clear-expiration" - removes the due date for a state

• "clean-messages" - removes any on-screen message notifications (this action is added to a translated workflow when the body of the data center messages action is empty)

• "clean-labels" - removes all the labels from a page or from the immediate child pages

• "copy-page" - copies the current page as one of a child of the current page, child of a named page, or child of a homepage of a specified space.

Related pages

• Workflow elements and concepts in Comala Document Management Cloud

• Product comparison