Versions Compared

Old Version 4

changes.mady.by.user Robert Alexander Marshall

Saved on

compared with

New Version 5

changes.mady.by.user Alain Martínez

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
maxLevel3
minLevel2
absoluteUrltrue
excludeSee also
typeflat
separatorpipe

Overview

This is an initial release of our Workflow Translator for Cloud. Further versions will have greater capability. For example, support for the translation of further server workflow elements and parameters to cloud compatible JSON code.

Excerpt
namecloudtranslator_wfb

A data center/server workflow can be translated into cloud compatible JSON markup using the workflow Workflow Translator for Cloud available in workflow builder.

Image RemovedImage Added
Info

This feature can be disabled and hidden from the workflow builder by setting the following dark feature: comalatech.workflows.migration.translator.enabled

The workflow cloud compatible JSON can be copied and then added to a cloud site space using the app workflow code editor in cloud.

As some product features in Cloud are different to data center/server, the workflow builder cloud translator will not translate all the elements and parameters of the data center/server workflow into a cloud compatible JSON workflow.

...

Info

Some elements and parameters of the server workflow may not be cloud JSON compatible.

Select the Copy button icon on the Translated workflow box title to copy the workflow cloud compatible JSON code to the clipboard.

...

Excerpt
nametranslatedelements

  • Workflow

    • name

    • description (if present

    • state

      • name

      • description (if present)

      • final

      • color

    • state transitions

      • select*

      • approved

      • rejected

      • updated

      • expired

    • approval

      • name

      • description ((if present)

      • approve button label (if present)

      • reject button label (if present)

Panel
bgColor#EAE6FF

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

What is not translated to cloud compatible

...

code?

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

...

Workflow JSON code triggers can be created and used in a cloud but these have different functionality to those in server.

Metadata and other values references are not translated.

In cloud, unsupported parameters include

Excerpt
nameunsupported_parameters

For the workflow

  • header parameter

  • footer parameter

For a workflow state

  • hideselection parameter

    • cannot be hidden from the progress bar in the workflow popup

  • taskable parameter

    • manual addition of workflow tasks by a user is not supported

  • duedate parameter

    • manual addition of an expiry due date for each state using workflow builder in cloud

  • changeduedate parameter

    • user by default can edit the due date for a state

For a workflow approval

  • credentials parameter

    • requirements for user authentication using an e-signature can be added for each approval in cloud workflow builder

  • assignable parameter

    • each approval can be set as Users can be assigned through UI in cloud workflow builder or code editor

Read Confirmations are not translated in the cloud compatible code. In a cloud site, read confirmations are added using the Comala Read Confirmations Cloud app.

Use workflow translator

Insert excerpt
MIG:Use Workflow Translator for Cloud in server to create and copy your server workflows to cloud
MIG:Use Workflow Translator for Cloud in server to create and copy your server workflows to cloud
nameusingtranslator_1
nopaneltrue

See also

Comala Document Management Cloud