Question : Saving values in InfoPath Form/WWF workflow application for later use

I have a WWF workflow that is pretty simple - it has only one submission form and one processing form.  The flow itself works fine.  When the task form is utilized, the processor enters values and can select to submit the form and the workflow is complete.

The problem lies in the procedural timing.  Of the values to be entered by the processor, he may some field values this week and the remaining values next week or later.  This being the case, the processor needs to be able to enter values into the form at different days/times.  Whenever he pulls up the form, he wants to see all the previous values he entered.

Obviously, the workflow must pause at this time and not continue to conclusion.  I current have a "submit" that does a standard submit (using a data connection) and closes the form.  But this option closes the workflow.

I have built a "Finish Later" button that closes the form but doesn't do a submit.  As expected, it keeps the workflow alive but doesn't save the fields' value.  How can I get the best of both worlds?

I see an option in the Rules to "Set a Field's Value" - I tried using that but I doesn't fully understand what values to use to define the saving of this form data.

Any help will be appreciated.

Thanx!

Answer : Saving values in InfoPath Form/WWF workflow application for later use

Yah that is it.

You could have two buttons like you described Save and Submit or something or there may be some fields that do not complete until it is ready and then the same button can be used but conditionally the complete is set by the condition of other data.

Then update your workflow to look at the status as well before executing.