Enhancement Ideas

So far we love the new designer ui, and realize the signer ui hasn't yet changed. I would like to see fields like the signer title, company and email be editable. It is confusing having those on the screen when the signer just sees something like "Signer Title", then once the signer signs, the title is shown.

Through the REST API, make the email notifications configurable much like configuring the signing ceremony layout on a package by package basis. The user experience can be somewhat confusing when one completes a sign ceremony online and then receives an email requesting a signature.

Hello, We would like to request being able to programmatically sign a signature on a single document for a specific signer, and sign all the signatures on a single document for a specific signer. Thanks!

Hi there, In order for a sender to get a very quick view of who has signed and who still has to sign is now only available through the evidence summary. It would be very helpful to have a button in the inbox, which generates a document which shows for each not completed package: - Signees - Signed yes/no - Date of signing. Thanks for your reply. Rob

Please provide a way to capture session expired event of signer

In our set up , we host multiple clients which may generate multiple packages . Since they all transit through our one eSign Account, we would like to see a way to : 1. Pass Custom References ( These are usually key items like Institution Code , Application No ...etc) 2. Search by those references 3. Generate reports based on those References. This will greatly help track down package once it landed in eSignLive back to where the actual application originated. Also it will provide valuable reporting tool per Custom Refence ( in our case per Institution )

Currently in our PDFs for Lending purposes we often have predefined signature fields on the form for up to 4 parties, although in a typical application , we may not always have 4 parties. As such , when I submit a JSON with the number of Signers less than the actual number of signature fields on the PDF, there is an error.validation.extractingFields, stating it couldnt extract the Signer2 where the latter is the name of the textfield in the PDF.

As discussed here there currently is no support for PDF check boxes or radio buttons when injecting values into a fillable PDF through your REST API (I am unsure about your SDK). The alternative of replacing them with with text fields and passing X values to them unfortunately does not meet WCAG 2.0 AA standards which I recently discovered also covers PDFs. Is this something that is on the development road map? Thanks.

Currently end users are having to MANNUALY move completed packages to archive to keep their inbox free of clutter. We would like to have a configuration setting that would allow us to indicated a time period to move the completed packets to archive and a secondary setting that would allow us to set up a permanent purge. Here is how we would like our environment to work with regard to this request.

Right now when a potential signer receives an email and clicks the link to view the document, there is no way for us to receive any notifications this has occurred. Even better, the ability to receive notifications for more precise events during the signing process (a notification for each signature, etc). This is important for us to know, so we can explain the contract terms and answer questions. This ties directly into the read-only "end user support view" for assisting the signer during the signing process. Thanks!