locked
Automatic workflow not starting RRS feed

  • Question

  • Hi,

    I have document library to which the data is submitted using an InfoPath form and a custom approval workflow is created to fire automatically when a new item is created and the workflow creates approval tasks in the Tasks list. Another secondary workflow is created to fire automatically on item creation to send customized email notifications to the reviewers about the approval tasks.

    When the workflow is configured to run manually, the workflow works fine. However, when the workflow is configured to start automatically the workflow remains in "Starting state" and it never changes to "Started" state. When the workflow is triggerred manually on the document library, secondary workflow is firing automatically on Task creation and approvers are getting notified. The problems comes only with the primary workflow attached to the document library based on InfoPath form.

    Both workflows are created by same user account in SharePoint designer and they are not being triggered by system account. Could anybody suggest what could be wrong with the primary workflow?

    Is there any chance where when an item added to the document library from InfoPath form, does it use system account and not causing the workflow to fire? That is the only reason I can think of. One more point that wanted to mention and it may be useful to identify the issue is: As the workflow is still in development, whenever New Document option is selected, the form is opening in InfoPath and not from the browser. So, when the form is submitted it is getting submitted from InfoPath editor, not from the browser. If this also can cause the problem, please suggest how to configure so that 'New Items' can be submitted from the browser.

    We are using MOSS 2007 and the workflows are created using SharePoint designer 2007.

    Thanks in advance,

    Raghu

    Monday, July 4, 2011 6:20 PM

All replies

  • Is the document still checked out when it gets submitted?  The "starting" status typically occurs when a document is submitted but is still checked out, which will happen if 1) you set the form library to require checkout or 2) there is some require metadata missing that forces the document to remain checked out until the metadata is provided.

    Btw, your 2nd workflow must be on the task list and not on the form library, but the way you s aid it was as if there were 2 workflows on the form library that both start on form creation.  Don't you mean the 2nd workflow is on the task list and starts on TASK creation?  You didn't say this, but it is what I believe to be the case.

    As for the InfoPath form, it will open in the browser if you tell it to.  THe form library has an Advanced Setting that says to open in the browser by default, but you must set that settings, because the default setting is to open in the client.  Also, the form template itself must be configured as a browser form.


    SharePoint Architect || Microsoft MVP || My Blog
    Planet Technologies || SharePoint Task Force

    Monday, July 4, 2011 10:35 PM
  • Hi ,

     

    Do you create the workflow with system account .The system account will not trigger  the SharePoint Designer workflow automatically .You can install the Infrastructure update ,and then change the account associated with the workflow by Stsadm  to make it start automatically .

     

    As for the ‘submitted from’ questions, you can set it like this: Open the form library >Settings >Form Library Settings>Advanced settings .Choose 'display as a web page' under Browser-enabled Documents .  Click OK to save the changes.

     

    For more information about the updating , please refer to this site:

    Workflows do not start: http://blogs.technet.com/b/victorbutuza/archive/2009/03/14/workflows-do-not-start.aspx

     

    Thanks,


    Entan Ming
    Tuesday, July 5, 2011 5:02 AM
    Moderator
  • Hi,

    I have verified the document library settings and the setting "Require documents to be checked out before they can be edited?" is set to No and when the document is submitted it is not remaining in check-out status. It does not appear to be the issue with some metadata missing as the document is not remaining in checked-out status after the form is submitted.

    The workflows are not created with the system account. The workflow attached to the InfoPath form based document library and the workflow attached to the Task list created using the same account. The workflow attached to the Task list is firing automatically and the issue is only with the workflow attached to the document library.

    What else could be going wrong with the document library? Please suggest.

    Thank you,

    Raghu

    Tuesday, July 5, 2011 5:47 AM