Dynamic, flexible, and powerful: Introducing Docusign Elastic Signing
Deploy frictionless, flexible, personalizable agreements that capture consent in a single step.
Today, we’re happy to announce Elastic Signing: an eSignature feature that offers capabilities for developers to build modern agreement experiences within their web or app flows. With elastic signing, developers can now deploy agreements in a frictionless, seamless manner to elevate and personalize the signer experience.
What is Elastic Signing?
Elastic Signing is a new eSignature feature that enables developers to build customized agreements that blend right into the rest of their web or app page. The new Elastic Signing functionality includes three notable features: dynamic content, conditional content, and UI customization. With dynamic content, specific values that need to be included in the agreement can be supplied in real time by the web application before the Elastic Signing experience is presented to the signer. With conditional content, developers can easily deploy a single template to configure multiple variants of an agreement based on the scenario instead of writing code to choose from multiple templates. Finally, UI customization offers the ability to create a delightful and frictionless signer experience. The agreement look and feel, colors, borders, and button shapes can be customized so that the agreement is deployed right within a web page or an app page seamlessly.
New code example in eight languages!
To help developers understand how to use the new features, we have created a new code example: How to embed an elastic signing agreement, which explains with step-by-step instructions how to build a web application that embeds the Elastic Signing functionality in your web application. All you have to do is understand your use case and provide the document that will be signed, including the dynamic fields to be set by your code. The example shows how to add the five basic fields that Docusign provides out of the box: Full Name, Email Address, Job Title, Company Name, and Date. However, you can modify the code to support any custom dynamic content field you need for your own use.
This example is making a REST API call to the Click API createHasAgreed endpoint using one of eight coding languages. Except for the Bash and PowerShell code examples, which make raw API calls, the other six languages (C#, Java, Node.js, PHP, Python, and Ruby) are making the API calls using the Click SDKs.
Note: If you used the Click SDKs before, you’ll need to upgrade your package version to the most recently released one to use this example.
Additional content for developers
In addition to the new code example above, we have also released updates to our Elastic Signing documentation to reflect the new functionality. You can find updated pages explaining how to use the dynamic content as well as how to customize an elastic template’s appearance in the Elastic Signing UI. We also have updates to our API Reference, including new endpoints.
Additional resources
Palash Agrawal currently serves as a Product Manager for the Docusign eSignature product. Prior, Palash worked as a tech entrepreneur, built products from scratch, and scaled them to serve millions of users.
Palash holds an MBA from MIT Sloan School of Management and a B.Tech from the Indian Institute of Technology, Bombay.
Related posts
Discover what's new with Docusign IAM or start with eSignature for free
