Hi, We have a typical business case wherein the Admin Assistant creates a package for signing. The Signer is required to upload an attachment and sign the document. The package is then routed to the Reviewer who is required to review the package (including the attachments) and then sign to accept it or reject the package if the reviewer opts to do so. We are unable to implement this functionality using the default workflow feature that is available out of the box. Not sure if there are any settings that we are missing. please assist thanks Neel
I am new to eSignLive still in the Sandbox, thought I would explore the QR Code. It doesn't seem to work. I created a package using the WEB UI, and for one signature I placed the signature and also added a QR Code.
Years ago, with our initial eSign implementation we noticed a significant drop off when we required a married couple to sign separately. In many states, we found that it was acceptable to have two signature tags, one for each spouses, in one eSign session to make electronic signing as simple as possible. Now that we're moving to the eSignLive Cloud solution, we don't see a mechanism to enable this same behavior. Is there something that I can do (we're using the Java SDK / REST APIs for integration) or is this behavior not possible in the current solution?
We had over 20 packages in our e-sign portal that display as expired even though the package was already completed. Does anyone know why that is? The technician indicated that the packages were completed and that signers were not receiving expiring e-mails. He suggested I follow up with my development team to see if there were any issues on our SDK code. Our developer looked into this issue and noted the following: It appears like there is a package status and package signature status.