In this blog, I will go over what you might have missed in the eSignLive Developer Community during the week of April 30th, 2018. Let’s get straight to it.
Opt-Out and Decline Messages
When creating transactions in eSignLive, you have the ability to give your recipients the option of opting-out or declining. In terms of functionality, they essentially both have the same behavior: it will put your transaction back to your draft folder. However, they have different business meanings. Opting-out of a transaction means that the recipient does not wish to sign electronically whereas declining means that the recipient wants changes to the transaction. However, both require the recipients to enter a reason before they can successfully opt-out or decline of a transaction. With the SDKs/API, you can retrieve these messages. From the link below, you can find a guide on how to retrieve the opt-out and decline messages.
If, for example, you want to give your users access to place signatures and fields onto the document instead of having this done programmatically through your application, you can do so by creating a designer session. The following guide shows you how to build the URL for the designer view using the Java/.NET SDK and REST API.
By default, eSignLive will send an email notification to all the signers once the transaction has been sent for signing. However, if you don’t want to have this behavior enabled, you can contact support (firstname.lastname@example.org) to have the email notifications disabled. Note that this configuration is on an account level. In other words, this will affect all transactions created after the changes have been applied.
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.