Conditional startup options in Nintex Workflow 365 migration to NAC

Thank you!

If a workflow needs to be started based on a value change in your SharePoint list from an original value, there are several options to accommodate for this in Nintex Automation Cloud.  These are also alternative solutions to what is available today in Nintex for SharePoint as the Compare to Field function in Conditional settings.

The solution options include starting workflows based on, if:

1. A value difference exists.
2. There is no match.
3. A value exists

Value difference exists

Add a Sharepoint column that calculates the difference between original and new value, using a subtraction formula.  Use this column as the workflow start event.  If there is numeric value in this column, then the workflow starts.

There is no match

Add a Sharepoint column that determines a match between original and new value, using an if/then formula.  Use this column as the workflow start event.  If not a match, then workflow starts (i.e. No).

A value exists

Add a Sharepoint column that checks for a value.  Populate the column with the new value.  Use this column as the workflow start event.  Then null out the value, after the workflow starts, such that a workflow is not started if other fields are changed.

1. Sharepoint list: Create a new column to capture the “Adjusted price”
2. In Nintex Automation Cloud workflow: Adjust the start event’s condition to wait for Adjusted amount to have a value.
3. In NAC workflow: Add a Sharepoint Update items action, and move the value from Adjusted amount to Amount, and null the Adjusted amount in preparation for future changes.