Forums
I'm looking for information on the declined process. When a signer declines a document, what happens in the system? Does the signer status get updated or is this at a package level? What happens to the package? Is it still considered "SENT" or is it in "DRAFT" mode? I have the call back notifications setup to receive "PACKAGE_DECLINED" and am currently setting this status on our end at the signer level. I just want to make sure that's correct before I finish wiring that up in our application. Thanks Colleen
Forums
This works (after unzipping the file) byte[] bytes = eslClient.PackageService.DownloadZippedDocuments(packageId); using (Stream file = File.OpenWrite(DocumentName+".zip" )) { file.Write(bytes, 0, bytes.Length); } This creates a corrupt document byte[] bytes= eslClient.PackageService.DownloadDocument(packageId, docpackage.Documents[0].Id); using (Stream file = File.OpenWrite(DocumentName+".pdf" )) { file.Write(bytes, 0, bytes.Length); } Note: You can use the UI to download the document successfully Thanks Jim
Forums
I'm looking for more information on the expiration date. Can you tell me how the date and time is stored on your end? And then what is checked when the expired callback event is sent? I would like to set it to expire today, but I get an error message saying the date must be in the future. Should I be including a time when setting this value? If so, should it be 11:59pm UTC or is it timezone specific? Thanks Colleen
Forums
Greetings I'm building an app for a customer using ESignLive. person1 fills in a couple Textbox fields with numbers and signs a document (there is only one place for that person to sign). The document is still open (not complete yet). 2 Months later person1 signs the document again in a different location (again there is only one place that person to sign) associated with the signature is a Label that contains the sum of the number fields in the first signing. I'm able to do this if the user is an account owner, but not if they are an invited signer.
Forums
We keep the byte info of a PDF in our database (BLOB). If I create packages with PDF's that are 1-2 pages I have no issues, but we have a PDF that has 7 pages and when we try to create a package with the larger PDF we get this error using the byte stream this is not an issue when uploading the doc directly: {Silanis.ESL.SDK.EslServerException: Could not upload document to package. Exception: The remote server returned an error: (400) Bad Request. HTTP POST on URI https://sandbox.e-signlive.com/api/packages/304d1ae6-7a90-4daf-bda2-d5e011f360f1/documents.
Forums
I have some questions about creating the signing url in the .Net SDK and the REST API. Here is what I have so far. I've created a package called "Test". I've added documents to Test. I've added Signers with just firstname, lastname and emailaddress to Test. I want to store the SignerId in my database, which I see that I can retrieve by using this:
string signerId = eslClient.GetPackage(pkgId).GetSigner(emailaddress).Id;
. So far, so good. In our application, the user will then be shown the designer view in an iFrame to add the signers and signing types to the documents.