Form Status Change Update - Best Practice - InfoPath Dev
in

InfoPath Dev

Form Status Change Update - Best Practice

Last post 04-21-2013 09:41 AM by Patrick Halstead. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 04-19-2013 07:39 AM

    Form Status Change Update - Best Practice

     All,

     I'd be interested to hear 'best practice'  to update a Form Status field. Virtually all of my forms have a workflow attached, normally to send emails.

     If a form has for example 5 stages - Initial Submission (field default value),Employee, Accounts, HR, Complete.

    When is it best or how to update the field?

    Normally I update the field status when a button (submit) is pressed. Yet, quite often you can press the button, it updates the form staus field, yet the workflow attached to the list or library isn't as quick and can quickly be left behind, especially if you manually go through a form to reach the end so a group of people down the line can access the form.

     Thanks

    W

  • 04-21-2013 09:41 AM In reply to

    Re: Form Status Change Update - Best Practice

    Hi W,

    Not sure I understand your last clause: "so a group of people down the line can access the form."

    Best practice is to have a submit or save buttons set the status value and then submit the form.

    The workflow will have a step for each status value with conditions so that multiple steps don't run. In other words, you want to only execute the workflow logic associated with a given status. Perhaps this will prevent your form from getting ahead of itself. :)

    Patrick Halstead
    Project Manager at Qdabra
Page 1 of 1 (2 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.