InfoPath forms with Workflows in SharePoint Office 2013

Hello, we are using SharePoint Office 2013 and I need to create workflows, via SharePoint Designer, that include InfoPath forms.  Is there any problems in doing this or any special set up required?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Nope!  Nothing special is required or any other steps.  Sharepoint treats InfoPath documents like any other document (which just happens to have the ability to write to SP lists).

One caveat you should be aware of is that Microsoft has (prematurely) announced the death of InfoPath.  MS will no longer support InfoPath in the Fall of 2016.  

InfoPath is a great tool for rapid application development, but if you are considering a long term solution you may want to look into Visual Studio designer

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
j_heckAuthor Commented:
TAD,  thanks for the update on InfoPath.  So you can build forms in Visual Studio designer (do you find this in visual Studio 2013?) and use them in SharePoint as well as in SharePoint Workflow?

Yes, you can develop a form using visual studio developer.  It is similar to infopath, but with a lot more features.  We've hit a couple of challenges trying to avoid infopath.

1) cost of visual studio license is much higher than infopath
2) Infopath was basic enough that a tech-savy non-IT person could use it.  Visual Studio is a lot more complex.

The end result is that we now use a lot of Site Content Types.  It's not as pretty as a custom form from infopath, but it's all native to sharepoint and will not be depricated
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.