Is "Wait for field change in current item" effective?
- Hi everyone,
I have step1, step2, and step3 fields. When the step2 becomes "complete", I want to send out emails. Pretty simple. What I am debating is.. among two possible ways, which one doesn't slow down the speed?
1. Start WF when an item is created and do "Wait for field change in current item" (wait for Step2 to become complete) and send out emails
2. Start WF when an item is changed and check Conditions (If Field Equals Value) and send out emails.
Two things to consider is that it could take a couple months from the creation of item to go to "step 2 complete" state (not good for solution1). Another thing is that data in other fields gets changed quite often (not good for solution2).
Which one would you go for?
Thanks..
Antworten
- I am using Start WF when an item is created and the "Wait for field change in current item" in several work flows that sometimes wait up to three months and I have had no problems. They have been in use now for over a year.
I stopped using "Start WF when a item is change" (except for a few WF's) because it is easy to get the Work Flow stuck in a loop.- Als Antwort markiertbevan wangModeratorDienstag, 16. Juni 2009 10:28
Alle Antworten
- I am using Start WF when an item is created and the "Wait for field change in current item" in several work flows that sometimes wait up to three months and I have had no problems. They have been in use now for over a year.
I stopped using "Start WF when a item is change" (except for a few WF's) because it is easy to get the Work Flow stuck in a loop.- Als Antwort markiertbevan wangModeratorDienstag, 16. Juni 2009 10:28
The article How to wait for a change in any list, wait for multiple field changes the current item for a different take on waiting for field changes in the current item.
The article explains how to configure a workflow which uses Standard (OOB) workflow actions and is developed using SharePoint Designer. Instead of using the "Wait for field change in the current item" action, the components of the workflow which are completed after waiting is finished are added to a separate "On Change" workflow, which uses standard conditions in the first step to determine if it can continue. If the conditions are not met for the field in the current item, the workflow will stop. If another instance of the workflow is running, new instances will also stop by setting a "Workflow_running" field to yes while an instance is running.
Using this technique gives you more control when waiting for specific criteria to be met. This includes being able to wait until a field in another list item is updated, or waiting for multiple fields in the current item.
See How to wait for a change in any list, wait for multiple field changes the current item (SharePoint Workflow) for more details.
Blogs: SharePoint Development | Web Development & Programming | Webmaster resources & free SEO- Als Antwort vorgeschlagendsoutter Samstag, 28. November 2009 08:10
