Perception is king, too bad it is often misled! If we take a minute to really examine the large majority of line of business applications that we spend time creating, deploying, and monitoring. Many of these applications are designed around the same core requirements which include providing your customer with the ability to capture, retrieve, edit and submit, data to an API, service or storage repository (i.e. a database or content management system). Think about the amount time, money and energy creating the most basic of applications, using technologies like .NET, Java, PowerBuilder VB6, etc.
This where I have spent a far amount of time recommending InfoPath to our customers, only to meet the same objections time and time again. InfoPath is just another technology I have deploy, and support on the client.
So, if InfoPath is so great, then why isn’t everyone using and deploying InfoPath solutions? The most common customer objection to using InfoPath is the requirement to deploy the InfoPath client. In order to fill out an offline form you have to install something on the client. The form requires a container, in other vendor solutions and even your custom solution to provide the common functionality we listed earlier (capture, retrieve, edit, submit). Let’s take a look at a few alternatives and discuss how InfoPath helps to solve the problem of the ever increasing number of applications your call center and IT teams need to support. Consider the following customer scenarios:
Customer “I need an offline solution for people to be able to fill out forms, validate user input and submit when they are back online.”
Response: “InfoPath would be a good solution for you to quickly deploy forms that can be submitted to a web service, database repository or SharePoint form library”
Customer “We are not going to use InfoPath it requires us to install a client on all of the workstations”
Response: “Let’s examine the other options”
· You have to deploy Word/Excel
· The data is not structured and form support in Word/Excel is very limited this is not the best solution for forms.
Build a “quick” app using a technology we already support (.NET/J2EE/PowerBuilder/VB6/Other):
· You have to deploy the app to the client
· You have to build your own shell (again)
· You have to come up with the format for exchanging data and write all the code to submit the data (again)
Purchase another solution like Macromedia or ADOBE eforms:
· You have the deploy the client (and make sure the version of the client installed is the one you intend to target
· You probably already own Office (at least in many corporate scenarios)
· .NET development are on par with Java development (we can argue but what’s the point)
· Integrating the data with other Office applications can be a challenge; InfoPath is part of Office so integration from the suite is very prescriptive
– and no everyone does not have the ADOBE reader (or even the same version already deployed).
We will just use the browser:
· Planning on doing any custom business rules you need to deploy the business rules.
· Planning on supporting anything besides Internet Explorer? You have to deploy the client.
· Scripting is a maintenance nightmare and provides poor support for debugging (especially remote debugging). How many offline browser applications exist today? I agree this is a great solution for online forms but offline forms have a number of challenges when hosted inside a browser for editing.
What about Groove?
· We think Groove is a great solution for offline forms just like we believe InfoPath is a great solution; however there are two challenges today before you determine Groove is the right answer for you:
· Today Groove uses its own form technology that existed before Microsoft acquired Groove Networks. This is yet another programming model you will need to support and it is not the strategic direction for the next release of Groove (2007). The next release of Groove will use the InfoPath form engine.
· You need to deploy the Groove client
The end point here is you are probably deploying to a Windows client, and in many scenarios there is a good chance you are running some version of Office on the client; especially for applications targeting internal users in the enterprise. I have not seen many good offline solutions that do not require at least a one time deployment of a client, to provides a rich management, deployment and a great end user experience for the enterprise. Keep in mind the alternative is to custom develop a solution, which often times lack many enterprise features for management, deployment debugging and security.
Using eForms in offline and online scenarios where I can leverage the capabilities of the client workstation, a tested shell that provides for a great out of the box user experience, XML file formats helps me to deliver value faster to my customers, while lowering the cost for development, deployment and maintenance.
For more information about InfoPath click here.