1548 results matched your search criteria
Forum topic
OneSpan Sign
Hi,
I am trying to embed the signing in my webpage using an iframe
To generate the session token i use
SessionToken sessionToken = eslClient.getSession
Forum topic
OneSpan Sign
Hello,
We are setting a particular document in the package to use AcceptFor signatures. The document in question IS NOT the standard eSign consent form. It is another document that we simply want the signer to acknowledge.
Forum topic
OneSpan Sign
Hi
Is there a way that custom package attributes can be shown in the email sent to the signers.
https://developer.esignlive.com/guides/feature-guides/package-attributes/
For example I might need some additional text in the email for only some of the signers.
Forum topic
OneSpan Sign
Our scenario:
Package is created, signed and completed at our premises.
We then allow the signer 5 days to go home and download the package.
However, we want to block the download if the signer takes longer than a certain number of days.
Forum topic
OneSpan Sign
Hey there,
In our project, we have one scenario requires embedding two signing ceremony in two different iFrame div at the same time, one for each signer of a package.
Forum topic
OneSpan Sign
https://community.onespan.com/documentation/onespan-sign/codeshare/designer-view-apex-sdk
Forum topic
OneSpan Sign
We keep the byte info of a PDF in our database (BLOB).
Forum topic
OneSpan Sign
I am following the example in your blog to Authenticate a Signer: https://www.esignlive.com/blog/esignlive-how-to-authenticating-signers/
Here is what I have produced:
var apiKey = CeremonyClient.GetKey();
var urlBase = CeremonyClient.GetUrl(); // "https://sandbox.e-signliv
Forum topic
OneSpan Sign
Hello, We have integrated our salesforce application with onespan using APEX SDK for our e-signature use cases.
We want to add personal message to individual signers of the package. Could you please let me know which APEX SDK method we should use to do the same?
Forum topic
OneSpan Sign
We've got a form where one section is a radio button group. The "Actions required" language at the top of the New Signer Experience form is telling user there are 8 actions when in actuality there are only three because one of the actions is a radio button group.