OneSpanSign.Sdk.Builder

I see, the PDF you provided is using document extraction feature, see the attachment where there are two PDF form fields with specific property name. If you modified these two form's name to:
[Signer.Fullname1]

[Signer.Fullname1.label1.Date]

This will switch the signature type to click-to-sign.

Duo

Hi Alfredo,

Thanks for your post! If you are developing with .NET sdk and trying to add signature of different types, use code around below lines:

DocumentPackage superDuperPackage = PackageBuilder.NewPackageNamed("Test Package .NET")
 .WithSigner(SignerBuilder.NewSignerWithEmail("[email protected]")
       .WithFirstName("Signer First Name")
       .WithLastName("Signer Last Name")
       .WithCustomId("Signer1"))
 .WithDocument(DocumentBuilder.NewDocumentNamed("sampleAgreement")
       .FromStream(fs, DocumentType.PDF)
       .WithSignature(SignatureBuilder
         .SignatureFor("[email protected]")
         .OnPage(0)
         .AtPosition(175, 165))
       .WithSignature(SignatureBuilder
         .InitialsFor("[email protected]")
         .OnPage(0)
         .AtPosition(175, 265))
       .WithSignature(SignatureBuilder
         .CaptureFor("[email protected]")
         .OnPage(0)
         .AtPosition(175, 365))
       ) 
       .Build();    

Duo

Too bad. I was trying to get away from doing .AtPosition(175, 165). My code automatically knows where the signature goes and the only issues is that it only comes as drawing. Should it ask what you prefer automatically?

Hi Alfredo,

I see, in that case, you are using automatic extraction methods, like Text Tags, Document Extraction, Position Extraction, and Text Anchor.

Can you provide a screenshot of your document where you have added the text tag or PDF form?

Duo 

Here is the PDF