In this blog, I will go over what you might have missed in the eSignLive Developer Community during the week of January 22nd, 2018. Let’s get straight to it.
With eSignLive, you have the ability to customize the emails sent out to recipients for signing. As you can see from the screenshot below, you can customize the sender, subject, and body of the email. Each of these email templates can be customized for each language supported by eSignLive. In addition, you have the option of disabling certain email templates if so you choose. This is not yet available through the web user interface or API. You can find a complete list of email templates you can customize in our documentation.
Specific Document Redirect
Elsewhere, the default behavior in eSignLive is to present the document where the first signature is required to be signed. If there is a need to show another document before that doesn’t require any signatures, you can do one of the following two things:
- Make this document a consent/disclosure document. This way, the recipient must hit the accept button to progress in the Signing Ceremony.
- You will need to create a signer authentication token. Then, you build the following redirect:
When adding fields (e.g. textfields, checkboxes, etc.) in eSignLive, you may want to ensure that valid entries are entered by your users. With eSignLive, you can achieve this by creating field validators. Essentially, a field validator enables you to require and restrict the range of acceptable values for an unbounded field. The link below is a guide on how to use field validators with the Java/.NET SDK, and REST API.
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.