This may be a bit long. I have a list with severla content types. My initial wf would first auto assign a random Admin, and send out communications on all opened items. then send communications each time the status changed. The last action was it would change the status to "Cust Updated" if the submitter made a change. I was receiving many wf failures, so I broke the wf into two separate wf. now wf 1 will run on new item only. this wf will auto assign a random admin and end. wf 2 will only run od changed items and only after the admin field is not blank. the problem is after wf 1 kicks off it runs auto assigns and triggers wf2. but wf 2 runs send first response, changes the status to "Cust Updated" and sends second response. I can not figure out how to make wf 2 hold off until the initial run through. Initiall I had it check if modified <> created and modified by = created by, then change status. but the new wf 1 changes that condition and can not be used. How can i trick the workflow on first trigger not to run?
Stump the Panel » SharePoint Workflow for All Users
Workflow Logic and conditions
(2 posts)-
jaxkookie
MemberPosted 2 months ago # -
jaxkookie
MemberI was able to resolve this issue. When i auto assign I have to add a comment to the comments field, because it is a required field. the message was a simple "this item was automatically assiigned to **" I had the wf check for this comment if it was not there it would trigger the event. works perfectly.
Posted 2 months ago #
Reply
You must log in to post.