Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I have two SharePoint Designer 2007 workflows associated with a "Request" list.

The first workflow automatically fires whenever a new request is submitted and sends an email to the requester.

The second workflow automatically fires whenever an existing request has been modified, sending a different email to the requester.

I have a hidden field on my list that I am using as a sort of "dirty bit". In my first workflow, I'm using the "Set Field Value" action to initialize the value. Once this workflow sets the field value, it actually causes the second workflow to be triggered.

I have been trying to come up with a way to prevent this from happening but I've yet to come up with a solution. Please keep in mind that these are Designer Workflow and I am unable to use any sort of coded solution.

Thanks in advance,

Will

share|improve this question
add comment

1 Answer 1

You have to put in some logic on the change workflow to exit appropriately as well as edit your dirty bit field appropriately.

Your on start workflow sets the field, then your on change workflow needs to check against that and escape, presumably if the field is set and the modified by person is the creator (since the on creation workflow executes under the context of the person who creates the item). If that is the case the workflow terminates, if it isn't, then the workflow would email out and then set your dirty bit flag to completed. If the workflow refires and it sees the dirty bit flag is complete, then it terminates.

You basically have to build in exit conditions into your flag and have the on change workflow evaluate it before sending the email.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.