Account


Earned badges

Achievement: Latest Unlocked

Topic Started

Topics

For over a year I have been creating packages using a JSON string as the package name (something like "{ApplicationId: 1033}").  I do this because the package name comes through in the event c

I'm using text tag extraction to place a required text field like this:

{{*esl:signer1:textfield}}

We are integrating ESignLive with our ASP MVC site.
I'm trying to send a document for signature using text extraction. It's working, but it's putting an extra signature field in the document that I don't want.

Replies Created

Reply to: Using Field Injection and Signature PositionExtraction together

0 votes
I am having this same problem (without the injected field). I have a pdf file with a field named "[signer1.Capture1]". When I create a package like this:
DocumentPackage documentPackage = PackageBuilder.NewPackageNamed(packageName)               
                .WithSettings(DocumentPackageSettingsBuilder.NewDocumentPackageSettings()                
                )                
                .WithSigner(SignerBuilder.NewSignerWithEmail(signerEmail)
                    .WithFirstName(signerFirstName)
                    .WithLastName(signerLastName)
                    .WithCustomId("signer1")                
                 )
                 .WithDocument(DocumentBuilder.NewDocumentNamed("doc1")                    
                    .FromStream(ms, DocumentType.PDF)
                    .EnableExtraction()                                    
                )
                .Build();
I get the "Cannot send package without approvals" error.

Reply to: Signer Name over lays and hides Captured Signer Signature

0 votes
I was wondering the same thing. Can the text and the signature be vertically (or horizontally) shifted so that both are legible? Incidentally, they seem to be more on top of each other when using text tags to place the signature than when using absolute positioning.

Reply to: Signer Name over lays and hides Captured Signer Signature

0 votes
I'm just following up with this. Making the field larger has no effect on this issue. It would be really nice if the position of the "E-Signed by" text could be specified. The way it is now, both the signature and the text are difficult to read. I'm not sure why this is the default, or why everyone else is apparently ok with it.

Subscriptions

Topics Replies Freshness Views Users

For over a year I have been creating packages using a JSON string as the package name (something like "{ApplicationId: 1033}").  I do this because the package name comes through in the event c

4 4 years ago 264
Profile picture for user Duo_Liang

I'm using text tag extraction to place a required text field like this:

{{*esl:signer1:textfield}}

1 4 years 2 months ago 72
Profile picture for user Duo_Liang
Hi, After signing ceremony, we have pdf file with signatures that is in general active pdf. In this active pdf, customers can view some legal properties that we do not expect in our application.
6 5 years 10 months ago 93
Profile picture for user Duo_Liang
We are integrating ESignLive with our ASP MVC site.
2 6 years 1 month ago 71
Profile picture for user mwilliams
I'm trying to send a document for signature using text extraction. It's working, but it's putting an extra signature field in the document that I don't want.
4 6 years 7 months ago 46
Profile picture for user harishaidary

Code Share

This user has not submitted any code shares.

Subscriptions Release Notes

This user is not subscribed to any release notes.