...
Excerpt | ||
---|---|---|
| ||
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 codeNavigate to the space document management dashboard in the cloud app.
The Workflow schema code for the base two-state workflow is displayed.
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 elementsThe 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
The following parameters for the state macro are not supported
There is no equivalent Elements with different functionalitiesTriggers are available in Comala Document Management Cloud but with different functionality.
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.
|
...