Excerpt | ||||
---|---|---|---|---|
| ||||
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Translate your server workflow to a cloud-compatible workflow
Excerpt |
---|
...
| ||||
Workflow Translator for Cloud 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 Confluence server or data center instance. In the space document management dashboard:
Choose Edit to open the workflow builder. Choose the Cloud Translator button. The Actual Workflow dialog box displays the current server or data center workflow.
Choose the Translate button to translate the server workflow to cloud-compatible JSON code. The Translated Workflow dialog box displays the cloud-compatible JSON code workflow. The Untranslated macros dialog box displays workflow elements and parameters the cloud translator has not translated. Unsupported elements Some elements and parameters the workflow translator does not support 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:
Copy the cloud-compatible JSON code to the clipboard using the Translated Workflow copy icon. Paste the copied workflow template code to the code editor in the Comala Document Management Cloud space document management dashboard 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 Invalid workflowA warning message is displayed if the translator cannot translate the server workflow. Check that the server workflow is valid in the server app. If the error persists, contact Appfire support. |
Add your cloud-compatible JSON code as a workflow schema to your cloud site
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
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.
|