InfoPath Dev

Good afternoon,

I have developed an Infopath Form that submits data into an Access database and also sends an email to a distribution list (which the originator of the form is not on). I was curious if it was possible to have Infopath send a copy of the completed form to the person who filled out the form?

 I apologize, this is in InfoPath 2003.

Thanks in advance for your help!

 Jacob

Sure, it shouldn't be a problem.  You can either use a basic SharePoint Designer workflow or maybe just add another Email Submit data connection.

Whichever way you do it, you basically need to trigger it ONLY when the form is complete.  To do this, simply make sure you have some sort of field (hidden or not) in the form template where you track the status of the form.  I typically control this status through my submit buttons.  I make sure that only certain buttons show at certain times during the workflow, and each one has a different rule set.  Each button click typically sets the workflow status to another state (unless it's a simple data update and not an approval).  Anyway, at whatever point your status reaches "Complete," then on that final button click, have a rule that submits to the email connection you've set for the original user.  The key is getting that user's email address, which you can do by consuming the UserProfileService and getting the WorkEmail node, but that's a SharePoint 2007 feature (MOSS only). I am not sure if InfoPath 2003 is a limitation there.  Regardless, if you have a way to get the originator's email, then you can leverage it in your final submit.

Thank you for the reply!

 And you pointed out exactly where my difficulty lies. Basically I wanted the originator of the form email address automatically placed into the cc: box of the email submit data collection via a programming command or other option. It looks like InfoPath 2003 is unable to glean this information automatically from the end user.

Thanks again!

It's really a shame that your organization is still using Office 2003.  That's your main problem - that is very old technology, and 2010 is already in people's hands.  The best thing to do would be to advance to 2007 before that software is obsolete.

i would suggest to wait for 2010, it is expected to be out in first half of 2010,

so it would be better to skip 2007 and directly jump to 2010.

I highly doubt an organization still stuck on Office 2003 is going to jump right into Office 2010, especially when their users have never seen a ribbon, but if they DID do that, it would be awesome.

well i dont think any organisation would like to buy licences for a software that they know can be replaced after say 6 months. Plus they have not yet found it necessary to migrate to 2007. I know it will be difficult for users to migrate from 2003 to 2010, but they will cetainly cut down the costs

People don't typically buy NEW licenses each time, so that doesn't matter.  Organizations typically have an enterprise agreement that covers all the Office licenses for each user, and they can move up to the next version no problem.  It is extremely unlikely for them to jump 2 versions of Office.