[MUSIC]
>> Welcome to today's session on
Expanding Power Automate with DocuSign.
My name's Mohamed Ali.
I'm a Lead Solutions Engineer with DocuSign.
I've spent the last maybe 15-20 years cutting code,
consulting, and really helping
a range of companies with their digital strategies.
Apparently, I've been helping
federal government agencies and
the financial sector where
Microsoft is literally the de facto standard.
I'll run you through a bit of an overview today,
given the idea of the background around
where we see DocuSign fitting into the bigger picture,
the current Power Automate Connecter today,
the DocuSign connector, where it really shines,
some areas where we've identified some gaps and how we
can really address them right now
today with existing functionality.
That's what I'm really excited about as well,
so I'll leave you with some assets
around doing it yourself as well.
I'll give you a bit of an overview.
From the feedback we've gotten from our almost
900,000 customers that we have worldwide today,
what we've understood is there are a lot of
different business tools that are being used,
175 on average and that's
an enormous amount just to get your job done.
What do you think about their connectivity?
A lot of the time, there isn't any or it's limited,
and what that leads to is a lot
of wasted time, productivity,
and a lot of frustration by users,
which is understandable and it tallies
up to 32 days per user per year,
just switching between apps.
You can see how that money and
effort waste and value's really adding up.
DocuSign works really well on its own.
It works even better when it's
integrated and embedded into your ecosystem.
The good news is DocuSign already has
450 plus pre-built integrations.
That's the ones we know about.
There's literally hundreds of others
that we don't even know about out there where
vendors have built us into their solutions.
What we're doing is we're doing our part and
to help solve some of
those disconnects between the disparate systems.
But importantly, Microsoft is a huge partner of ours,
along with some of the other major players like Google,
SAP, Salesforce, Workday, to name a few.
When I say DocuSign works better when it's integrated,
that's especially true with Microsoft.
It's really like a hand and glove relationship.
If you're simply in Word today or in
Outlook and you want to send
the document out to get it signed,
that's a simple click on a button and
hit the "Send" option and you're done.
If you're looking for something more complex,
like pre-filling a document,
merging data from Dynamics into a code,
and then sending in that out for
signature and then have
that being stored back into SharePoint,
you can do all that with
the pre-built connectors that we have today as well.
It's really powerful as it is
today with the range of products that we
support but where you're looking for
more control and even more automation,
that's really where Power Automate works really well.
The DocuSign Connector for
Power Automate today as is, is great.
It extends all the Microsoft
and the part of the products literally hundreds out
there on the Power Automate platform and
allows them to electronically approve, sign,
and utilize a lot of
the existing DocuSign functionality that we
have where it really helps
today and some of
the ones that I've highlighted on the screen.
The ability to send templates out.
Where that's really great is if you think about
an on-boarding for a new employee,
you may send them a template for them to
complete information about themselves,
the tax details and so forth,
attached that proof of address and
other information that's required
from them as an on-boarding pack,
that'll be sent off to a manager for
approval and then to payroll for processing.
That can happen automatically today within DocuSign.
Another great example is around the post-signing,
you can listen for
real-time updates directly from DocuSign,
so you imagine when that employee completes
the signing process and
that on-boarding process is complete,
you'll get notified directly from within Power Automate,
and that can trigger off some actions to happen next,
so you could deploy a laptop
and other access to
other systems for them if needed as well.
You can control that entire process
using the existing pre-built
connector that we have today.
Within that connector, we have
15 plus different triggers
and actions that you can utilize straight away,
but we've identified some gaps.
Before I jump into those,
the good news is we've recently taken over
the source code from Microsoft folder connector
and what that means is,
watch this space, there's going to be
some really good enhancements coming this way.
That's really exciting in itself but right now today,
there are a couple of gaps I'll talk
about them and I'll tell you
how we can really address them.
Number one, merge fields and data write-back.
Essentially, what that is, is the ability to take data,
whether it's in SharePoint,
for instance, merge it,
pre-fill it into a document,
might be the address of
that employee that you might already have.
That's something that you can't do today,
but in saying that,
Microsoft Dynamics,
the integration that we have with
that already allows for that.
From a CRM point of view,
you're covered, merging data,
data write-back, that whole sinking process,
you don't have to worry about it. That's great.
Sending envelopes.
When I say an envelope in DocuSign speak,
it's essentially the ability to send
one or more documents out through a workflow.
Getting it approved, getting it signed.
Think about a procurement contract, for instance,
you might prepare it in
words and sitting on a SharePoint site,
you want to be able to send that out automatically.
You can use the pre-built
SharePoint connector but if you're looking for
something a bit more automated
or with a lot more control around it,
that doesn't exist today.
Again, a bit of good news around that one is,
I'm going to show you that specific example and how we
can address that today
with the functionality that we have.
That's what I wanted to introduce to you,
the actual DocuSign REST APIs.
You can actually harness the full capabilities of
that REST API directly from
Power Automate with only a light amount of code.
What's important here is
our DocuSign eSignature platform,
is built based on our API from the ground up.
What that means is,
the majority of what you can do
using our platform and our interface,
you can do via the API.
For instance, if you had
a requirement around SMS delivery,
someone getting an SMS link for them to sign
a document as opposed to an e-mail
for them to sign a document,
you can do that right now today using
our API and you
can just embed that as a step in your flow.
That becomes really powerful in accessing
all the innovations that we have
today and future ones that are coming as well.
There's two simple steps to set this up.
Number one, is to create a custom connector,
which is the Power Automate feature
that's available today and you just point
that to DocuSign using
the highly secure or authentication methods.
Number two is you follow that wizard along to
create the custom connector and then the last step,
it will ask you for the structure of the API call.
What you can do here is you can
utilize our developer hub,
which has many, many code recipes, examples,
working code that you can just copy and paste into
that last step and
the connector will understand the structure of it,
save it, and that's pretty much it.
Then you'd be able to teach it,
this action is for sending a template with merge fields.
This action is sending
a dynamic document grabbed from a SharePoint site.
You teach it once and then you can
reuse that action many times.
I'll show you that actually today.
Before I jump into a live demo
to give you an idea about how it works.
I've got a basic flow on the screen right
now where a trigger is at the top in the SharePoint side,
if a new file is created in a folder,
it'll trigger off this flow to be executed.
We get the file content,
and then from there the last two steps
are related to that API call.
Once I expand them out,
what we're looking at here is,
compose is basically taking
that file and converting it to base 64 format.
The last step is that custom connector step.
You can say it's quite well structured,
it's got fields for you to complete.
What I've done here is I've showed you some key areas.
We can dynamically grab data from
SharePoint or other systems and pop them into there.
In this example, I've grabbed the output from
that file content and I've popped it
into that first area there.
I've got a signer e-mail and signer name
that I've grabbed from SharePoint,
and have popped it into there.
If I need to add an additional signer
or an additional document,
I simply click the "Add New Item" button there.
It's really powerful from that point of view.
Once you set this up, you don't really need to
add any more code or remove anymore code.
It understands that the structure
and you can dynamically add and
remove the amount of
documents and recipients that you need.
Let me jump into a demo
right now and I'll show you what that looks like.
We're looking at my screen here.
What I'm looking at here is a quote.
Now this quote is being sent off for,
I want it to be sent off for execution.
Now, the trigger that I've built into
my flow in Power Automate is,
when that status is changed from
draft to send for signature,
that will trigger off a process to
send that document out for execution to the supplier.
Let me do that now, to
the customer should say, so let me do that now.
Change that to send for signature.
By changing that status,
within about 30 seconds or so,
I'll receive an e-mail for me to sign that document.
Now, in the meantime,
what I'll do is I'll show you behind
the scenes how that works.
Let me take a step back here to the start.
This is my flow that I've created.
The first step is the trigger
is when an item or a file is modified,
so the status is modified for that document.
I will get the document properties,
which is what you see there.
That's getting all the different properties there.
Then from there I can actually check the status of it.
Checking the status is
just a standard step within Power Automate.
I'm checking whether the status
equals sent for signature.
If it does, then I get the file content.
That's normal, I compose the basics default format,
and then I send the document now.
We can see here that I'm sending the document out.
I've got all the variables that I talked
about in the previous slide built into this here.
I've got the signer e-mail
and the signer name and so forth.
That's all being grabbed from the signer name,
the signer e-mail, the file name.
We'll just dynamically pop that into here.
If I wanted to add an additional document,
I'd simply click "Add",
and it would say it would enumerate
its number two, and that's pretty much it.
That's all that's really needed.
Now, heading back to my demo,
I've sent this out.
Now let's see what it looks like from
a signing experience point of view.
I'll minimize this screen here.
I'll pop on my mobile phone
because people are always on the go.
The ability to actually sign on your
phone becomes really powerful.
That's me on my mobile phone at the moment.
I'll click on that document that I've just received.
Then you will say that I can
then hit the review document link,
and it will launch into that.
All you need is a browser and
an e-mail address in order to sign
a document using DocuSign you don't
need an account or anything like that.
First step is to provide my consent
to use electronic signing.
US city clicks on the screen because I'm
actually using my phone at the moment.
But what you will say is that it converts
it to mobile-friendly responsive mode.
It'll work on any size screen that you have.
It will just convert it to really look great.
You can say how easily that is to read.
If I untick the mobile-friendly option,
you'll see that, you have to pinch
and zoom to read every single word.
It's just not a great experience.
Can you imagine if this was 10 or 20 pages long,
this would be, no one's going to sign off on that,
you'd have to wait till they get back to their desk,
which delays the process even more.
This way, if I click "Next",
I just sign away,
and then I can just draw my signature there.
It doesn't need to match the way a handwritten signature
looks from electronic signing point of view,
What's important is we kept
your consent to sign a document, a and b,
all the evidence that DocuSign captures in
the background to prove
that you're the one who signed it;
so your name, your e-mail,
your IP address, your location, timestamps.
We can collect additional information
like you find number.
We can do ID proofing,
so a whole host of ways that
we can tie you to the signature,
improve that you're the one who signed it.
Press "Next" and finish.
That pretty much completes that process there.
That's completed that process there.
I'll share my screen and just finish off that demo again.
Let me just share my slides again, and great.
I've shown you the demonstration there.
What we're looking at here is some
real life examples that
we've helped customers with
using Power Automate, and DocuSign.
The first one was around
Contract Management and Execution,
similar to the example that I just showed you there,
this was actually a multinational
construction group that we worked with.
The ability to track
a project status and when the
project status changes in the list,
it will automatically send all the documents
out in a specified folder to a subcontractor,
or multiple subcontractors,
track the status of that and then once it's completed,
push it into Google Drive.
That was their specific requirements.
We were able to very easily do that with
minimal code using Power Automate and DocuSign.
Quite a simple example,
but very powerful in the ability
to automate that end-to-end process.
Another one was around an insurance organization
having customer online forms, that they'd built out,
and then the ability to take the data from that form,
pre-fill it and merge it into a DocuSign template,
have them sign that,
make any final changes and then write
that information as well as assign
document back into Microsoft Dynamics.
Again, very straightforward.
Then the last one was around recruitment and on-boarding.
The similar example to what I talked about earlier,
around that implement pack going
through that approval workflow,
from an employee to a manager to payroll.
Those are very common examples that we come across.
But the truth is,
DocuSign has
helped our customers with literally hundreds,
if not thousands of
unique use cases around the entire business.
You might think of us around legal contracts or HR.
But if you're looking at the examples here,
the kind of use cases we help
with underpin an entire business.
From the front office, whether it's sales,
or services to the back-office,
if it's HR, procurement, finance, or legal.
We do help with the entire business end-to-end.
Now, when you couple that with
Power Automate and our Microsoft partnership,
that end-to-end digitization and
automation becomes really powerful.
I'd like to leave you with some very useful guides.
The first one is a step-by-step guide around
exactly what I've gone through in
more detail around how to set it up.
Very similar to what I was talking about there,
only differences is it's
http step as opposed to a custom connector step.
But the rest it is pretty much
identical and you can use that example today anyway.
The second one is that
develop a hub that I was talking about.
Loads and loads of content guides, API 101.
There's a lot of videos to get you up and
running and working code to get you up and running.
Postmen rest API collection,
so you can download that today and put it in
your postmen and you'll have access to
all those rest API
calls that you can copy and
paste into your custom connector.
That should be more than enough to get you up and
running. Thank you very much.