...
| Note |
|---|
Note: The post-migration report will show a summary of “INCOMPLETE” if any warnings or errors were found during the migration. JSU relies on the JCMA tool to move across any workflows, schemes, resolutions, transitions etc. in order to configure your workflow rules correctly on your Cloud site. |
...
In the above images, you can see that all of our JSU post-functions have been successfully migrated to our Cloud site, but we can see the Linked Transition has a visible error. To deduce why that is we can have a look at the specific configuration of this on our Server site vis Cloud site.
Server:
...
Cloud:
...
As you might be able to see from the above images, our Cloud post-function is missing a value for the “All other sibling issues (for example linking to the target with the same link type) must have one of the following statusesTransition” field, whereas the Server field contains the “Done” transition that has an ID of “31”here.
If you remember our “Missing transition” warning from the post-migration report, it also told us that a transition with ID “31” couldn’t be found. Now that we’ve found the misconfiguration, This is likely to be related to that, so let’s fix it. Let’s have a look at the specific configuration of this post-function on our Server site vs Cloud site.
Server:
...
Cloud:
...
On your Cloud side, edit the misconfigured post-function and add ensure the correct transition values are added to the empty field value “Transition” values (in our case we need to add “Done”the same workflow with transition “Done” and ID “31”) and then save your changes by clicking “Update”.
...
As you can see in the above image, after updating the post-function the error no longer appears. After you’ve resolved all issues on a your workflow, don’t forget to Publish publish your workflow using the options at the top of your workflow screen.
...
…and that’s it! You’ve now successfully migrated to Cloud with all of your JSU workflow rules included! 🎉
...