Wednesday, May 16, 2012 10:25 PM
I'm still a bit new with Sharepoint, but I have been tasked at work with making a site in Sharepoint that I think will include InfoPath and workflows and need some advice on whether or not I can do the things I'm wanting to, and if so, how.
First, a general overview of the process: An employee submits a new product idea using an InfoPath form. When this form is submitted, an ID is assigned and then a second, different InfoPath form is generated. The second form is used by management to evaluate the idea and decide whether to create the product or reject the idea, however, the idea needs to be kept so that it could be looked at again at a later date. If the idea is approved, when the InfoPath form is submitted, one of two things might happen: a workflow kicks off to build a new site specifically for this product which could include multiple folders pre-populated with Word and Excel documents, and finally the two InfoPath forms are moved into the site; or a workflow kicks off that copies a template site which is pre-populated with the necessary documents and structure to a new site for that specific product and then the InfoPath forms are copied in as well. If the idea is rejected, the two InfoPath forms are moved into a different document or form library for archival purposes, an "idea vault", if you will.
Is Sharepoint capable of this level of automation from an InfoPath form and workflow?
Thursday, May 17, 2012 9:30 AM
Sure, but you won't be so new to InfoPath after this job. There are 2 general advices I'd like to give you at this point:
- You can promote InfoPath fields to SharePoint list metadata, influence their values within the InfoPath form and base your workflow actions on that.
- Study the way the InfoPath XML looks after you've filled it in, you'll need it when generating the second, different InfoPath form.
- Marked As Answer by Emir LiuMicrosoft Contingent Staff, Moderator Thursday, May 24, 2012 2:59 AM