I am using SharePoint and Nintex 2010. I have a list that has this workflow attached to it. The workflow is set to run if there is a new item created or an item that is modified. When an item is modifed or added, I check in the workflow for a certain condition. When the condition is true, it sends a notification, changes the workflow status, changes a status field in the list and then ends the state machine. This workflow is running twice instead of once so I am getting two emails instead of one. How can I prevent this? Thanks!
Could you specify a condition in the workflow settings when the workflow should start on modified? So instead of Yes, start on modified, choose a condition and set it on something other than status field.
Other options could be to have a pause as the first action so that all changes are committed first. Then have your condition as the following action to make sure it is not run twice.
Currently it is set up to run conditionally - when status = Submitted. I have a state machine. The first state is 'Submitted'. I can't change those two things or it will mess up the way other things work. In the 'Submitted' state, I am checking the value of a field.....which is where the email notification gets sent.
Lisa, does this have to be solved by using a workflow? Can't you put some logic into your form that checks the same? Then you could output a message above the form with some text explaining they forgot to fill in a certain required field.
Exactly, in a Nintex from you can create cascading drop downs and validate a field is required without the list defining the field as required using validation on the control, or a Validation Rule. In the validation you can specify a Message to appear to the user immediately at the top of the screen so they can make the changes then. Using a workflow would seem to hinder the user experience.
This link shows how to use a validation rule to make sure a comments box is not empty before submission on a task form.