eSignLive Release 11.10: Mobile Authentication Pages
Release 11.10 of eSignLive has recently been deployed to the sandbox environment where we've updated the Mobile Signing Ceremony authentication pages in addition of a couple of bug fixes. You can find the deployment dates for all our environments on our Trust Center page.
Mobile SMS/Q&A Authentication Pages
In the Mobile Signing Ceremony (MSC), we've updated the SMS and Q&A authentication pages to be mobile friendly. Previously, users signing on mobile with required authentication were directed to the desktop authentication pages that were not responsive. Let me walk you through an example to show you how these pages will look from this release forward:
- Create a transaction with a dummy recipient which you have access to the email address and add an SMS or Q&A authentication to this recipient. If you don't know how to do so, you can follow this guide on our Developer Community.
- Once you've sent your transaction for signing, click on "Go to Documents" in the email notification you receive.
- You will then be directed to the new SMS or Q&A authentication page depending on the type you chose.
- After you've entered the correct PIN or answer, you will be redirected to the Mobile Signing Ceremony.
Confirm Dialog Text
In addition to the above, you can now customize the confirmation message that appears in the Signing Ceremony when a recipient clicks the confirm button to apply their signatures to a document. Note that this can only be done through support and not through the API/SDK. Below is a screenshot of a customized confirm dialog:
A couple of bugs have also been fixed in this release. Most notably, we've fixed an SDK issue that prevented the retrieval of templates that contain Text Tag information. You can find the complete list of bug fixes on our documentation page. 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.