Forums
Hello, We have integrated our salesforce application with onespan using APEX SDK for our signature use cases. We have setup below usecase which is working fine. 1. Sent e-signature request to John smith (only one signer on the package). 2. John Smith signs the document. 3. we query the package using below code, we can retrieve the package details and do necessary operations by parsing the JSON.
Forums
Hello, We have integrated our salesforce application with onespan using APEX SDK for our signature use cases. We have this below scenario, could you please check how can we handle this? 1. Email sent to signer named 'John Smith' for signature. On all our signature request packages, we have made SMS authentication as mandatory. 2. John Smith opens the email, uses ‘Change Signer’ button (see the screenshot named changesigner) to assign it to Tom Murphy. Now at this point user has to click on 'Authentication' tab to set any authentication category.
Forums
Hello, We are new to onespan. We have integrated our salesforce application with onespan using APEX SDK for our signature use cases. Currently we are generating the documents with Conga and while generating the documents we are placing the signature tags (eg, {{esl:Signer1:Capture:Size(120,30)}}) into the document. Then using apex SDK to the package for signature. This use case is working fine for us. We have one requirement, where we need a field called “Signer Title”, which we want customers to Input when they sign.
Forums
Hi, We're experiencing an issue with our Email sent from OneSpan where we select the package's language as French, the signer's language as french, but they receive it in English. This has worked in the past without our code changing to call the rest service, and I haven't seen anything in the release notes that mentions this. Is this a bug that was introduced in a release? This might be better suited for the REST API forum, but we are using the Apex SDK to build the package. Thank you
Forums
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. In the past, the date format was always the GMT datetime format and that worked fine. Lately, it seems our date format is being forced to MMMM dd, yyyy . I tried overwriting the format, but nothing seems to work.
Forums
Hi , I have created package and adding document from Salesforce. The document is in Spanish language. But i am getting below error: Line: 683, Column: 1 ESignLiveRESTAPIHelper.ESignLiveRestAPIHelperException: Error creating eSignLive package with documents: 400 - Bad Request - {"messageKey":"error.validation.verifyDocument.documentExtractError","message":"[error.validation.verifyDocument.documentExtractError]","code":400,"name":"Validation Error"} I am trying to attach Manifest_SD-157095.pdf from salesforce. PFA document in this post.