ASP.NET Custom Web Form vs InfoPath

I just assigned a project to make the paper process a website. I need to do so that the user can fill out the online form and sign it with the mouse. Entered data and signature should later be obtained as a PDF file.

So, I created a working prototype using ASP.NET web forms and a third-party PDF library (iTextSharp) along with the mouse signature capture tool that I purchased.

The prototype works great. But I'm worried that I might need to distribute this application to support many (maybe hundreds) of forms. Each form has different fields, but they all require a signature. It took me 2 days to create a prototype for one form, including creating web forms, marking fields in PDF format, connecting fields of web forms with fields in PDF format, etc. .... In the future I do not want to spend 2 days to customize each form, is there a better way than creating a custom form using ASP.NET?

I know InfoPath, but never used it, has anyone done anything like this before? Is InfoPath with SharePoint the best solution to my problem? Or something else? If anyone can give me some advice, I would really appreciate it.

Thanks a lot!

+3
source share
3 answers

The advantage that infopath has is that it has the ability to use digital ink (handwriting) out of the box. if your version of Windows includes Microsoft Ink (tablet XP, Vista, Win 7), then Infopath will allow you to record text and images using various input devices (mouse, pen, etc.) depending on the control you are using. The text box will use handwriting recognition to convert text to text, where a free drawing will be allowed as an image window, perfect for caputring signatures.

Infopath , . "". , . , - xml. , .

...
, ( ) . Infopath , , .., , -, , . , (-, ), , , .

, , -, PDF-.

, ...

+1

​​ . , Adobe LifeCycle, SharePoint ECM. InfoPath , SharePoint InfoPath. SharePoint SharePoint, InfoPath . , , html-, , ... , , InfoPath . Adobe LifeCycle , PDF , . Adobe LifeCycle , .

, SharePoint , . , , InfoPath, SharePoint, .

0

@ sean717: you come up with itextsharp, which reminds me of an existing tool that we use in our company. Check out www.pdfsharepoint.com if you want both highly interactive PDF forms and integration with SharePoint 2010. It works for us.

0
source

Source: https://habr.com/ru/post/1720514/


All Articles