>> Hi, I'm Chris McNulty,
Senior Product Manager on
the Office 365 team here at Microsoft.
When working with common back office procedures,
it's important to be able to collaborate with confidence,
being assured that the system will automatically take
care of routing common workflow requests,
being able to introduce document sign off,
and ensuring dynamic protection of
information based on content with data loss protection.
Let's take a look. Here, I'm
reviewing a list of new hires showing the organization.
I can use a customized process to request that
IT gets specific information for my new hire.
By requesting new equipment from IT,
I'm prompted what kind of equipment Jason wants,
and we will select a tablet for him.
Once I choose that device,
this Flow generates a task for the IT department to
get them a new piece of equipment by their hire date.
Now here, within the IT site,
I can go into their planner to see their request.
If I scroll over to the onboarding bucket,
I can see the request for
Jason Moore to receive a new tablet,
and since IT knows this was already known about,
mark it as completed with
the process being closed out for the user.
Another common business process is attestation.
Here, I'm browsing into
a document library to route a document for approval to
Jason via our integration
with Adobe's Sign e-signature product.
Let's pick the profit-sharing plan,
and say that I want to get signatures
on the selected file.
There's Jason in the list,
and when I run the flow,
the document will be converted to
PDF with a placeholder added for an e-signature,
and delivered to Jason.
Let's look at that from Jason's perspective.
Now, I'm inside Jason's email,
and you can see the mail for me requesting that he sign
off on the profit-sharing plan
since he's joined Contoso today.
He's prompted to click here
to review and sign the document.
This part of the process is
integrated into the Adobe Signature cycle.
Now, as Jason, I see the document prepared for signature.
I scroll down, add my signature,
and supply an e-signature.
Once accepted, the signed document is routed
back to me for final logging. Let's take a look.
Here, I can see that Flow has orchestrated
the entire signature process between Contoso and Jason.
I've received notice that the fully signed document has
been returned back to me for
further logging and processing.
We can also build even more complex business processes.
Here, I'm going to use
a Flow designed to send a series of
onboarding documents to a new hire over several weeks.
However, we know that
some hires have urgent needs for benefits,
which would require us to select something different for
them to allow them to immediately subscribe to benefits.
Here, I ask a question at the outset if the employee
has an urgent benefit question, and I run the Flow.
Rather than take three weeks to look
at all the documents we're going to distribute to Jason,
let's take a look behind
the scenes at how the Flow is built.
Here, we're looking at the Welcome to
Contoso Email Campaign process.
One of the things we'll look at is from the outset,
we can see I'm asking if
the employee needs accelerated benefits.
If the answer is yes,
they will immediately get the benefits email,
and then resume with the regular email distribution,
allowing me to distribute a series of documents over
the next several weeks with
a seven-day delay set in-between.
Your back office can also handle
lots of sensitive information.
With our automatic classification and protection engine,
you can transact with confidence.
Here, I have a standard Word project document
found in the strategy area.
I'm going to add a credit card number to
this document, and save it.
You'll notice that my centralized policy
will automatically notice that
this file has identified
credit card data inside of it and put a watermark,
reminding me anytime I'm
working with a document like this,
I want to use special care.
Alternately, I could use this label to enforce
mandatory encryption of this financial document,
and add other policy based on
sensitivity such as key projects,
personal data or healthcare information.