I am currently in the process of converting a number of workflows from SP2010 to Nintex on SP2013.
As part of this conversion, I am questioning if I should change the logic I have been using.
Our workflows are all approval processes which go through different stages of approval and status until they are completed.
In the past, the way I created them was that there was a single workflow which checked for a status change (using a second text column) and then if the status changed, I executed that if-then statement.
The entire workflow would run every modification.
Now, looking at Nintex with State Machines or even the Switch statements with looping, is it best practice to NOT execute the workflow on every modification but rather have the workflow run on created and use a singular workflow throughout the process?
I have not started testing this out yet but it seems to make more sense to me. I just was trying to see if there were major flaws to using state machine or switch loops vs using a switch loop which runs on the current status every time the item is modified.
Solved! Go to Solution.
State machines for the win!
if your approval process kicks off as soon as your item is created then I would have one workflow and utilise change state action to direct your item through the process based on outcomes inside the workflow.
I LOVE them!
And a Switch is also useful if a workflow is ever terminated by accident or falls over for some reason.
If you use a Switch in a State machine and set the state machine to go to the Switch branch first, you can list your various "States" in the switch so that if an item workflow has been approved, for example, by a director, then a user terminates it mistakenly or something, if the state defines that the workflow has passed the director level approval, you can use your switch branch to set the workflow to go direct to the next stage of your state machine. Something you certainly couldn't do with a linear process.