With Web GUI and PDF forms, what you can apply is Document Extraction feature. And you only need to change your PDF form property name to fit the Document Extraction.
Signers added through GUI will follow the signer name of signer1/2/3/4, which can be exactly recognized by Document Extraction Naming Syntax.
For example, you can set your PDF form property name [Signer1.Fullname1] or [Signer1.Fullname1.Textfield1] binding to the first signer you added via GUI
And don’t forget to enable Document Extraction feature at your account level by contacting our support team at firstname.lastname@example.org. With this setting, all your document forms will be detected for document extraction by Doc Engine in default.
Thanks for your quick reply. In our system I have to implement esign feature. We have almost 100+ pdf forms in our system. If I use OneSpan API do I need to create all this PDF from scratch or I can do some modification in existing PDF’s.
Some of the PDF’s contains custom logic and generated by code.
This reply was modified 4 months, 3 weeks ago by lakhan.
If using API/SDK, it’s more flexible for you to handle PDF forms.
You can use Position Extraction Feature to location your PDF form without changing its name.
Or you can also consider using Text Anchor to use existing texts on your pdf.
And of course, you can use Document Extraction feature if you are able to modify your PDF forms’ property names.