Week In Review: Developer Community - May 1, 2017
Let's take a quick look at what happened for the week of May 1st in the Developer Community.
Sending Transaction Without Signatures
In eSignLive, every transaction must include at least one signature for one of the signers/recipients. Hence, you cannot send a transaction without signatures/approvals. If on the other hand, you are looking to create a consent style document in a transaction, you can have a look a this guide on how to do so. Note that signatures/approvals cannot be added on a consent document. In other words, if you choose to add a consent document in your transaction to be accepted by a signer/recipient, this particular document cannot have signatures/approvals for any other signer/recipient. Link to Post
Disable Email Notifications
Email notifications are on an account level, meaning that any change will affect all subsequently created packages/transactions. If you wish to turn off the email activate (i.e. email signers/recipients receive to sign), for example, you will need to send support a request. However, if you decided to turn off automatic email notifications, you can still manually notify your signers/recipients as shown below: Java SDK
eslClient.getPackageService().notifySigner(packageId, "[email protected]", null);
eslClient.PackageService.NotifySigner(packageId, "[email protected]", null);
Customize Capture Text
When using capture style signatures/approvals, you have the ability to customize the text that appears after confirming your signature/approval, as shown below: Though, this feature is on account level. You will need to send support a request to have it changed. Link to Post 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.