[Music]
Hi my name is Matthew Roknich, I am a
Developer Evangelist here at DocuSign.
I'm here today in sunny Seattle with
David Miller, who is a Senior Software
Engineer. David, thank you so much for
being here today. >> Matt, thanks for having
me.
>> Excellent so David how long have you
been a software engineer? >> A long time. I
started in high school and luckily just
missed the punch card era, but got
interested in it and decided to head for
a software engineering computer science
degree. >> And correct me if I'm wrong, you
mentioned that you were also part of
different startups along the
way. >> Yeah I started two companies, neither
of them made it, but we're
fabulous experiences and
since then I've been in bigger
companies in more startup type
roles and really enjoyed that
environment. >> So how long have you been
developing at DocuSign? >> I've been at
DocuSign for about a year and a half now.
>> Excellent and having been here for
a year and a half, what is the best part
about being a DocuSign? >> Just coming to
work every day. Interesting problems to
solve, working with smart energetic
people. We all work as a team
really well, I feel like so it's
enjoyable to come to work, which is not
always the case at some companies.
>> Absolutely and what is your current area
focus? What are you working on in your
new team? >> I'm working on responsive
signing, so I'm on the signing team here
at DocuSign
and the main focus is taking the API
responsive signing in to the public
front-end application and adding the
responsive features to that. >> Awesome so
responsive signing, what exactly is that?
>> So responsive signing is a new way for
our DocuSign recipients to interact with
their documents. In the past when they
were signing on mobile devices, tablets,
or other small screens, the recipients
would need to pinch and zoom and scan
through out their documents. It was a
difficult process on a small screen.
Responsive signing allows you to quickly
read and view on any device without any
specialized gestures. >> So David, what makes
the document responsive? >> So either
through sending HTML through the APIs
or us converting PDFs or Word documents
to dynamic HTML, we create a responsive
document that will fit to either a
mobile or a tablet device, expand or
contract. >> Great and then the smart
sections portion, what is that? >> Smart
sections allows you to take this HTML
and through your documents be able to
mark it up and provide functionality.
Like if you have a long legal document
you can compress sections into
collapsible sections, you can put break
buttons in there, you can do things like
rotate tables that would be a real wide
table into a tall table, which should
fit on a mobile device better. >> Great and
then responsive signing and smart
sections, are these features a part of a
new API or part of an existing? >> These are
part of our existing eSignature API,
they're a premium feature that you need
to talk to your account representative
about. >> Awesome, so David can you show us
how developers can use responsive
signing and smart sections in their apps?
>> Yeah absolutely I've got a good example
here. So we're gonna start with just a
basic Word document, it's got markup in
it we'll see that in a little bit, but
this document I've put into my Postman,
its the tool I use for doing API calls
for testing things out. So you'll see
I've got the binary encoded base64 word
document in there, that's this right here,
and the key piece of information. This is
just a create and send envelope call, one
of the most common things you do with
DocuSign. There's an additional
section here called HTML definition
which describes our smart section work,
our responsive work, I should say, and
says our source is a document. This could
be HTML if you're sending a source HTML
and then additionally I've got a switch
on here called showMobileOptimizedToggle
which allows the signer when
they're signing the document to switch
between either PDF view or responsive.
>> Standard signing experience versus new responsive.
>> Yeah so you can switch between
the two. So we can send that and take a
look.
Okay so we have our document here and I
haven't done anything to it other than
send it responsibly. So you can see the
toggle switch that I talked about is displayed
here so we can switch between
regular PDF view, which is
pretty zoomed out and you've got to
pinch and zoom to get
around it. And a responsive document,
which is the HTML that was generated
from our source document and you can see
that based on your form-factor it resizes and
adjusts to the screen. So now we're going
to- this is a document it's pretty
long, it's got a bunch of information in
it, a lot of scrolling and so forth so
we're gonna do some smart section work
on that to make it look a little bit
better. So what I'm going to do is I'm
going to collapse a lot of that text down
at the bottom into more digestible
sections here. The way I'm doing that
is again in this HTML definition we've
got displayAnchors, which are our smart
sections. And we've got startAnchors and
endAnchors which define within the
document, so this text is in the document,
which specifies where this section is
going to be applied. And then you
can remove it from the document. A bunch
of other settings that you have there.
Additionally, on the display settings
we're going to specify it like my first
section I'm going to say it's gonna be
collapsed and then I've got HTML to
define the actual section that
represents that. My second section, for
example, is collapsible, which means it's
going to be expanded and can be
collapsed. So let's take a look.
Okay so this is going be our document,
which is the same document, the only thing
I've done is added those sections and so
we'll see how that turned out. So we go
down here to the sections. Here's the
first section I described in the Postman
call it's a collapsed section so you can
see it can be expanded, it was already
collapsed. Second one is expanded and can
be collapsed. So you'll see that all that
text down at the bottom has been- >> It
cleans it up quite a bit. >> Yea, but you also
notice that we have some other stuff in
our document here this is a
header and footer that we're going to
take care of next. So a lot of times you
may not want to see that in your
responsive document, it just kind of
tightens up the document a bit. So we'll
go and do that. So all I've done in the
next API call, it's again just a create
envelope call same call we're just adding
things to the the previous ones, is I've
added a section. Marked it
with SF for start
footer and EF for end footer for my
markers within the document. Then I just
said type was print-only, which means
that this is going to display on your
final document, your PDF form it'll still
display, but in your responsive it'll
just remove it. >> So this step it'll remove
that portion of the document? >> Yes we've got all our other smart
sections and we've added this smart
section to it. Okay so now as we go down
here you'll see that. >> Voilà, it's gone!
>> The sections are done it's nice and clean and so we
don't have any those headers and footers
in there anymore, so you've got a
nice concise document here that's easily
digestible. You can expand the things
that you want to read in more detail or
not. So this is the remainder of
the document collapsed. >> Very cool
so for you developers out there that are
interested in utilizing responsive
signing and smart sections head over to
developers.docusign.com and contact
your account manager if you want to pump
it up to these premium features,
but otherwise David thanks much for
being here today. >> Absolutely was very fun, have
a good one. >> Thanks. >> Hi, thanks so much for
watching the video. If you'd like to
learn the latest and greatest in DocuSign
technology I would highly encourage
you to attend our Momentum conference
and Hackathon in June in San Francisco,
it's completely free for developers.
[Music]