views:

194

answers:

3

How can I Submit an InfoPath form to a SharePoint library AND to an email box at the same time when the user hits SUBMIT?

I need my form to be approved by several users in a particular order; then re-submitted to the SharePoint site, and to another email box so that the next approver can see the approvals, and approve their own, then submit it and have it drop onto Sharepoint again, etc.

The email chain works (the form as an attachment), and the approvals show, but the form doesn't get updated on the SharePoint Form library.

A: 

Sorry for asking but have you considered using a workflow rather then emails? I'm not sure whether the basic workflows in WSS 3.0 will cater for your senario but the MOSS workflow should be more than adequate.

Kasper
A: 

Kasper - yes, I have. But I need the approvals to be made and visible on the form itself, not in the Workflow, where it wouldn't be part of the form. Thanks though :-)

Hey margreet, use the comment function to comment an answer - new answers will be resorted by relevance. So later on it will not be possible to understand the conversation any more. :)
MrFox
A: 

You can add an additional DataSource for submission (send to SharePoint library) and add a rule to your submit button before the save&close rules.

BUT - I would suggest a method that is based on workflows and a form that is held on a SharePoint site. I had a very similar task, where approvals were needed in a staged manner.

If there is a fixed number of approvers, create fields for each one - if the number is not fixed you will need some replacing rules that change the current approver with the next one. Then you will need one (or more) workflows that are triggered by a flag field (or more) that you promoted before. (Make them writable from the outside during publication - the workflow will need that) This field (or fields) trigger the workflow that sends the email. After sending it should clear that flag to avoid infinite looping.

The mail should contain a link to the SharePoint library. And the approver should work on that library rather than sending the XML file through the network.

Hint: Enable versioning on that libary - and you (or the approvers) can keep track of the changes.

Hint 2: If this process will be part of the daily work, maybe a custom view and alerts will help the approvers keep track of the form's status.

MrFox