31 results matched your search criteria
Forum topic
OneSpan Sign
As discussed here there currently is no support for PDF check boxes or radio buttons when injecting values into a fillable PDF through your REST API (I am unsure about your SDK).
Forum topic
OneSpan Sign
I tried this one on SDK 10.10.1.0, and tried various different ways to see if it will return the Field properties and it failed to return. My PDF contains only 2 fields that I'm populating using Field Injection. Please see attached screenshot.
Forum topic
OneSpan Sign
Hi,
Is it possible to inject the values using field names rather than ID , since its becoming very difficult to send values using id because if we have four environments each time its very difficult to inject values using ID.
Forum topic
OneSpan Sign
Hello,
Currently we're having the following solution:
1. PDFs are created using DOCUMENT EXTRACTION (for signatures) and FIELD INJECTION (for text fields);
2. Values for text fields are new in every request;
3. Positions for text fields are configured with PDF form fields;
4.
Forum topic
OneSpan Sign
Hi,
If my understanding is correct the Checkbox in eSignLive PDF form is bound to a Signature field.
What this means is, as a user signing the form, I have the option to Check or Uncheck it.
However, is there a checkbox that I can put on the form that will be filled with static data.
Forum topic
OneSpan Sign
Hi,
I'm trying to implement Field Injection, but when I post to the payload to /api/packages, I get the following error.
"messageKey" => "error.validation.verifyDocument.hasNeedAppearancesFlag"
Forum topic
OneSpan Sign
Is there any way to customize a signing date to comply to a specific date format? I.E.
Forum topic
OneSpan Sign
Has anyone noticed problems with the handover URL and hash location strategy routing? If so, have you found a workaround?
When setting the handover url to something like "https://www.mydomain.com/#esign", we are seeing different behavior between the handover button and text link.
Forum topic
OneSpan Sign
Hi,
We are sending a PDF with fields for signature and date. The date is currently injected and is the package creation date. We were wondering if there is a way to have the date be the actual signing date.