New in the e-SignLive™ Winter Release: Designer View Access – The Human Touch
e-SignLive™’s API and SDK, along with the embeddable signing ceremony, have long enabled organizations to add e-signature capabilities to their homegrown or third-party systems. What the e-SignLive Winter Release does is provide the ability to access the designer view programmatically. This gives organizations more choices in how they construct electronic workflow and in particular how they design document layouts. For example, you’re a software architect and you’re looking to integrate e-signatures into your platform or app. You now have the ability to embed the designer view GUI in your own UI to enable the review and layout of signature blocks and fields in documents. This new option introduces the possibility of manual intervention when building an electronic transaction process when a fully automated straight through electronic transaction is not desired. How it works The designer view works similarly to the e-SignLive signing ceremony, namely through the use of an HTML view embedded via an iframe. Just as with the signing ceremony, the user first creates a package through the API/SDK. Then, the user creates a session for the agent. Here’s a little code snippet using the e-SignLive Java SDK that shows how to execute these two steps: EslClient esl = new EslClient("Your API Key", "https://apps.e-signlive.com/api" ); DocumentPackage designerBlogExample = newPackageNamed( "Policy for e-signature" ) .describedAs("This is a package created using the e-SignLive SDK") .withSigner(newSignerWithEmail("[email protected]") .withFirstName( "John" ) .withLastName("Smith")) .withDocument( newDocumentWithName( "First Document" ) .fromFile( "/path/to/document.pdf" ) ) .build(); PackageId packageId = esl.createPackage(designerBlogExample); SessionToken sessionToken = eslClient.createSenderSessionToken(); Only a minimal package definition along with document is sent to the API/SDK. The last step in the code snippet creates the agent session token, which will be necessary to open the designer view. Once that is done, the designer view can be opened in a web browser window or tab, or embedded directly within your system using an HTML iframe. Here’s a screenshot of what Designer looks like:
For users familiar with e-SignLive, they’ll notice that the designer view looks exactly like the document preparation tool found in the standalone version of e-SignLive minus the branding and top level navigation buttons. From the designer view, users are able to move signature fields around, place new signatures and fields and ultimately send the package out for signing. Find out more about the e-SignLive designer view in the complete documentation. Want to try it out? Sign up now for a free e-SignLive developer account and start integrating e-signatures into your organization’s applications. Etienne Hardy is Silanis’ SaaS Software Architect and leads the e-SignLive™ engineering team. Etienne’s background in web application architecture and development extends to industries including finance, human resources, insurance, medical and pharmaceutical.