Hi, We are seeing very slow performance - both in API responses as well as trying to use the web UI. The API is also sporadically returning us 500 errors. We seem to get brief windows in which we can successfully get an API call through, but then the 500s start happening again. The system status page seems to indicate all is well, but that is not our experience. I'm trying to establish if this is something specific to our account, or are there system-wide issues? Thank you!
I'm using Field Injection for my documents, but can't figure out how to use a Signature field that is already created on my PDF form. Do I have to create a signature field manually like what is done here ===> https://developer.esignlive.com/guides/feature-guides/sign-documents/ ? I would like to think there is a way to use the signature field that is already on the for, but obviously I am not aware how. Using the .net implementation. Thanks in advance, Jack
Hi, One of our testers performed below use case: a) Signed the document using eSignLive b) The digital signatures were captured in the signature block c) Downloaded the signed copy from eSignLive & opened the PDF d) Clicked on the 'Fill & Sign' option appearing on the right of the document e) Tester was able to annotate the document. I read in the forums that what you get from the eSignLive download is a flattened copy of the PDF..they are akin to images. Tampering the PDF does not hold good from a legal standpoint. Is that true?
My company has been working with yours to white label the product and resell it. Is it possible to embed the eSignLive web app, (the site you access in the sandbox mode), into an iFrame to be placed in our application? If so, how do we embed this page in an iFrame and load a specific user's account? I'm being told that our users would not have their own username and password, so we have to create the session for them. All of the examples I'm finding are only for API integration.
Hi, We are using the following API to retrieve the signer signing url GET /packages/{packageId}/roles/{roleId}/signingUrl We are controlling the signing process from within our host application by providing the signing url to the signer as an iframe within our application. For this to work effectively, we would like to disable the email that goes out to the signer at the package level. Please let us know if this is doable. (NOTE: we are creating the package using eSL apis) thanks Neel
Hi, Inside my one document, If I put only below tags it's working fine. {{esl:signer1:list:options("Ja", "Nee")}} {{esl:signer2:list:options("Ja", "Nee")}} But if I put other tag for textbox then I am facing below error : {"messageKey":"error.validation.texttag.propertiesFormatError","parameters":{"tag":"{{esl:signer1:list:options(\"Ja\", {{esl:signer1:textfield:size(200,50),Maxlen(200)}}"},"message":"{tag={{esl:signer1:list:options(\"Ja\", {{esl:signer1:textfield:size(200,50),Maxlen(200)}}}: Properties format error.","code":400,"name":"Validation Error"} Here inside the one TR I have put l