1602 results matched your search criteria
Forum topic
OneSpan Sign
Hi,
This issue popped up in the last couple of weeks in our testing Sandbox environment. We've been using Text Anchors to configure all our signatures, so we have a FULLNAME block, and a corresponding Date signed that gets auto-populated on signature.
Forum topic
OneSpan Sign
Not sure when this change was made, but previously in the designer view, adding Signature fields would show the signers name on the field itself. But now it no longer shows a name and appears to be color coded to the signers displayed on the left.
Forum topic
OneSpan Sign
Hi,
Is there a way to use the field extraction feature and also set the name of the (form) fields in the pdf to store the data.
Forum topic
OneSpan Sign
We are moving over to New Signer Experience. We are using Java SDK to add validation to fields like this:
.withValidation(FieldValidatorBuilder.regex("^\\d{2}/\\d{4}$").required().withErrorMessage("Please enter a valid retirement date (MM/YYYY)"))
Forum topic
OneSpan Sign
Hi eSignLive,
Currently the documents are auto navigating to next document with in the same package once the signing completed on document.
Forum topic
OneSpan Sign
Hi,
I'm trying to submit a payload to POST https://sandbox.esignlive.com/api/packages, in the past few days it has been intermittently working and not, this morning it hasn't been working at all yet.
The error message is
{ messageKey: 'error.internal.default',
technical:
Forum topic
OneSpan Sign
For Sharepoint connector:
Since Document ID becomes important for implementing additional SP document workflows (eg. Post package completion), is there a way to configure embedding SP doc ID (if document is selected from SP document library) within package document ?
Forum topic
OneSpan Sign
Hi,
currently I have a client with large document size (1870k), and this document is combination of several other documents, some of them with signatures, and some of them without .
Forum topic
OneSpan Sign
I'm seeing some odd behavior, on my local development environment, I can create a package and delete the "default-consent" page without issue. Once I've moved this to our integration environment, this same call fails.