Kwizcom Forms

Workflow custom form changes in SharePoint 2013

In this post, we will discuss some changes towards custom forms in the workflow in SharePoint 2013. You can also check out my previous posts on:

Create a sequential workflow using Visual Studio 2010 in SharePoint 2010

SharePoint deveopment training course

In SharePoint 2010 for custom forms types like Association Forms, Initiation Forms, and Task Forms, you can use aspx pages or SharePoint InfoPath forms. But in SharePoint designer workflows, the forms are constructed using Infopath forms. But if you are using Visual Studio to create workflow then you can use either InfoPath forms or .aspx forms.

Remember If you want to create a custom association form, then you have to create the two lists that were needed for every workflow association: the task list and history list.

There are two very important changes to workflow forms when creating custom workflows using Visual Studio 2012.

1- SharePoint 2013 introduced client-side object model (CSOM) to provide coverage for the workflow API.

2- All forms should be created as ASP.NET Web Forms rather than InfoPath forms.

Another change in creating custom forms for custom workflows in SharePoint 2013 using Visual Studio 2012 is that developers will only focus on creating two types of forms: custom association forms and custom initiation forms. Task forms have been dropped in SharePoint 2013.

Check out Best Alternative to InfoPath -> Try Now

free sharepoint training

SharePoint Online FREE Training

JOIN a FREE SharePoint Video Course (3 Part Video Series)


About Bijay Kumar

I am Bijay from Odisha, India. Currently working in my own venture TSInfo Technologies in Bangalore, India. I am Microsoft Office Servers and Services (SharePoint) MVP (5 times). I works in SharePoint 2016/2013/2010, SharePoint Online Office 365 etc. Check out My MVP Profile.. I also run popular SharePoint web site

View all posts by Bijay Kumar →