custom ASP.NET web form vs InfoPath -
I have been assigned a project to create a paper based process on a web based basis only. What I need to do is allow the user to fill an online form and sign his / her using the mouse. Data entered and signature should be obtained later in the form of a PDF file.
Therefore, I have created a working prototype using ASP.NET webforms and a third party PDF library (iTextSharp), as well as a mouse signature capture device that I bought.
The prototype works fine but my concern is that I may need to support this application several (maybe hundreds) of forms, each form has different fields, but all of them A signature is required. I took 2 days to create a prototype for a form, create web forms, mark fields in PDF templates, hook web form fields with fields in PDF form, etc ... In the future I do not want to spend every form 2 days to set, is there a better way to make ASP.net's custom image?
I know about the information, but it has never been used, did anybody do anything before that? Is InfoPath with SharePoint a Better Solution of My Problems? Or something else? If someone can give me some advice, then I appreciate it.
Thanks a lot!
The advantage of Infopath is that it has the ability to take advantage of digital ink (handwriting) if the box If your version of Windows includes Microsoft Inc. (XP tablet, Vista, Win 7), then InfoPath will allow you to get text and images based on control and control using various available input devices (mouse, pen etc.) . The text box will use handwriting recognition to convert text to text, where an image box will be ideal for signing a free drawing.
I used Inapath as a standalone disconnected client system, which used to be the email transport arrangement form was earmarked by an email and was added to the Outbox. The form was automatically sent when the user had recovered their email. The good thing about Infopath is that data is xml, what you can do with data, as well as providing you with exciting flexabilty.
As a side note ...
You can think of the legal side of things when people are signing (using handwriting) as e-form InfoPath separates presentation and data to capture data for reporting, workflow etc. It gets negative from legal point of view because data is originally intended to digitally sign the signed signature Can be submitted. In most cases this is not a problem, but if it is any form of legal document (invoice, goods receipt), then you have to think about how to keep both data and presentation together and at the same time Ho.
This will be a problem for any system that separates the data from the presentation, it can be Web based forms, InfoPath or PDF formats.
Hope this helps ...
Comments
Post a Comment