Let’s take a quick look at what happened for the week of May 15th in the Developer Community.
Change Signature Type After Package Creation
In eSignLive, you can assign four types of signatures to a signer/recipient: fullname, initials, capture, and mobile capture. If, for example, your use requires you to change the signature type after sending your transaction for signing, you will first need to change the status of your transaction back to DRAFT.
Right now, there is a bug when updating the signature type where the document unexpectedly changes to a disclosure document. If you’re experiencing this issue, there is a workaround available which you can find from the link below. This bug will be fixed in the next release of eSignLive.
Verify Package Integrity
For every transaction, eSignLive provides an extensive audit trail at the signer/recipient level. Namely, the audit trail includes the sequence of actions performed by the signer (e.g. entering the transaction, authenticating the signer’s identity, approving consent forms, signing documents) along with the date and time of each event. Though, the audit trail does not include owner/sender modifications on the package/transaction.
However, you can retrieve the package json after you’ve sent your package for signing and store it in your own databases. Whenever you want to see if changes has been made on the package, you can retrieve the current package json and compare it against what you’ve stored. The package json also includes a “lastUpdatedDate” field, which tells you the date/time of the last time the package has been modified.
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.