This site has moved to the integrated Appfire documentation and information site for our apps.

From February 2024 this site is no longer updated.

Take a look here! If you have any questions please email support@appfire.com

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

What is migrated to Cloud?

Only the following is migrated with the Confluence Cloud Migration Assistant

  • current workflow status of each page

  • an entry in the workflow history

Any document that had a workflow applied while being in server,  in each cloud space will have

  • a lozenge added to the content in cloud showing the current workflow status

  • an entry on each document’s workflow history saying "Document has changed to 'xxx' state"

Migration adds the last workflow state in server an attachment to the document in cloud.

These will be present as long as document has been properly migrated using the Atlassian Migration process and the linked user exists in the cloud site.

What is not migrated to cloud?

The following is not included in the migration

  • workflows 

  • full page activity (the workflow history)

  • expiry date(s)

  • assigned approvers

  • assigned read confirmations

  • record of which page version was the final state

  • any metadata set or retrieved by get-metadata and set-metadata macros and workflow parameters

When migrating to Cloud

Each workflow in server can be translated to cloud compatible JSON code using the /wiki/spaces/AWPD/pages/14256308236 option in workflow builder (from Comala Document Management v6. 17.10+). The code can be copied and pasted to the workflow Code Editor in a cloud site space.

0

0

  • No labels