We want to use bulk sign to be able to sign a document for a signer
your SDK only supports passing signer Id + package ID
Is there a workaround to pass document id
I have been using the .NET SDK solidly for about 6 weeks with no issue. My coworker mentioned 2 weeks ago that one day he suddenly could not create a signing package when he could the previous day. I could not reproduce the error (below) on my machine, so we had to pass some work onto another coworker due to time constraints.
I was working on my app Friday without issue, then today ran into the same error
OneSpan recently implemented "Signers can now: (1) upload one or more supporting documents to a transaction before the transaction is completed; (2) upload multiple documents in a single attachment.".
How do I turn this feature off? Our relationship was 1 to 1 with attachments and receiving zip files instead of photos is a breaking change to our current implementation.
For testing I have minimized the attached PDF to just have one field, a single pre-labeled signature. Similar documents work fine but this particular one gives me a “noApprovals” message when trying to run it through an exiting .NET submission program which is already setup & working. I am not sure what "noApprovals" means here and why this document is giving it but not others.
Hello, I tried to make an API call to retrieve incomplete SENT packages, but the results included a COMPLETED package along with SENT packages. All COMPLETED pakcages were not returned, just one was. Here is the call:
Page<DocumentPackage> packagesSent = eslClient.PackageService.GetPackages(DocumentPackageStatus.SENT, new PageRequest(1,100));
I only want SENT packages. Why would a COMPLETED package also be returned? Is there another way to limit the results to just SENT packages?
Thank you
Hello,
I have a scenario where I have a signer that is attached to a package but does not have fields to sign on a document. I am able to generate the url for the signer using this line of code in .NET
var signingUrl = eslClient.GetSigningUrl(new PackageId(id), eSignSigner.SessionToken);
But it only generates when the package is created and not completed yet -- when all signers have signed the document and I debug the code down to where the url comes in, I get a 404 error saying the url can't be found for the user.
Any ideas?
contract is a class with accessible properties that have been populated by this point and is a parameter being passed into the call here.
All the text anchors have been verified in the starting doc...
string sourceFile = pdf.FullName;
string LenderEmail = "[email protected]";
bool CoBorrower = false;
Hello!
After a Package is Completed its available at the plataform the option to manually Archived the transaction . Ok with that.
But those the plataform do any "Auto Archived", like after X days of being Completed the transaction is auto archived. If the answer is yes,what the number of days (X) ? Is it configured? Where?
Tank you!
Hello Duo,
I am getting this error while using the latest chrome beta.
Refused to display 'https://sandbox.e-signlive.ca/login?destination=%2Fpackages%2Fj1oMqRKTUWPAUkJJyQjFsHigA-0%253D%2Fsign'
in a frame because it set 'X-Frame-Options' to 'sameorigin'.
Thanks,
Nehme
Hello,
We're using the .NET SDK for OneSpan Sign. When creating a package, we're receiving a message that we've placed an object (presumably the signature) outside the page boundary. The full error details from the SDK are below.