Workflow migration issues and workarounds

There are common issues that you might face when you are migrating workflows. Given below are some of the common issues and recommended resolutions.

You can also visit Nintex Connect to ask questions, find solutions, and share knowledge about the Nintex platform.

Data type mismatch on workflow configurations

This known issue may occur during a workflow conversion.

Issue and cause

When converting a workflow, the configuration settings may not work as expected and produce workflow conversions issues and errors.

Resolution

If you see this error, check your data types. For example, double versus integer versus number. This could be the source of the issue and changing the settings can help resolve the problem.

Flexi-task action is not supported

Nintex for SharePoint Server provides the Flexi-task action that enables the designer to add complexity to a task. This action is not compatible with Office 365.

Suggested workaround: Use the Assign a task or Start a task process action.

Custom workflow actions are not supported

Custom actions are actions that are not included by default with a Nintex installation. Currently, Nintex for Office 365 does not support custom actions within a workflow design. If you have custom actions within your on-premises workflow, please contact your developer or partner about the best way to replicate this functionality in Office 365.

Workaround: If the custom action connects to a cloud server, use the Call HTTP Web Service or Web Request action to replicate some of that functionality.

This feature has been added to the product roadmap.

Constants and global variables are not supported

Currently, Nintex for Office 365 does not support constants and global variables. There are no contextual settings to handle global constants as it exists in on-premises.

Workaround: Create a SharePoint list to host data and reference the variables that you want within the workflow.

This feature has been added to the product roadmap.