You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/lab_rpa/Exercise_1.md
+26-27Lines changed: 26 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,9 @@
1
1
---
2
2
layout: default
3
-
title: Exercise 1
4
-
parent: Automation Engine Overview
3
+
title: Automation Center
4
+
parent: Automation Engine Labs
5
5
nav_order: 11
6
6
---
7
-
8
7
# Automation Center
9
8
10
9
## Introduction
@@ -26,18 +25,18 @@ For our particular use case, the Process Owner who owns the **Setup Direct Depos
26
25
27
26
## Submitting an Automation Request
28
27
29
-
In this section of lab you will submit an automation request and review an existing one. we are going to walk you through the screens of Automation Center to help you understand what it does and how it works.
28
+
/n this section of lab you will submit an automation request and review an existing one. we are going to walk you through the screens of Automation Center to help you understand what it does and how it works.
30
29
31
30
32
31
1. Log in to your instance as **Admin** then click on **Favorites** (1) then on **Submit an Automation Request** (2). (You might have to scroll down to see it at the bottom of the list)
33
32
34
-
33
+
35
34
36
35
Typically a Process Owner that have identified a need for automation will go here to submit an Automation Request. In our scenario, it could be the Process Owner who owns the 'Setup Direct Deposit' Process. By submitting a request the Process Owner can share detail about the process and the need for automation. The Automation COE would then review the request, vet it, and priorities that request.
37
36
38
37
1. The **Submit an Automation Request** form should look as shown in the picture below. Note that this is an out of the box form that comes with Automation Center.
39
38
40
-
39
+
41
40
42
41
43
42
1. Fill out the form with those information (We are just showing how to submit the request, it does not matter what you type on that form for the exercice).
@@ -55,11 +54,11 @@ This form is used to gather as much information we can about the process so the
55
54
56
55
Notice on the form that the user has the ability to attach any relevant files that would help the Automation team understand the process to automate. It can be process documentation, screenshots, recording of manual steps etc:
57
56
58
-
57
+
59
58
60
59
1. Once you have filled out the form click **submit** to submit your request to the Automation COE team
61
60
62
-
61
+
63
62
64
63
Now that we have submitted an Automation Request, It is time to review it as if we were the Automation COE team using Automation Center to track those requests and review them.
65
64
@@ -71,22 +70,22 @@ Automation COE teams can prioritize, and manage automation requests from differe
71
70
72
71
From your instance, Click **All** (1) then type **automation center** (2) then click **Automation Center Home** (3) to open the Automation Center Workspace.
73
72
74
-
73
+
75
74
76
75
The landing page of Automation Center shows a lot of useful information for the Automation CoE lead to oversee goals, performance, and pipeline. It provides the big picture and helps visualize benchmarks for automation business goals and activity in one place.
77
76
78
77
1. Review the Automation Goals - The **Automation Goals** section shows the progress automation goals, What has already been achieved, what is going well, what can be improved. The progress is shown only for the goals that are associated with a request from the current year. Feel free to click the numbers on the goals widgets to view the data and filters:
79
78
80
79
81
-
80
+
82
81
83
82
1. Scroll down to until you see the Active Automations information, we are going to change the date on the filter to make sure the widgets has demo data to show. Click on (1) **Date:** filter, then on (2) change the value to **Last 3 months** and click **Apply** (3) as showm below:
84
83
85
-
84
+
86
85
87
86
Those widgets report of deployed automations by business, job summaries, cost savings, and time savings.
88
87
89
-
88
+
90
89
91
90
> The Cost Saving and Time Savings are not showing any data because we do not have the right Demo Data on those lab instances right now.
92
91
@@ -99,81 +98,81 @@ Automation COE teams can prioritize, and manage automation requests from differe
99
98
Under **Top 10 Application used** (2),by default the widget reports the top 10 business applications used. We are able to bring the visility into Applications that are used by automation because directly from the **Automation Request** we can link that Automation Request to one or many Business Application(s) (Business Application that are referenced in the CMDB)
100
99
101
100
102
-
101
+
103
102
104
103
Scroll down until you see **Future Automations**:
105
104
106
105
This is where the Automation COE team can see their pipeline of automation requests by intake source and request to be deployed.
107
106
108
-
107
+
109
108
110
109
Automation Center is also able to collect and report on Automation Execution, from ServiceNow's RPA solution but we also provide a framework and datamodel to allow customer to collect data from 3rd Party Automation solution To fetch execution data from 3rd party solution this would involve mostly buidling a flow in Flow Designer to collect data from an API in order to populate the sn\_ac\_automation\_execution table.
111
110
112
111
At the top of the Automation Center pager locate the and click the **Executions** Tab as shown:
113
112
114
-
113
+
115
114
116
115
The first for widgets provide visibility into Executions Jobs, Automation Incident, Automation Changes and Business Application Changes, this are very valuable information for when organization run Automation at scale, we are able to provide this level of detail because ServiceNow Incident, Problem, Change (ITSM) run on the same platform has one single datamodel
117
116
118
-
117
+
119
118
120
119
Click in the blue portion of the Circle Chart on the Job summary widget as shown to open the view that shows the running executions:
121
120
122
-
121
+
123
122
124
123
Notice the source column, Automation Center shows the running Automation executions from 3rd party RPA solution:
125
124
126
-
125
+
127
126
128
127
> The date displayed on the view comes from the sn\_ac\_automation\_execution table on the platform, metadata from 3rd party automation tool are stored in that table
129
128
130
129
After looking at the **Job Summary** view, you can now close that tab as shown below:
131
130
132
-
131
+
133
132
134
133
Now that we have reviewed the **Automation Center Dashboard**, lets review an Automation Request
135
134
136
135
1. From the Automation Center Workspace, click on the List icon (1), then click **All Automation Request** (2), then locate the Automation request (3) **ATR0002003 - Setup Direct Deposit** and click on it to open it
137
136
138
-
137
+
139
138
140
139
This is where an Automation COE team member would go to review an **Automation Request**, manage and track all the activities from the technical requirement gathering, development, testing and execution of the automation.
141
140
142
141
As you can see from that screen, the Automation team can review all the detail that was submitted by the Process Owner in the Automation Request:
143
142
144
-
143
+
145
144
146
145
> Notice the **Application used** field it contain the Business Application from the CMDB. This is very useful information for the Automation Team so if they need to identify the application Owner or get information about the systems to automate, it's all in the CMDB!
147
146
148
147
This give a good overview of the ask from the Process Owner, from that Automation Request, the Automation Team can then start planning the different activities to deliver the automation, click on the **Tasks** tab as shown to review them
149
148
150
-
149
+
151
150
152
151
You should see a list of 3 tasks, this is where the Automation CoE can orchestrate and manage all the activities required to build the automation. They can create tasks and assign them to differents teams (based on the requirements gathered in the Automation Request) Often time building Automation takes differents skillset such as Integration, RPA, Workflow development, or even the team responsible for the application we need to automate. It can be many different teams involved in the process. Automation Center help manage that.
153
152
154
153
Click on the Automation Task number **ARSK0001015** to open it:
155
154
156
-
155
+
157
156
158
157
You can see you can set a priority, Due Date and Assign the task to a Team or a person. Lets Assign this task to the RPA Team so they can start working on building a Robot in RPA to automate that legacy HR/Payroll app!
159
158
160
159
1. We are going to set an Assignment group the a team can start workin on this task
161
160
162
-
161
+
163
162
164
163
Locate the **Assignment group** field (1) Type **RPA Team** (2) to search for the rpa team on the list, then select the value **RPA Team** from the list (3) and click **Save** (4):
165
164
166
-
165
+
167
166
168
167
The RPA Team now will see that they have a new task assigned to them and can start working on it.
169
168
170
169
Close that tab by clicking on the x next to **Create RPA Robot** as shown:
171
170
172
-
171
+
173
172
174
173
As an Automation CoE, you can mark that Automation Request as **In Progress** so the Process Owner who submitted the request knows that the team is working on it (Notification can be configured on the platform). Click on the **Move to In progress** button as shown below:
0 commit comments