---
title: "Using workflow translator for cloud"
canonical: "https://support.appfire.com/space/CDML/649857615/Using%20workflow%20translator%20for%20cloud"
format: markdown
---
> Macro (aura-html)


> Macro (excerpt)

## Overview

The **Workflow Translator for Cloud** is an option in the hosted app workflow builder to support your cloud migration.

The tool provides a simple way to recreate a custom workflow from the hosted app as a cloud-compatible workflow for use in your Confluence Cloud site.


> ℹ️ Space workflows are included in the migration to Confluence Cloud. Page workflows are not included, but can be consolidated as a space workflow with a content label filter before migration. Workflow Translator is useful to move a workflow individually to a Confluence Cloud site, for example, in advance of a space migration to test the cloud functionality.

## Translate your hosted app workflow

> Macro (excerpt)
> 
> [Workflow Translator for Cloud](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649924970) is available in the workflow builder in the global workflows dashboard, the space document management dashboard, and from a page when a page workflow is applied.
> 
> > 📝 A global administrator must enable the workflow translator for your hosted Confluence instance.
> 
> In the space document management dashboard:
> 
> - Open the three-dot menu for a space scope workflow
> 
> ![image](media://a971c869-5c56-4f54-af9a-f4694e353ab6)
> 
> Choose **Edit** to open the workflow builder.
> 
> ![image](media://ff128d0b-0da4-4c66-8df6-4eab4606df96)
> 
> Choose the **Cloud Translator** button.
> 
> ![image](media://f49f2d15-9c78-4779-8e55-c6c30f0200fc)
> 
>  The **Actual Workflow** dialog box displays the current server or data center workflow.
> 
> ![cdmc_workflowtranslator_untranslated.png](media://c733ac1a-edd2-460f-9829-882f662ccdd7)
> 
> > ℹ️ Before translating the workflow, you can edit the server workflow markup in the **Actual Workflow** dialog box. Changes made in this dialog box **are retained **when you return to the workflow builder and markup editor in your server or data center app.
> 
> Choose the **Translate** button to translate the server workflow to cloud-compatible JSON code.
> 
> ![cdmc_workflowtranslator_highlightedunsupported_translated.png](media://a44b7248-4cb9-400c-bf28-b354be66a0e3)
> 
> The **Translated Workflow** dialog box displays the cloud-compatible JSON code workflow.
> 
> ![image](media://98a8dac2-735f-43cd-8715-99e44597a430)
> 
> The **Untranslated macros** dialog box displays workflow elements and parameters that the cloud translator has not translated.
> 
> ![cdmc_worklfowtranslator_extract_unsupportedmacros.png](media://f1d64a5a-b7ec-464b-8dc3-51f3723e57bc)
> 
> **Unsupported elements**
> 
> There are some elements and parameters that the workflow translator does not support, which are available in the cloud but have different features and functionality. Some of these, such as triggers, can be added to the workflow in the cloud app visual builder or code editor.
> 
> The workflow translator includes the following warning message about different functionalities in the cloud:
> 
> ![image](media://24d5021b-3408-419d-8711-ddb78fbb42f0)
> 
>  User and group condition parameters in an approval work slightly differently in the cloud, and you should check the functionality by applying a workflow in Confluence Cloud.
> 
> Confluence usernames used in the workflow must be replaced with the corresponding user IDs in Confluence Cloud
> 
> E-signature authentication for an approval reviewer is only available through the use of a time-based token generated by a third-party authentication app. When approval reviewer authentication is required, you need to review whether your system user access processes are compatible.
> 
> > ℹ️ All dialog boxes in the [Workflow Translator for Cloud](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649924970) are scrollable if required to view all the content.
> 
> Copy the cloud-compatible JSON code to the clipboard using the **Translated Workflow** copy icon.
> 
> ![image](media://69c9e784-edce-4419-8737-2b156b3183e6)
> 
> Paste the copied workflow template code into the [JSON code editor](https://appfire.atlassian.net/wiki/spaces/CDMC/pages/2192837873) in the Comala Document Management Cloud app space settings and save it as a new workflow in your cloud site space.
> 
> > 📝 Suppose you copy several templates and save them as text files before adding them to the cloud app. In that case, use a code editor rather than a text editor to avoid the creation of unrecognized characters in the JSON code, such as **“ **(curled) in place of `"` (straight).
> 
> ### Invalid workflow
> 
> A warning message is displayed if the translator cannot translate the hosted app workflow.
> 
> ![image](media://09bce420-2d7e-43f8-a821-3648669ad780)
> 
> Check that the workflow is valid in the hosted app.
> 
> If the error persists, contact [Appfire support](http://appf.re/support).

## Add your cloud-compatible workflow to the cloud

> Macro (excerpt)
> 
> After translating a hosted app workflow into cloud-compatible JSON, this can be copied and pasted into the app [JSON code editor](https://appfire.atlassian.net/wiki/spaces/CDMC/pages/2192837873) in the cloud app instead of creating a new workflow from scratch in the cloud.
> 
> Once added, this workflow can be edited with both the [visual editor](https://appfire.atlassian.net/wiki/spaces/CDMC/pages/2193162438) and the [code editor](https://appfire.atlassian.net/wiki/spaces/CDMC/pages/2192837873).
> 
> - Navigate to the space document management dashboard in the cloud app
> 
> ![cdmc_documentmanagmentdashboard_cloud_bundledworkflows_no_active_wf.png](media://5941002b-0ed5-49d2-93c1-512d72683686)
> 
> - Choose **Create New Workflow**
> 
> ![cdmc_createnewworkflow_visualbuilder.png](media://a4f5538e-b01a-463c-9473-0a4c7cd053ad)
> 
> - Select the **Code Editor** icon
> 
> The **Workflow schema** code for the base two-state workflow is displayed.
> 
> ![cdm_cloud_code_editor_pasted_crewatenewworkflow_base_workflow.png](media://078ee014-c117-4472-8019-50ee1b705635)
> 
> - Highlight all the code in the dialog box and delete it
> - Paste into the empty **Workflow schema** dialog box the copied cloud-compatible JSON code
> 
> ![cdm_cloud_code_editor_pasted_tranalatedworkflow.png](media://bf22c0ef-3edc-4f2a-b201-2e2ff4416c37)
> 
> - Choose **Save**
> - Choose **Exit**
> 
> ![cdmc_documentmanagmentdashboard_cloud_translated_workflow added as custom_wf.png](media://70fccfb7-664b-4b7a-bbe9-e6e1487bdd11)
> 
> The workflow is added to the dashboard and as an option in the workflow picker when adding a page workflow.
> 
> The new workflow does not include any workflow elements and parameters listed in the **Untranslated Macros** dialog box in the hosted app [Workflow Translator for Cloud](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649924970).
> 
> You need to review your cloud workflow and edit it where appropriate to meet your needs in the cloud. You need to
> 
> - Add any features available in the cloud (with different functionalities) that were not translated by the [Workflow Translator for Cloud](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649924970)
> - Review your cloud process where there is a [feature difference between the hosted app and the cloud](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649627126), and the feature is not available
> 
> The workflow, including workflow triggers, can be edited in both the cloud app [JSON code editor](https://appfire.atlassian.net/wiki/spaces/CDMC/pages/2192837873) and the [visual editor](https://appfire.atlassian.net/wiki/spaces/CDMC/pages/2193162438).
> 
> For details of workflow elements that are not translated or that have different functionalities, see: [https://appfire.atlassian.net/wiki/spaces/CDML/pages/2179924396](https://appfire.atlassian.net/wiki/spaces/CDML/pages/2179924396)