Home » sharepoint » SharePoint 2013 » The Business Case for Publishing Electronic Forms with SharePoint Server 2013

The Business Case for Publishing Electronic Forms with SharePoint Server 2013

It may be easier to conceptualize the architecture of electronic forms publishing systems built on SharePoint Server 2013, if the business case for electronic forms is presented first. In a video tutorial titled “The Importance of Forms to Businesses” Darvish Shadravan makes just this point. This video tutorial is included in a set of training content on this topic available for individual and group viewing, SharePoint 2013: Enterprise Forms DVD.

This video tutorial can be very useful to SharePoint 2013 stakeholders looking for content to help drive end user adoption of the computing platform. Our presentation begins with an argument in favor of electronic forms publishing, “Why do forms matter?” Organizations in the public, private, and not for profit sectors can certainly implement paper based, manual forms publishing systems, so a decision to implement electronic forms publishing can certainly be regarded as a step in the direction of adopting, broadly, office automation alternatives for this task.

On the question of “Why do want to do these forms in SharePoint, in the first place?” Darvish Shardravan emphasizes the importance of three features of any successful effort to build a publishing system for electronic forms:

  1. On board support for an organizations unique set of business processes
  2. A simple processing system, easy for end users to consume
  3. and an artifice useful for masking any/all complexity of the form processing system

So SharePoint Server 2013 is a good platform to build forms publishing systems including each of these important features. Further, this video stresses the importance for administrators, developers, designers and architects to adopt this view of what characterizes a highly useful electronic forms publishing system built on SharePoint Server 2013.

Of course, one of the strengths of InfoPath as a forms publishing system were its “views”, which can be used to deliver the same electronic approval system to different Line of Business (LoB) units, but cloaked in a different “skin” as required.

Ira Michael Blonder

© Rehmani Consulting, Inc. & Ira Michael Blonder, 2013 All Rights Reserved