In this blog, I will go over what you might have missed in the eSignLive Developer Community during the week of January 1st, 2018. Hence, let’s get straight to it.
Downloading Uncompleted Transactions
In eSignLive, you several options when it comes to allowing your recipients to download documents. You could, for instance, disable downloading of the documents all together during the Signing Ceremony and simply deliver the signed documents via email. Another option you have is to only allow download of documents once signing has been completed. This is achieved by enabling the “disableDownloadForUncompletedPackage” field in the transaction settings through our REST API. This setting will also be available in the next version of the SDKs.
Customizing UI Messages
In addition to the above, you can also customize the messages that appear in the navigation bar in the Signing Ceremony (see screenshot below) to fit your needs. These UI messages can also be customized on a per language basis. Note that the UI messages can only be customized through our support team. You can send your request to firstname.lastname@example.org to have them changed or if you wish to know the complete list of UI messages that are customizable.
Lastly, I’ve written a simple console application that will copy all of your senders, templates, and layouts from account to another. In order to run this tool, you will need the API key and environment URL (e.g. https://sandbox.esignlive.com/api) of both (source and target) accounts. Note that the source and destination accounts cannot be on the same environment. In other words, this tool will not work if you try to copy a sandbox account to another sandbox account on the same environment. This restriction comes due to the fact that you cannot have senders under two different accounts in the same environment. In addition, the source and destination accounts must be registered under the same email address. It also recommended to run this tool with Fiddler to monitor the requests going to eSignLive. This way, you can easily check if any of the requests fails.
If you have questions regarding this blog or anything else concerning integrating eSignLive into your application, visit the Developer Community Forums: developer.esignlive.com. That’s it from me. Thank you for reading! If you found this post helpful, please share it on Facebook, Twitter, or LinkedIn. You can find all of my previous blogs by going to my author page.