Account
I am a
Developer
Product(s)
Earned badges
Achievement: Latest Unlocked
Replies
Topics Started
Preferences
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 callba |
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
Monday, September 10, 2018 at 05:06amI 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
Thursday, February 22, 2018 at 08:53amI 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
Friday, May 25, 2018 at 04:12amI'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.
Reply to: Text Extraction is creating an extra signature field
Thursday, December 14, 2017 at 05:37amGot it. Thanks!
Reply to: Signer URL not working on Mac
Thursday, May 24, 2018 at 02:23amI tested on macOS version 10.13.3, Safari version 11.0.3. Thanks!
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 callba |
4 | 3 years 10 months ago | 251 |  |
I'm using text tag extraction to place a required text field like this: {{*esl:signer1:textfield}} |
1 | 3 years 11 months ago | 69 | |
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 7 months ago | 87 | |
We are integrating ESignLive with our ASP MVC site.
|
2 | 5 years 10 months ago | 69 |  |
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 4 months ago | 44 |  |
Subscriptions Release Notes
This user is not subscribed to any release notes.