Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Excerpt
nameusingtranslator_2

After translating a server workflow into cloud-compatible JSON, this can be copied and pasted into the app code editor in the cloud app instead of creating a new workflow from scratch in the cloud. Once added, this workflow can be updated with both the visual and code editor.

Add the workflow template JSON code

Navigate to the space document management dashboard in the cloud app.

cdmc_documentmanagmentdashboard_cloud_bundledworkflows_no_active_wf.png
  • choose Create New Workflow

cdmc_createnewworkflow_visualbuilder.pngImage Modified
  • 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
  • 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
  • choose Save

  • choose Exit

cdmc_documentmanagmentdashboard_cloud_translated_workflow added as custom_wf.png

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.

You need to review your cloud workflow and edit it where appropriate to meet your needs in the cloud. You need to

The workflow, including workflow triggers, can be edited in both the cloud app code editor and the visual editor.

Unsupported elements

The following elements and parameters in our example workflow were listed in the Unsupported macros dialog box in the Workflow Translator for Cloud.

The following macros are not supported

  • get-metadata

  • set-metadata

The following parameters for the state macro are not supported

  • hidefrompath

  • hideselection

  • taskable

There is no equivalent selectedApprovers parameter in our cloud app. However, the approval is translated to settings in the cloud that only allow selected approvers to undertake the approval. The approval can be checked using the options in the approval editor in the visual builder in the cloud, and it can also be checked when the workflow is applied to a page.

Elements with different functionalities

Triggers are available in Comala Document Management Cloud but with different functionality.

  • a workflow trigger with a supported event in the cloud is translated. However, a trigger with no supported event in the cloud is not translated

  • workflow trigger actions with a supported action in the cloud are only translated if the trigger event is translated.

Some triggers can be translated with empty trigger actions if there is no supported cloud workflow trigger action.

Workflow parameters, although translated in the tool, also have different functionality in the cloud, and these should be reviewed in use and, if required, updated/amended by editing the workflow parameter in the workflow builder visual editor.

The submit transition is not translated directly, but when present in the server workflow, it is created in cloud-compatible JSON code as a select transition with a single destination state.

Info

Atlassian continually updates the capabilities of the Confluence Cloud platform. We are also committed to developing our cloud apps, including translating additional workflow elements and parameters to cloud-compatible JSON code using Workflow Translator for Cloud in our server and data center apps.

...