A lot has already happened here at Momentum 2018, but we’re not nearly through. Day 1 began yesterday morning bright and early, as attendees from near and far gathered at the Hilton Union Square in San Francisco to check-in for the business acceleration event of the year. Just after 9:00am, Neil Hudspith, President, Worldwide Field Ops, DocuSign, kicked things off in the opening keynote.
The Opening Keynote
Neil took the audience through an abbreviated journey of DocuSign, one which is 15 years in the making. Today, DocuSign serves 400,000 customers, has hundreds of millions of users, and is present in 180+ countries. And particularly significant to you, our amazing developers, more than 60% of DocuSign transactions take place through the DocuSign API.
This morning, we revealed our vision of enabling modern Systems of Agreement.
Every company has an existing system of agreement. From sales contracts to employment offers to purchase orders and more, a system of agreement is how written agreements are prepared, signed, enacted, and managed. It’s no secret that DocuSign’s eSignature technology replaces the tedious and slow process of printing, signing, scanning, and faxing. Our expanded vision is to modernize the world’s Systems of Agreement, and to broaden the DocuSign platform to automate and connect what happens before, during, and after the e-signature.
You can learn more here about how companies are accelerating and simplifying the way they do business with modern Systems of Agreement – and how you can too.
DocuSign for Salesforce CPQ
Perhaps one of the most exciting announcements for developers to come out of this morning’s keynote is the announcement of DocuSign for Salesforce CPQ as the modern System of Agreement platform to close deals. This new integration provides for a faster and easier experience at every stage of the quote-to-cash process. During the keynote, Andy Tzou, DocuSign Senior Product Manager, provided a live demo of the new integration, which illustrated the immersive experience for Salesforce users. Salesforce end users never have to leave the Lightning interface to prepare, sign, act, and manage quotes and agreements. Tomorrow’s Day 2 keynote will feature DocuSign’s Chief Product Officer, Ron Hirson, showing where and how the digitization and automation assists in the preparation and acting on quotes and agreements in Salesforce CPQ. DocuSign for Salesforce CPQ will be available in the summer of 2018.
Immediately following the opening keynote, we dove right into the breakout sessions. This year’s developer track was called Developer Reverb, with a slew of developer-focused sessions.
Developer Reverb Breakout Sessions
Check out the amazing developer sessions from Day 1 below, and find all of the session content available for download, here.
Intro to the DocuSign APIs and Developer Tools
This first and introductory session was led by Ergin Dervisoglu, Senior Product Manager, DocuSign. Ergin helped developers new to the API – or those who just needed a refresher – learn how to integrate DocuSign functionality directly into their apps or websites, and how to do so in minutes. We saw him guide the crowd through the newly redesigned DocuSign Developer Center, demonstrate live API tools, go through the three OAuth methods, and more.
Best OAuth Practices When Authenticating to DocuSign APIs
Larry Kluger, Senior Program Manager, DocuSign, took the helm for this session. DocuSign has secure authentication schemes for any type of application, and Larry discussed the different ways to authenticate, whether you’re building a service integration or a user application. He talked about different OAuth patterns where he presented the different login workflows, consent, token management, and more.
Everything You Ever Wanted to Know About Forms and Fields
Seriously: everything you ever wanted to know. Brandon Schnierer, Solution Architect, DocuSign, took the crowd through a comprehensive overview of forms and fields and answered questions along the way. He also showed how to take advantage of the multitude of form features, including dynamic fields, anchor text, templates, XFA vs. Acrobat PDFs, and more.
Santa Clara County Extends DocuSign Functionality by Creating Dynamic Signing Groups with the eSignature API
The title of this session nearly says it all. Lawrence Lam and Malu Sivasankar from Santa Clara County, CA, were kind enough to join us at Momentum to take the crowd through an innovative solution for using DocuSign. They showed how the county’s IT department extended standard DocuSign functionality by using the eSignature API to create configurable “dynamic signing groups,” which enabled them to assign signing groups dynamically without needing to update templates or PowerForms.
Sizing Up DocuSign’s New Mobile Optimized Signing Paradigm
Vasu Sampath, Principal Solution Architect, DocuSign, went over DocuSign’s new responsive signing experience. He discussed Smart Sections and the simplicity of manipulating the code; the ability to do significantly more with HTML than with static documents; the differences between this solution and our legacy approach, and much more.
Would it really be a proper tech conference without an ISV showdown? Today, we highlighted a group of successful independent software vendors with vertical or process-specific DocuSign integrations.
Procore Product Manager, Nyasha Gutsa, MoxiWorks Director of Moxi Cloud Partnerships & Integrations, Kylah Searing, General Networks Corporation President, Todd Withers and Nintex Technical Evangelist, Ryan O’Leary faced off against one another in a series of demos featuring their innovations. The judging panel consisted of DocuSign VP of Developer Programs and Evangelism, Marie Huwe, DocuSign Chief Product Officer, Ron Hirson, SVP of Engineering, Tom Casey, and VP of Global Partner Solutions, Ryan Cox. While the competition was tight, Procore walked away with first place.
The fun continued in evening, with Michael Franti & Spearhead performing live for the Momentum crowd!
As always, be sure to check out these resources for complete information and continual updates: