2061 results matched your search criteria
Failed to Delete Document
Forum topic
OneSpan Sign
Hello, I hit the REST API to try and delete a document from our package, and this is the response we got. { "messageKey": "error.validation.cannotDeleteDocumentInActivePackage", "message": "Document is in a active package and cannot be deleted.", "code": 400, "name": "Validation Error" }
layout updation by data of system
Forum topic
OneSpan Sign
Hi Team, We are able to successfully upload a single document while creating a package .
PDF Format In Chrome
Forum topic
OneSpan Sign
Hello, We are running into an issue where our signed PDF files are not being displayed correctly in Chrome and sometimes Firefox as well. Everything is normal with the PDF documents until we sign and download them through eSignLive.
Set Expiry Date For A Package
Forum topic
OneSpan Sign
Hi, I have a requirement to have an expiry date to be set during package creation or package update. I have read through the request and response related to packages and configuration and still could not figure out the procedure or field where the data should be set.
Communication with Go3/Go6
Forum topic
Mobile Security Suite
I just got a Go3 and Go6 hard tokens. And i need to communicate with these devices. How do I do this?
Populate Text Fields with dynamic data in API call
Forum topic
OneSpan Sign
Hello!
Possible to have Text Tags pre-populate signers?
Forum topic
OneSpan Sign
Use Case: Client has Vertical Enterprise App that they can customize output.  We have trained them on text tags and they are very excited for dynamic signing blocks, etc.  
Allow Department to Change Signer
Forum topic
OneSpan Sign
We are using the APEX SDK plus OSS event notifications to manage our signing ceremonies. Salesforce sends out all emails to the signers with the OSS url.
Using KBA
Forum topic
OneSpan Sign
Guys - We are looking at enabling KBA into our custom system.
Signer identified at runtime
Forum topic
OneSpan Sign
Hi, We've a scenario wherein we have 3 signers for a given document and all of them sign sequentially. Singer1 signs then signer2 and then signer3. The issue though is that signer2 is identified at runtime and known to signer1. i.e.