We have integrated with OneSpan using your .Net SDK (version 184.108.40.206 ). We are experiencing a scenario where we have a transaction has 1 document, 1 recipient and 1 attachment request. The document is signed and the user uploads an attachment. The sender rejects the attachment. If the sender then tries to edit the transaction, we are getting the following error:
Is there any feature in OneSpan (.NET SDK or manual download by owner), that lets the package owner download multiple signed docs from the same package as one single PDF?
I want to leverage the feature of restricting each document's visibility to only its signers, but still have the ability to have a single signed PDF containing all the docs from the package.
In a package with multiple documents, created using .net SDK,
Is it possible to set a document's visibility during signing ceremony only to the signers on each document, through SDK?
If so, then after the package is completely signed and email goes to all signers with the download link to the signed documents, will a signer be able to download the docs not visible to him/her?
When OneSpan releases a new version on their production environment, will there will always a corresponding SDK version update as well? How are the OneSpan environment and SDK updates timed?
Can the integration code use an earlier version of SDK even when the OneSpan environment has been updated to a new major version?
What is the recommendation from OneSpan on these major releases and SDK versions update ?
I updated from 11.33 using the downloaded SDK, but found the NuGet for 11.35 today, but am having issues resolving the ESLClient class from the NuGet install. I tried a using for each namespace in OneSpanSign namespace, and am having no luck. Did the class change from 11.33 to 11.35? Not finding anything in the documentation.
Is there any recommended way to update the package name property after it was first created, through .NET SDK?
Tried calling the UpdatePackage method to update the package but it didn't update the package name property. Also calling the SendPackage after UpdatePackage step resulted in the following error. It looks is UpdatePackage is already changing the status of the package from Draft to In Progress.
I have a form which I'm using document extraction to pull in fields from, and some of the pieces need to be entered at the signing ceremony. Is it possible to mask some of those fields as they are considered PPI? I'll read them on the backend securely, but don't want them showing up in plain text on the finished document.
Fields on the form:
[Borrower.Capture1.Textfield1] - Can be plain text
[Borrower.Capture1.Textfield2] - PPI
[Borrower.Capture1.Textfield3] - PPI
[Borrower.Capture1] - Can be plain text
On an In progress transaction (SIGNING_PENDING) with multiple signers & with Document A that is signed by (SIGNING_COMPLETE) Signer A, is it possible to update the document content (bytes) without losing the already obtained signatures from Signer A?
I noticed that eslClient.PackageService.UpdateDocumentMetadata did not update the new contents on the same document
Is there a way using the .NET SDK, to discard a draft version of the transaction and go back to its previous in-progress version?
As the title asks: I'm working on an in-person signing flow where all signers will be on the same device, and am embedding the signing ceremony in an iFrame. For aesthetics and ease of control, I want to get rid of the welcome/signup/guest login controls, as well as the "For Assistance" number from the upper right page of the screen. Is that something that can be done?