Tuesday, March 27, 2012 6:20 PM
The above is a workflow in Sharepoint 2007
Late Date is set by the workflow to be 1 day later than the due date (currently it is set to 5 minutes for testing purposes). It is the field that is used to trigger when the late notification is sent out.
Date Counter is a field that is updated by the workflow to monitor the passage of time. On initial creation Date Counter is set to Create Date. On modification, Date Counter is set to modified date. The workflow compares Date Counter to the Due Date. If it Date Counter is less than Due Date, the workflow then sets it to the Due Date and pauses until due date. If the Date Counter is equal to the due date and status is not complete, it sends an email indicating the task is due. If the due date counter is greater than or equal to the late date and the task isn’t complete, it sends a notice the task is late.
When run, I get the first e-mail when due date is reached and also the second e-mail when late date is reached. But subsequent e-mails which must be sent evry 5 mins is not being sent. (The late date and date counter are incremented by 5 mins. each time). NOT SURE WHY ??
- Moved by Entan MingMicrosoft Contingent Staff, Moderator Thursday, March 29, 2012 6:34 AM sharepoint 2007 workflow (From:SharePoint 2010 - Using SharePoint Designer, Infopath, and other customization)
Wednesday, April 11, 2012 4:56 AMIS your due date field capturing the date and time or date only? This will determine why your counter is not working
Friday, April 13, 2012 2:26 PM
The following e-mails aren't sent because you're running into an issue that was fixed with a service pack in SharePoint that prevents workflows from starting themselves again. This is called looping and is no longer permitted in SharePoint. The best resolution for you is to create a machine state workflow that will loop within the workflow until it meets the condition to complete.
This is documented here:
Considerations & Limitations
If Service Pack 2 or higher has been installed on the servers hosting SharePoint, workflows will function different to an environment at the SP1 level or less as after SP2, an "On Change" workflow won't re-initiate itself when the current item is modified. This can affect looping workflows, as they may have been configured to loop by updating the current item. The looping workflow solution detailed below should work on servers with or without SP2 installed.
If I have misunderstood what you are trying to accomplish, please let me know.
Scott Heim - Microsoft Office InfoPath and SharePoint Designer Online Community Support