1108 results matched your search criteria
Forum topic
OneSpan Sign
One of your competitors offers something they call a 'document markup feature' that allows signers to make changes to documents and negotiate changes during the signing process. Does OneSpan have any feature like this currently or is it on the roadmap?
Forum topic
OneSpan Sign
Hey there!
I have a transaction with ExpirationDate with 2 signers (with sign order) and are required Attachments.
Forum topic
OneSpan Sign
In my scenario, the signer has to send the document back to the initiator to correct and make changes before they can sign. How can I do that.
Forum topic
OneSpan Sign
Hi,
We are noticing that the handover link is not showing after signing all the documents.
Steps to reproduce:
1. We create a package with 4 signers
2. User 1 signs everything works fine, we see the handover link.
3.
Forum topic
OneSpan Sign
Hi there! It would be nice to specify that documents ALWAYS attach after a signing package is complete. This currently has to be done per signer and in our industry, I want to ensure that ALL signed docs get sent to ALL signers by default. Is this possible?
Forum topic
OneSpan Sign
So far we love the new designer ui, and realize the signer ui hasn't yet changed. I would like to see fields like the signer title, company and email be editable.
Forum topic
OneSpan Sign
Hi,
we upgrade SDK to 11.25 (was using 11.0.2), we noticed that the locale has been changed
in 11.0.2, when we sent 'fr-CA' to SDK, SDK will translate to api package as 'fr'
in 11.25 when we sent the same request, SDK translate to api package as 'fr-CA' which is not recognized so the package languag
Forum topic
OneSpan Sign
We have users that have changed their name which results in a change to their email address that impacts their account with OneSpan. What has been the best practice there, as we have single sign-on, once the user have changed their name, it will take time again to go back and it is just a m
Forum topic
OneSpan Sign
When I do PUT request to /api/packages/{package_id} with request payload as
{
"status": "DRAFT"
}
I get error response as
{
"code": 415,
"entity": null,
"message": "Unsupported Media Type",
"messageKey": "http.status.415",
"name": "Unsupported Media Type",
"technical":
Forum topic
OneSpan Sign
Hi!
It would appear that the success response message sent by esign sandbox to a request for signingStatus was somehow changed, over this last weekend, from 'COMPLETED' to 'SIGNING_COMPLETED'. This seemingly minor detail cost the dev team all day today.