Microsoft Developer Network > Forenhomepage > SharePoint - Workflow > Very basic workflow cycles over and over and over
Stellen Sie eine FrageStellen Sie eine Frage
 

BeantwortetVery basic workflow cycles over and over and over

  • Dienstag, 30. Juni 2009 14:26Dave Pyett TeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillen
     
    Afternoon all!

    I have created a very basic workflow that runs against a custom list when a item is changed.  This workflow is designed to finalise a change request through a column called Change Status (which cannot be edited by the end users):

    If 'Documented' = No
    Stop workflow and log to history
    Else
    Set Change Status to 'Completed'
    Email assignee with details
    Stop workflow and log to history.

    'Documented' is a simple drop down choice field with Yes|No as the options.

    When I edit an item and select Yes to the Documented field, the workflow kicks in and sends the email.  It then sends another email and another and another............until I manually delete the item by which time, I usually have a hundred or more emails sitting in my inbox.

    I would have thought with the lines (Stop workflow...) it would only ever send 1 email but this is not the case.

    Any ideas?  I'm probably missing something simple here.

    Using: WSS 3.0 and SharePoint Designer 2007
    SharePoint Administrator | SharePoint Fan http://davepyett.wordpress.com - Follow me on twitter: twitter.com/dpyett

Antworten

  • Dienstag, 30. Juni 2009 21:16Stunpals TeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillen
     Beantwortet

    Could you not set the WF to start on creation and then use the Action - Wait for Field to change on current item? You then set the value you are waiting for. This way the WF starts only one time and your user only gets 1 email.

    • Als Antwort markiertDave Pyett Donnerstag, 2. Juli 2009 08:55
    •  

Alle Antworten