Enhancement Ideas

Follow-up of https://developer.esignlive.com/forums/topic/emailmessage-content-length-limit/ Most of the fields have 4000 characters limit, but here we have only 1024. I would love to have it increased.

I was looking through the sample created using Android SDK. It did not seem to have an option to create a transaction using a template. Has this future been implemented? If not, are there any plans to implement it?

The following code does not return the specific error message.

In the same way as we can programmatically configure the Signing Ceremony via SDK (http://docs.esignlive.com/content/c_integrator_s_guide/sdk/k_customization/customizing_the_signing_cermony.htm) , we need to be able to customise the Designer View on a package by package basis. Currently this is possible only via support request - https://www.esignlive.com/blog/esignlive-how-to-customizing-the-designer-view/ - but this doesn't give enough flexibility when integrating, where we may be connecting through different Esignlive accounts, and each of them would have to be customised (hampering also t

It would be extremely helpful to enhance the signing ceremony UX. Since it's the core component of an end-user, we would love to see enhancements to the UI/UX to make it a better/more intuitive experience. Below are a couple of items: 1. Add an easy clickable navigation feature for required fields that are not signature elements, like the software uses for the signature elements - we have users that completely miss required fields because there's no initial visual to the user that there are other fields that need to be completed except signature elements. 2.

Hello Team, I have a scenario where I create and send a PackageDocument from a dynamically provided PDF document and I add a number of signatures based on a text-anchor.

Today in the eWitness player, when viewing a signing package. We are showing the email message, the subject, the To Address, and the text body of the message. However, we are not seeing the From email address. It would be useful to have this included to help with troubleshooting in the future.

There was some talk about removing the opt-out functionality in other threads because it seems as though it is basically the same as "Decline". The package gets put into draft mode as soon as a signer chooses this. But I would actually like to see Opt-Out be used to let the package continue to be signed. We have a customer who requested this, apparently a signer has a conflict of interest and wanted to “opt-out” rather than decline since they don't need all signers to sign, just a majority.

Reposting from the .Net SDK channel Issue: It seems the issue is because eSignLive is anticipating that the ‘Id’ of the group is the GUID that identifies the group in eSignLive, and so if the ‘Id’ is changed to something else it can’t find the role of the group.

Unhandled Exception: Silanis.ESL.SDK.EslServerException: Could not upload document to package. Exception: The remote server returned an error: (400) Bad Request.

Allow users to toggle between tenants they have access to in E-Witness without signing out and then back in.