SPEAKER 1: Let's take a look at how
UiPath's internal automation center of excellence or CoE,
saves more than a week's worth of work
every year using our own technology.
SPEAKER 2: So let's say we have a new automation idea that
was assessed, and we've decided to move forward with this
and start the analysis of the process,
and the development of the process.
In this case, we'll also have to track
all the parts of the process in our internal Jira system,
and be able to create all the stories required
for the analysis.
And that would mean that we will be creating
in our Jira, an Epic type of request that will contain
inside of it, all the stories related
to analysis phase, development phase, deployment and so on.
And for that, we have an automation in place.
The first, we will need to copy the automation hub
link that will be needed in the steps of the process.
Then we can go ahead and access apps.
This app can also be started from UiPath Assistant,
so I'm going to go to CoE app.
This app contains two processes.
The one that I'm interested in is to create Jira issues.
And the other one, it's another app used in the CoE.
We will need to enter the automation hub link here,
so I copied it before.
The process name, the one that we
had in automation hub and the process description
needs to be entered as well.
As a user, you'll also have to select the division
to which this process pertains.
In this case, I know that its people operations.
If I select generate confluence pages,
I'll show you later how the automation will
be created on the required pages in our internal confluence,
like a template for the process definition
document, the deployment plan, the solution architecture plan.
And if I click the submit button,
the process will start running and will
be creating an Epic together with all the tasks required
there.
The process has to go and create more then sub-tasks
in even Jira, inside the Epic.
And also will have to create all the related confluence pages.
We have it now, and I can go into our CoE page, CoE Jira
project and look up the new project that was created.
So here it is.
It contains the name that-- it has
been named based on what I have shared,
that is the description.
And this is something that we've predefined in the back-end.
All the stories that are required to be created
were created by the automation, containing
the name of the project again.
And it has linked everything to the Jira Epic.
So this is the automation hub link
that I pasted in the beginning, and then furthermore it
has created and linked all the required documentation
in confluence.
So if we go to the PDD first for example,
it has been added under people operations section.
And so as you can see here, internal automation, people
operations.
It has created the PDD template that a business analyst could
then start updating, followed by the template for the solution.
Design document, the DSD and the deployment plan.
So following the steps of the automation flow,
all these documents are going to be manually updated,
but at least we have the templates created for us
from the beginning.