Week In Review: Developer Community - February 6, 2017

Haris Haidary, February 15, 2017

Let's take a quick look at what happened for the past week in the Developer Community.

Capture Signature Behavior

Currently in eSignLive, if you have multiple capture signatures per document in a transaction, a signer only has to draw his signature only once per document. Any subsequent capture signatures on the same document will be automatically drawn. Lately, there has been a number of requests to change this behavior. In other words, force signers to draw their signature for every capture signature fields. This feature is currently on our roadmap where you will be able to set on an account level whether or not signers must draw their signatures in every signature box. Link to Post

Callbacks Setup

Once you have your callback event notification listener up and running, there isn't much to configure in terms of firewall or port settings other than possibly white-listing eSignLive's outbound IP addresses. If you’re currently able to make requests with the API/SDK to eSignLive, you should be good to go. Though, if you're running into issues, you can find eSignLive's outbound IP addresses from the link below. Link to Post

Signing Date Customization

In addition to signatures, you can have signature date fields, which at the time of signing the system automatically populates this field with the current date. The default format for the signature date is the following: yyyy-MM-dd HH:mm:ss 'GMT'. You can change this format to anything you wish. However, this can only be done by sending support a request and not through the the SDKs/API. 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.

Haris Haidary Junior Technical Evangelist LinkedIn | Twitter