|
|
|
---
|
|
|
|
title: User guide for process designer
|
|
|
|
---
|
|
|
|
|
|
|
|
# Contents {#contents .TOC-Heading .unnumbered}
|
|
|
|
|
|
|
|
[Pre-requisistes: [1](#pre-requisistes)](#pre-requisistes)
|
| ... | ... | @@ -26,598 +22,300 @@ title: User guide for process designer |
|
|
|
|
|
|
|
[9. Report a case [28](#report-a-case)](#report-a-case)
|
|
|
|
|
|
|
|
[10. Case officer receives a new disciplinary case
|
|
|
|
[30](#case-officer-receives-a-new-disciplinary-case)](#case-officer-receives-a-new-disciplinary-case)
|
|
|
|
[10. Case officer receives a new disciplinary case [30](#case-officer-receives-a-new-disciplinary-case)](#case-officer-receives-a-new-disciplinary-case)
|
|
|
|
|
|
|
|
[11. Other relevant ServiceNow user documentation
|
|
|
|
[31](#other-relevant-servicenow-user-documentation)](#other-relevant-servicenow-user-documentation)
|
|
|
|
[11. Other relevant ServiceNow user documentation [31](#other-relevant-servicenow-user-documentation)](#other-relevant-servicenow-user-documentation)
|
|
|
|
|
|
|
|
# Pre-requisistes: {#pre-requisistes .unnumbered}
|
|
|
|
|
|
|
|
1. User has the role customer manager (technical role name if you need
|
|
|
|
to contact support: x_steas_uh_core.customer_manager)
|
|
|
|
1. User has the role customer manager (technical role name if you need to contact support: x_steas_uh_core.customer_manager)
|
|
|
|
|
|
|
|
2. Logged in user has English as their preferred language
|
|
|
|
|
|
|
|
# Guide {#guide .unnumbered}
|
|
|
|
|
|
|
|
All screenshots attached to this document are intended to help the user
|
|
|
|
find buttons and functions in their own screen, and the screen that the
|
|
|
|
user sees may look different, based on their roles, accesses, what
|
|
|
|
version of ServiceNow the instance is, and how the instance is
|
|
|
|
configured.
|
|
|
|
|
|
|
|
To define a process navigate to **the UH Core \> FUP** (use the search
|
|
|
|
functionality under \'**All**\'). Choose which process you want to
|
|
|
|
create a flow for. Then click on the \"**Define process**\" button.
|
|
|
|
|
|
|
|
{width="6.678807961504812in"
|
|
|
|
height="2.7666404199475068in"}
|
|
|
|
|
|
|
|
User is further taken to App Engine Studio. Here you get the opportunity
|
|
|
|
to choose which template you want to use. Each template should give a
|
|
|
|
small description about its content. You also have the opportunity to
|
|
|
|
create your own template.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.421527777777778in"}
|
|
|
|
|
|
|
|
For this user guide, \"**UH define** **process**\" is used, where
|
|
|
|
components such as schema, process definition and a table are included.
|
|
|
|
To select this template, hover over the field and click \"**Use
|
|
|
|
template**\".
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.4555555555555557in"}
|
|
|
|
|
|
|
|
On the next step add your name and description. The name should reflect
|
|
|
|
the process following the best practices of their institute. In the
|
|
|
|
example below, we use names from the functional analysis and provide a
|
|
|
|
brief description. After filling in the fields, click \"**Continue**\".
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.859722222222222in"}
|
|
|
|
|
|
|
|
It may take up to a few minutes to generate the application. After it is
|
|
|
|
created click on \"**Go to app home**\".
|
|
|
|
|
|
|
|
{width="3.1527777777777777in"
|
|
|
|
height="2.8340277777777776in"} {width="3.0694444444444446in"
|
|
|
|
height="2.8361111111111112in"}
|
|
|
|
|
|
|
|
The first thing the user sees when the application is created will be
|
|
|
|
similar to the image below. It will automatically be generated a table,
|
|
|
|
a form and a process definition that users can use in any way they want.
|
|
|
|
For more information about the different parts, read the following
|
|
|
|
article:
|
|
|
|
<https://docs.servicenow.com/bundle/utah-application-development/page/build/app-engine-studio/concept/create-application.html>
|
|
|
|
|
|
|
|
For this user guide, we will establish a process for handling
|
|
|
|
disciplinary cases with students. We need to add some fields to the
|
|
|
|
table and enter questions in a form for a student to see. Furthermore,
|
|
|
|
with the process definition, we will extract the student\'s name from
|
|
|
|
OrgReg spoke. To start, click on the existing table \"**Case**\".
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.8652777777777776in"}
|
|
|
|
|
|
|
|
Here is a list of the fields that are already available and inherited
|
|
|
|
from the core system. If you only want to see fields that are unique to
|
|
|
|
this process, you can tick \"**Show non-extended table fields**\" in the
|
|
|
|
upper right corner. We want to add more fields to collect information
|
|
|
|
from the student as user input and through integrations from subject
|
|
|
|
systems. This is stored as data in the application and visible to case
|
|
|
|
officers. For this scenario, we are interested in knowing the type of
|
|
|
|
disciplinary violation in question, here we want the student to be able
|
|
|
|
to choose between several options. We thus create a new field by
|
|
|
|
clicking on \"**+ Add new field**\".
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.7604166666666665in"}
|
|
|
|
|
|
|
|
Give an appropriate name to the field under \"**Column label**\", the
|
|
|
|
column name is automatically set when filled in. Then select
|
|
|
|
\"**Choice**\" in the \"**Type**\" field. This gives us the opportunity
|
|
|
|
to define several choices for this field.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.6756944444444444in"}
|
|
|
|
|
|
|
|
The next step defines which type of choice for the field is desired
|
|
|
|
(e.g. drop-down). Then you enter the various choices, here we have
|
|
|
|
defined three choices for disciplinary violations. For easier overview
|
|
|
|
when adding something not quantitative, one should switch \"**Value**\"
|
|
|
|
to a numerical value. Then click on \"**Done**\", and \"**Save**\".
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.279166666666667in"}
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.421527777777778in"}
|
|
|
|
|
|
|
|
In addition, we add a field that retrieves the student\'s name through
|
|
|
|
an integration from subject systems (this is looked at in more detail
|
|
|
|
when we define the process flow later in the supervision). This field
|
|
|
|
becomes of type \"**String**\", which is a text field.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.3833333333333333in"}
|
|
|
|
|
|
|
|
To easily find the table in later steps, we can define a suitable name
|
|
|
|
for the table. This is done by clicking on the **\"Properties**\"
|
|
|
|
button. Here you have the opportunity to change \"**Label**\" on the
|
|
|
|
table. Since this is a process of handling disciplinary matters, we call
|
|
|
|
it something that reflects that.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="0.7381944444444445in"}
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.571527777777778in"}
|
|
|
|
All screenshots attached to this document are intended to help the user find buttons and functions in their own screen, and the screen that the user sees may look different, based on their roles, accesses, what version of ServiceNow the instance is, and how the instance is configured.
|
|
|
|
|
|
|
|
To define a process navigate to **the UH Core \> FUP** (use the search functionality under '**All**'). Choose which process you want to create a flow for. Then click on the "**Define process**" button.
|
|
|
|
|
|
|
|
{width="6.678807961504812in" height="2.7666404199475068in"}
|
|
|
|
|
|
|
|
User is further taken to App Engine Studio. Here you get the opportunity to choose which template you want to use. Each template should give a small description about its content. You also have the opportunity to create your own template.
|
|
|
|
|
|
|
|
{width="6.3in" height="2.421527777777778in"}
|
|
|
|
|
|
|
|
For this user guide, "**UH define** **process**" is used, where components such as schema, process definition and a table are included. To select this template, hover over the field and click "**Use template**".
|
|
|
|
|
|
|
|
{width="6.3in" height="2.4555555555555557in"}
|
|
|
|
|
|
|
|
On the next step add your name and description. The name should reflect the process following the best practices of their institute. In the example below, we use names from the functional analysis and provide a brief description. After filling in the fields, click "**Continue**".
|
|
|
|
|
|
|
|
{width="6.3in" height="2.859722222222222in"}
|
|
|
|
|
|
|
|
It may take up to a few minutes to generate the application. After it is created click on "**Go to app home**".
|
|
|
|
|
|
|
|
{width="3.1527777777777777in" height="2.8340277777777776in"} {width="3.0694444444444446in" height="2.8361111111111112in"}
|
|
|
|
|
|
|
|
The first thing the user sees when the application is created will be similar to the image below. It will automatically be generated a table, a form and a process definition that users can use in any way they want. For more information about the different parts, read the following article: <https://docs.servicenow.com/bundle/utah-application-development/page/build/app-engine-studio/concept/create-application.html>
|
|
|
|
|
|
|
|
For this user guide, we will establish a process for handling disciplinary cases with students. We need to add some fields to the table and enter questions in a form for a student to see. Furthermore, with the process definition, we will extract the student's name from OrgReg spoke. To start, click on the existing table "**Case**".
|
|
|
|
|
|
|
|
{width="6.3in" height="2.8652777777777776in"}
|
|
|
|
|
|
|
|
Here is a list of the fields that are already available and inherited from the core system. If you only want to see fields that are unique to this process, you can tick "**Show non-extended table fields**" in the upper right corner. We want to add more fields to collect information from the student as user input and through integrations from subject systems. This is stored as data in the application and visible to case officers. For this scenario, we are interested in knowing the type of disciplinary violation in question, here we want the student to be able to choose between several options. We thus create a new field by clicking on "**+ Add new field**".
|
|
|
|
|
|
|
|
{width="6.3in" height="2.7604166666666665in"}
|
|
|
|
|
|
|
|
Give an appropriate name to the field under "**Column label**", the column name is automatically set when filled in. Then select "**Choice**" in the "**Type**" field. This gives us the opportunity to define several choices for this field.
|
|
|
|
|
|
|
|
{width="6.3in" height="2.6756944444444444in"}
|
|
|
|
|
|
|
|
The next step defines which type of choice for the field is desired (e.g. drop-down). Then you enter the various choices, here we have defined three choices for disciplinary violations. For easier overview when adding something not quantitative, one should switch "**Value**" to a numerical value. Then click on "**Done**", and "**Save**".
|
|
|
|
|
|
|
|
{width="6.3in" height="2.279166666666667in"}
|
|
|
|
|
|
|
|
{width="6.3in" height="2.421527777777778in"}
|
|
|
|
|
|
|
|
In addition, we add a field that retrieves the student's name through an integration from subject systems (this is looked at in more detail when we define the process flow later in the supervision). This field becomes of type "**String**", which is a text field.
|
|
|
|
|
|
|
|
{width="6.3in" height="2.3833333333333333in"}
|
|
|
|
|
|
|
|
To easily find the table in later steps, we can define a suitable name for the table. This is done by clicking on the **"Properties**" button. Here you have the opportunity to change "**Label**" on the table. Since this is a process of handling disciplinary matters, we call it something that reflects that.
|
|
|
|
|
|
|
|
{width="6.3in" height="0.7381944444444445in"}
|
|
|
|
|
|
|
|
{width="6.3in" height="2.571527777777778in"}
|
|
|
|
|
|
|
|
Navigate back to App home by clicking the first tab.
|
|
|
|
|
|
|
|
## Access control
|
|
|
|
|
|
|
|
New tables are created with a default set of ACLs. If access to the
|
|
|
|
table should be managed through RoLF, theses needs to be deleted or
|
|
|
|
deactivated. We here describe how to acheive this.
|
|
|
|
New tables are created with a default set of ACLs. If access to the table should be managed through RoLF, theses needs to be deleted or deactivated. We here describe how to acheive this.
|
|
|
|
|
|
|
|
1. From AES, edit the table
|
|
|
|
|
|
|
|
2. Open advanced view
|
|
|
|
|
|
|
|
3. Scroll down to the related list "Access control"
|
|
|
|
3. Scroll down to the related list “Access control”
|
|
|
|
|
|
|
|
4. Change active to "false" for all records
|
|
|
|
4. Change active to “false” for all records
|
|
|
|
|
|
|
|
## Record producer
|
|
|
|
|
|
|
|
The next step will be to create the form that the student can see and
|
|
|
|
use when they want to file a disciplinary case in the student portal.
|
|
|
|
Navigate to disciplinary proceedings under \"**Experience**\", which
|
|
|
|
takes us to Record Producer/ Post Producer.
|
|
|
|
The next step will be to create the form that the student can see and use when they want to file a disciplinary case in the student portal. Navigate to disciplinary proceedings under "**Experience**", which takes us to Record Producer/ Post Producer.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.5145833333333334in"}
|
|
|
|
{width="6.3in" height="2.5145833333333334in"}
|
|
|
|
|
|
|
|
Here are several steps to go through when creating a form. Follow the
|
|
|
|
side menu on the left side from the first step.
|
|
|
|
Here are several steps to go through when creating a form. Follow the side menu on the left side from the first step.
|
|
|
|
|
|
|
|
## Details
|
|
|
|
|
|
|
|
Give a name and description to the form. Note that this is what the
|
|
|
|
student will see when registering, so it is good to provide a detailed
|
|
|
|
description of what the form will be used for. Click \"**Save**\" after
|
|
|
|
the information is filled.
|
|
|
|
Give a name and description to the form. Note that this is what the student will see when registering, so it is good to provide a detailed description of what the form will be used for. Click "**Save**" after the information is filled.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.3715277777777777in"}
|
|
|
|
{width="6.3in" height="2.3715277777777777in"}
|
|
|
|
|
|
|
|
## Destination
|
|
|
|
|
|
|
|
This is where the destination must be filled in. That is, which table
|
|
|
|
this form should point to and update information in. This tends to be
|
|
|
|
auto-filled when the form is created directly in App Engine Studio, or
|
|
|
|
by using a template that automatically creates forms. If an
|
|
|
|
application/process is created without the use of a template, one must
|
|
|
|
also find the table this form should point to.
|
|
|
|
This is where the destination must be filled in. That is, which table this form should point to and update information in. This tends to be auto-filled when the form is created directly in App Engine Studio, or by using a template that automatically creates forms. If an application/process is created without the use of a template, one must also find the table this form should point to.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.0243055555555554in"}
|
|
|
|
{width="6.3in" height="2.0243055555555554in"}
|
|
|
|
|
|
|
|
## Location
|
|
|
|
|
|
|
|
On the next step, Location/Location, it should be defined where this
|
|
|
|
form should be located. Here you will have access to choose a directory
|
|
|
|
and which category it should be located under. This makes it available
|
|
|
|
in the end-user protal and determines where in the directory they should
|
|
|
|
be located. Click on \"**Browse\"** under Directories and select the
|
|
|
|
appropriate one. It\'s the same procedure for categories.
|
|
|
|
On the next step, Location/Location, it should be defined where this form should be located. Here you will have access to choose a directory and which category it should be located under. This makes it available in the end-user protal and determines where in the directory they should be located. Click on "**Browse"** under Directories and select the appropriate one. It's the same procedure for categories.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.5701388888888888in"}
|
|
|
|
{width="6.3in" height="2.5701388888888888in"}
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.5597222222222222in"}
|
|
|
|
{width="6.3in" height="2.5597222222222222in"}
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.5618055555555554in"}
|
|
|
|
{width="6.3in" height="2.5618055555555554in"}
|
|
|
|
|
|
|
|
## Questions
|
|
|
|
|
|
|
|
Furthermore, the questions are defined in the form. These are linked to
|
|
|
|
the fields we created in the table. To define a new question click on
|
|
|
|
\"**Insert new question**\" and select the type. We want to collect the
|
|
|
|
type of disciplinary violation in question, so we choose \"**New
|
|
|
|
Question**\".
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.5944444444444446in"}
|
|
|
|
|
|
|
|
When creating a question, the type must be selected, in the same way
|
|
|
|
that one defines a new field in a table. Here, type reflects the field,
|
|
|
|
we want to give the student more choices, and select the question type
|
|
|
|
\"**Choice**\". The values should be retrieved from the discipline
|
|
|
|
violation field in the table, and thus select the drop-down menu
|
|
|
|
\"**Fixed values\".**
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.4138888888888888in"}Check \"**Map to a specific field on the
|
|
|
|
table**\" and select the \"**Disciplinary violation**\" field created in
|
|
|
|
the **table**. The name is automatically set as the field is selected.
|
|
|
|
Furthermore, we must enter the actual question we want to ask the
|
|
|
|
student, this will be what the student sees in the form.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.3958333333333335in"}
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.3895833333333334in"}
|
|
|
|
|
|
|
|
Further on the next tab, Options/Choices, we define the same choices
|
|
|
|
that we entered at the field level in the table. Click \"**Insert
|
|
|
|
question**\" / \"**Save**\" and you will automatically be taken back to
|
|
|
|
the previous page.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.373611111111111in"}We also want a description of the
|
|
|
|
disciplinary violation, here the existing question that already points
|
|
|
|
to the description field can be used. To edit the question, click on the
|
|
|
|
icon in the center. The procedure is the same as the question we created
|
|
|
|
above.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.311111111111111in"}
|
|
|
|
Furthermore, the questions are defined in the form. These are linked to the fields we created in the table. To define a new question click on "**Insert new question**" and select the type. We want to collect the type of disciplinary violation in question, so we choose "**New Question**".
|
|
|
|
|
|
|
|
{width="6.3in" height="2.5944444444444446in"}
|
|
|
|
|
|
|
|
When creating a question, the type must be selected, in the same way that one defines a new field in a table. Here, type reflects the field, we want to give the student more choices, and select the question type "**Choice**". The values should be retrieved from the discipline violation field in the table, and thus select the drop-down menu "**Fixed values".**
|
|
|
|
|
|
|
|
{width="6.3in" height="2.4138888888888888in"}Check "**Map to a specific field on the table**" and select the "**Disciplinary violation**" field created in the **table**. The name is automatically set as the field is selected. Furthermore, we must enter the actual question we want to ask the student, this will be what the student sees in the form.
|
|
|
|
|
|
|
|
{width="6.3in" height="2.3958333333333335in"}
|
|
|
|
|
|
|
|
{width="6.3in" height="2.3895833333333334in"}
|
|
|
|
|
|
|
|
Further on the next tab, Options/Choices, we define the same choices that we entered at the field level in the table. Click "**Insert question**" / "**Save**" and you will automatically be taken back to the previous page.
|
|
|
|
|
|
|
|
{width="6.3in" height="2.373611111111111in"}We also want a description of the disciplinary violation, here the existing question that already points to the description field can be used. To edit the question, click on the icon in the center. The procedure is the same as the question we created above.
|
|
|
|
|
|
|
|
{width="6.3in" height="2.311111111111111in"}
|
|
|
|
|
|
|
|
## Settings
|
|
|
|
|
|
|
|
Under settings you can choose whether you want to give the student the
|
|
|
|
opportunity to add attachments or not, or hide buttons. Here it is
|
|
|
|
important to note that if you choose to hide the \"**Add to wishlist**\"
|
|
|
|
button, the archiving functionality in the portal for this form will
|
|
|
|
also disappear. We thus choose to leave everything as it does.
|
|
|
|
Under settings you can choose whether you want to give the student the opportunity to add attachments or not, or hide buttons. Here it is important to note that if you choose to hide the "**Add to wishlist**" button, the archiving functionality in the portal for this form will also disappear. We thus choose to leave everything as it does.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.323611111111111in"}
|
|
|
|
{width="6.3in" height="2.323611111111111in"}
|
|
|
|
|
|
|
|
## Access
|
|
|
|
|
|
|
|
Under accesses/access, you can define which group or role should have
|
|
|
|
access to the form. This automatically falls on the \"**SNC external**\"
|
|
|
|
group if nothing is added manually, which is a group to grant access to
|
|
|
|
external users.
|
|
|
|
Under accesses/access, you can define which group or role should have access to the form. This automatically falls on the "**SNC external**" group if nothing is added manually, which is a group to grant access to external users.
|
|
|
|
|
|
|
|
## Review and submit
|
|
|
|
|
|
|
|
At the last step, a summary is displayed and all choices, questions and
|
|
|
|
any locations you have chosen for the form to be. To make the form
|
|
|
|
available to users click \"**Submit**\". To see a form preview, click
|
|
|
|
\"**Preview**\".
|
|
|
|
At the last step, a summary is displayed and all choices, questions and any locations you have chosen for the form to be. To make the form available to users click "**Submit**". To see a form preview, click "**Preview**".
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.359027777777778in"}
|
|
|
|
{width="6.3in" height="2.359027777777778in"}
|
|
|
|
|
|
|
|
Form preview:
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.2631944444444443in"}
|
|
|
|
|
|
|
|
We now navigate back to App Home and start setting up a process
|
|
|
|
definition that will use the data we have created in the table. The
|
|
|
|
purpose of the process in the example in this guide is to retrieve and
|
|
|
|
update information about the student submitting a disciplinary violation
|
|
|
|
case. We use process definition to automate this, making it easier for a
|
|
|
|
case officer to handle the case with correct information. To start,
|
|
|
|
click on the \"**Logic and Automation**\" tab and click into the process
|
|
|
|
definition.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.3916666666666666in"}
|
|
|
|
|
|
|
|
Start by adding a swimlane to the process by clicking \"**+ Add a new
|
|
|
|
lane**\". A swimlane, \"**Lane**\", can be seen as a grouped sequence of
|
|
|
|
activities within a process. For more information such as the individual
|
|
|
|
components of Process Automation Designer (PAD) read the following
|
|
|
|
article:
|
|
|
|
<https://docs.servicenow.com/bundle/utah-build-workflows/page/administer/process-automation-designer/concept/process-automation-designer.html>
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.567361111111111in"}
|
|
|
|
|
|
|
|
Here we give a short title to the swimlane and a description that says
|
|
|
|
something about what this swimlane should do. Click \"**Save and
|
|
|
|
close**\" to save the information.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.6444444444444444in"}
|
|
|
|
|
|
|
|
We start by adding a first activity by clicking on \"**Add another**
|
|
|
|
**process activity**\" in the left tab. The first thing we want a
|
|
|
|
caseworker to see is an instruction. This instruction should contain a
|
|
|
|
concise checklist for the further activities we will add to the flow,
|
|
|
|
and which we would like a case officer to quality check before further
|
|
|
|
case processing is carried out.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.4763888888888888in"}
|
|
|
|
{width="6.3in" height="2.2631944444444443in"}
|
|
|
|
|
|
|
|
We now navigate back to App Home and start setting up a process definition that will use the data we have created in the table. The purpose of the process in the example in this guide is to retrieve and update information about the student submitting a disciplinary violation case. We use process definition to automate this, making it easier for a case officer to handle the case with correct information. To start, click on the "**Logic and Automation**" tab and click into the process definition.
|
|
|
|
|
|
|
|
{width="6.3in" height="2.3916666666666666in"}
|
|
|
|
|
|
|
|
Start by adding a swimlane to the process by clicking "**+ Add a new lane**". A swimlane, "**Lane**", can be seen as a grouped sequence of activities within a process. For more information such as the individual components of Process Automation Designer (PAD) read the following article: <https://docs.servicenow.com/bundle/utah-build-workflows/page/administer/process-automation-designer/concept/process-automation-designer.html>
|
|
|
|
|
|
|
|
{width="6.3in" height="2.567361111111111in"}
|
|
|
|
|
|
|
|
Here we give a short title to the swimlane and a description that says something about what this swimlane should do. Click "**Save and close**" to save the information.
|
|
|
|
|
|
|
|
{width="6.3in" height="2.6444444444444444in"}
|
|
|
|
|
|
|
|
We start by adding a first activity by clicking on "**Add another** **process activity**" in the left tab. The first thing we want a caseworker to see is an instruction. This instruction should contain a concise checklist for the further activities we will add to the flow, and which we would like a case officer to quality check before further case processing is carried out.
|
|
|
|
|
|
|
|
{width="6.3in" height="2.4763888888888888in"}
|
|
|
|
|
|
|
|
Navigate to **Common Activities**/**Common Activities Instruction.**à
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.8006944444444444in"}
|
|
|
|
|
|
|
|
Fill in an appropriate title and description. Click \"**Save and**
|
|
|
|
**close**\" to save the activity.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.5729166666666665in"}
|
|
|
|
|
|
|
|
Earlier in the user guide, we created metadata in the table. Here we
|
|
|
|
created a multiple choice field where one can choose the type of
|
|
|
|
disciplinary violation, and a field that should contain the student\'s
|
|
|
|
name. We can expect to receive data from the form the student submits
|
|
|
|
when they report a new violation. We have previously defined it as a
|
|
|
|
mandatory field the student must complete to submit the case. We also
|
|
|
|
want to know the student\'s name and automatically fill the data in that
|
|
|
|
field to simplify the processing of the case for a case officer. We can,
|
|
|
|
for example, obtain this information through an integration with a
|
|
|
|
professional system. For this user guide, we retrieve the student\'s
|
|
|
|
name via the system OrgReg.
|
|
|
|
{width="6.3in" height="2.8006944444444444in"}
|
|
|
|
|
|
|
|
Fill in an appropriate title and description. Click "**Save and** **close**" to save the activity.
|
|
|
|
|
|
|
|
{width="6.3in" height="2.5729166666666665in"}
|
|
|
|
|
|
|
|
Earlier in the user guide, we created metadata in the table. Here we created a multiple choice field where one can choose the type of disciplinary violation, and a field that should contain the student's name. We can expect to receive data from the form the student submits when they report a new violation. We have previously defined it as a mandatory field the student must complete to submit the case. We also want to know the student's name and automatically fill the data in that field to simplify the processing of the case for a case officer. We can, for example, obtain this information through an integration with a professional system. For this user guide, we retrieve the student's name via the system OrgReg.
|
|
|
|
|
|
|
|
To do this, we must create a custom activity that is linked to an already created integration. First, select a new activity by clicking on "**Add another** **process activity**". Then click on "**Create a new activity**".
|
|
|
|
|
|
|
|
{width="6.3in" height="2.4451388888888888in"}
|
|
|
|
|
|
|
|
Write an appropriate title that reflects what this activity will do. The table this should point to is where OrgReg is located.
|
|
|
|
|
|
|
|
{width="6.3in" height="2.884027777777778in"}
|
|
|
|
|
|
|
|
Further down in the same tab, we need to define which flow this information should be retrieved from. For more information about Flow Designer, see the following article: [Flow designer (Service now)](https://docs.servicenow.com/bundle/utah-build-workflows/page/administer/flow-designer/concept/flow-designer.html) Click on the magnifying glass and find the right action.
|
|
|
|
|
|
|
|
To do this, we must create a custom activity that is linked to an
|
|
|
|
already created integration. First, select a new activity by clicking on
|
|
|
|
\"**Add another** **process activity**\". Then click on \"**Create a new
|
|
|
|
activity**\".
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.4451388888888888in"}
|
|
|
|
|
|
|
|
Write an appropriate title that reflects what this activity will do. The
|
|
|
|
table this should point to is where OrgReg is located.
|
|
|
|
{width="6.3in" height="2.8618055555555557in"}
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.884027777777778in"}
|
|
|
|
{width="6.3in" height="2.847916666666667in"}
|
|
|
|
|
|
|
|
Further down in the same tab, we need to define which flow this
|
|
|
|
information should be retrieved from. For more information about Flow
|
|
|
|
Designer, see the following article: [Flow designer (Service
|
|
|
|
now)](https://docs.servicenow.com/bundle/utah-build-workflows/page/administer/flow-designer/concept/flow-designer.html)
|
|
|
|
Click on the magnifying glass and find the right action.
|
|
|
|
{width="5.292400481189851in" height="3.1840748031496062in"}
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.8618055555555557in"}
|
|
|
|
After saving the new activity by clicking "**Submit**", we need to find it again in the activities in the same way we arrived at the instruction: Click to "**Add an activity**", and we navigate to **Manage disciplinary case Retrieve user informationà**. You can also look up the activity.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.847916666666667in"}
|
|
|
|
{width="6.3in" height="1.336111111111111in"}
|
|
|
|
|
|
|
|
{width="5.292400481189851in"
|
|
|
|
height="3.1840748031496062in"}
|
|
|
|
Here we automatically get metadata from the integration that we can use to link and retrieve information. Here there is both the opportunity to use the right tab or see an expanded view by clicking "**View all properties**".
|
|
|
|
|
|
|
|
After saving the new activity by clicking \"**Submit**\", we need to
|
|
|
|
find it again in the activities in the same way we arrived at the
|
|
|
|
instruction: Click to \"**Add an activity**\", and we navigate to
|
|
|
|
**Manage disciplinary case Retrieve user informationà**. You can also
|
|
|
|
look up the activity.
|
|
|
|
{width="6.3in" height="2.6506944444444445in"}
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="1.336111111111111in"}
|
|
|
|
{width="6.3in" height="2.6284722222222223in"}
|
|
|
|
|
|
|
|
Here we automatically get metadata from the integration that we can use
|
|
|
|
to link and retrieve information. Here there is both the opportunity to
|
|
|
|
use the right tab or see an expanded view by clicking \"**View all
|
|
|
|
properties**\".
|
|
|
|
We want to link the field from the integration to retrieve information about enrollees. Here we want the name of the enrollee / student and find the field that contains that information.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.6506944444444445in"}
|
|
|
|
{width="6.3in" height="2.6430555555555557in"}
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.6284722222222223in"}
|
|
|
|
{width="6.3in" height="2.64375in"}
|
|
|
|
|
|
|
|
We want to link the field from the integration to retrieve information
|
|
|
|
about enrollees. Here we want the name of the enrollee / student and
|
|
|
|
find the field that contains that information.
|
|
|
|
After saving information from the previous step, we will now add a new activity that updates the field we have created (Student name) in our table with data we retrieve from the integration. Select the activity "**Automated update record**".
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.6430555555555557in"}
|
|
|
|
{width="6.3in" height="2.6645833333333333in"}
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.64375in"}
|
|
|
|
Navigate to the **"Automation**" tab and link the "**Record**" field in the right tab to retrieve new cases that are created. You can easily do this with the help of a Data pill.
|
|
|
|
|
|
|
|
After saving information from the previous step, we will now add a new
|
|
|
|
activity that updates the field we have created (Student name) in our
|
|
|
|
table with data we retrieve from the integration. Select the activity
|
|
|
|
\"**Automated update record**\".
|
|
|
|
{width="6.3in" height="2.6534722222222222in"}
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.6645833333333333in"}
|
|
|
|
The table field on the right tab we must associate with the table where all cases are located. Here we select the table we created "**Disciplinary Proceedings**".
|
|
|
|
|
|
|
|
Navigate to the **\"Automation**\" tab and link the \"**Record**\" field
|
|
|
|
in the right tab to retrieve new cases that are created. You can easily
|
|
|
|
do this with the help of a Data pill.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.6534722222222222in"}
|
|
|
|
{width="6.3in" height="2.6381944444444443in"}
|
|
|
|
|
|
|
|
The table field on the right tab we must associate with the table where
|
|
|
|
all cases are located. Here we select the table we created
|
|
|
|
\"**Disciplinary Proceedings**\".
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.6381944444444443in"}
|
|
|
|
|
|
|
|
We then associate the field we want to update in the table. Here we must
|
|
|
|
also link the \"**Value**\" field to the activity we created in previous
|
|
|
|
steps, which retrieves user information from the integration.
|
|
|
|
We then associate the field we want to update in the table. Here we must also link the "**Value**" field to the activity we created in previous steps, which retrieves user information from the integration.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.6791666666666667in"}
|
|
|
|
{width="6.3in" height="2.6791666666666667in"}
|
|
|
|
|
|
|
|
{width="5.732292213473316in"
|
|
|
|
height="2.3865594925634297in"}
|
|
|
|
{width="5.732292213473316in" height="2.3865594925634297in"}
|
|
|
|
|
|
|
|
This is what it will look like when all fields are associated with the
|
|
|
|
correct data source.
|
|
|
|
This is what it will look like when all fields are associated with the correct data source.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.64375in"}
|
|
|
|
{width="6.3in" height="2.64375in"}
|
|
|
|
|
|
|
|
We then add a final activity that only notifies the case officer that
|
|
|
|
they can continue further processing of the case once the first steps
|
|
|
|
have been completed.
|
|
|
|
We then add a final activity that only notifies the case officer that they can continue further processing of the case once the first steps have been completed.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.625in"}
|
|
|
|
{width="6.3in" height="2.625in"}
|
|
|
|
|
|
|
|
Now the process is ready, to use it one must activate the process by
|
|
|
|
clicking on «**Activate**». You also have the opportunity to test the
|
|
|
|
flow before activating.
|
|
|
|
Now the process is ready, to use it one must activate the process by clicking on «**Activate**». You also have the opportunity to test the flow before activating.
|
|
|
|
|
|
|
|
## Caseworker form:
|
|
|
|
|
|
|
|
Back in the table view, we can find forms pointing to the workbench of
|
|
|
|
caseworkers. This form is what the case officer sees when they open a
|
|
|
|
case associated with the process \"**Handling disciplinary
|
|
|
|
violations**\". Navigate to the second tab \"**Forms**\".
|
|
|
|
Back in the table view, we can find forms pointing to the workbench of caseworkers. This form is what the case officer sees when they open a case associated with the process "**Handling disciplinary violations**". Navigate to the second tab "**Forms**".
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.7527777777777778in"}
|
|
|
|
{width="6.3in" height="2.7527777777777778in"}
|
|
|
|
|
|
|
|
It is possible to remove fields you do not want to see in the form and
|
|
|
|
add other fields. To find a field, you can also use the search engine on
|
|
|
|
the left tab. Here we have identified a field we created in the table
|
|
|
|
\"**Disciplinary violations**\". To add to the form click on the field
|
|
|
|
and drag it into the location desired.
|
|
|
|
It is possible to remove fields you do not want to see in the form and add other fields. To find a field, you can also use the search engine on the left tab. Here we have identified a field we created in the table "**Disciplinary violations**". To add to the form click on the field and drag it into the location desired.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.6458333333333335in"}
|
|
|
|
{width="6.3in" height="2.6458333333333335in"}
|
|
|
|
|
|
|
|
You also have the opportunity to create new sections in the form. We\'re
|
|
|
|
creating a new section for the record and adding the two fields we\'ve
|
|
|
|
worked on the most in this process: Disciplinary Violations and Student
|
|
|
|
Names. After configuring the form as desired, click \"**Save**\".
|
|
|
|
You also have the opportunity to create new sections in the form. We're creating a new section for the record and adding the two fields we've worked on the most in this process: Disciplinary Violations and Student Names. After configuring the form as desired, click "**Save**".
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.651388888888889in"}
|
|
|
|
{width="6.3in" height="2.651388888888889in"}
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.626388888888889in"}
|
|
|
|
{width="6.3in" height="2.626388888888889in"}
|
|
|
|
|
|
|
|
Now the new process is ready for use. The form is ready in the portal,
|
|
|
|
and a case officer now gets this process up every time a case of
|
|
|
|
disciplinary violation is reported.
|
|
|
|
Now the new process is ready for use. The form is ready in the portal, and a case officer now gets this process up every time a case of disciplinary violation is reported.
|
|
|
|
|
|
|
|
## Report a case
|
|
|
|
|
|
|
|
Now that we have set up our own process, it is ready to be used. To test
|
|
|
|
this, we can log in with a student account and file a disciplinary
|
|
|
|
violation case. We will then open the case as a case officer and check
|
|
|
|
whether all the information needed to start the case processing is
|
|
|
|
available. We start by opening the student portal and find the form by
|
|
|
|
clicking on \"**Services**\".
|
|
|
|
Now that we have set up our own process, it is ready to be used. To test this, we can log in with a student account and file a disciplinary violation case. We will then open the case as a case officer and check whether all the information needed to start the case processing is available. We start by opening the student portal and find the form by clicking on "**Services**".
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.8430555555555554in"}
|
|
|
|
{width="6.3in" height="2.8430555555555554in"}
|
|
|
|
|
|
|
|
Here, the student will have a variety of forms available. A student
|
|
|
|
should also be able to see categories on the left side that act as a
|
|
|
|
filtering of these. We select the form \"**Disciplinary case**\".
|
|
|
|
Here, the student will have a variety of forms available. A student should also be able to see categories on the left side that act as a filtering of these. We select the form "**Disciplinary case**".
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.4097222222222223in"}
|
|
|
|
{width="6.3in" height="2.4097222222222223in"}
|
|
|
|
|
|
|
|
Fill in information about the violation and click \"**Submit**\". A new
|
|
|
|
disciplinary case is now being established.
|
|
|
|
Fill in information about the violation and click "**Submit**". A new disciplinary case is now being established.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.8180555555555555in"}
|
|
|
|
{width="6.3in" height="2.8180555555555555in"}
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.654861111111111in"}
|
|
|
|
{width="6.3in" height="2.654861111111111in"}
|
|
|
|
|
|
|
|
## Case officer receives a new disciplinary case
|
|
|
|
|
|
|
|
In the case management platform, we have opened the new case that has
|
|
|
|
come in from the student. The first thing a caseworker navigates is
|
|
|
|
Guidance with a variety of activities. These are the same activities we
|
|
|
|
defined in the process designer. As a case officer, the steps are
|
|
|
|
followed downwards. The case officer first gets a checklist.
|
|
|
|
In the case management platform, we have opened the new case that has come in from the student. The first thing a caseworker navigates is Guidance with a variety of activities. These are the same activities we defined in the process designer. As a case officer, the steps are followed downwards. The case officer first gets a checklist.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.834722222222222in"}
|
|
|
|
{width="6.3in" height="2.834722222222222in"}
|
|
|
|
|
|
|
|
As a case officer, the checklist is followed, and the task is to check
|
|
|
|
whether the Disciplinary violations and student names fields contain
|
|
|
|
data. This will then be important information for a case officer to have
|
|
|
|
before they can continue the case processing.
|
|
|
|
As a case officer, the checklist is followed, and the task is to check whether the Disciplinary violations and student names fields contain data. This will then be important information for a case officer to have before they can continue the case processing.
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.81875in"}
|
|
|
|
{width="6.3in" height="2.81875in"}
|
|
|
|
|
|
|
|
After verification, the case officer can check off for the task, which
|
|
|
|
indicates that it has been completed. This is done by clicking \"**Mark
|
|
|
|
Complete**\".
|
|
|
|
After verification, the case officer can check off for the task, which indicates that it has been completed. This is done by clicking "**Mark Complete**".
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.834722222222222in"}
|
|
|
|
{width="6.3in" height="2.834722222222222in"}
|
|
|
|
|
|
|
|
{width="6.3in"
|
|
|
|
height="2.8361111111111112in"}
|
|
|
|
{width="6.3in" height="2.8361111111111112in"}
|
|
|
|
|
|
|
|
## Other relevant ServiceNow user documentation
|
|
|
|
|
|
|
|
The following links can be used to learn more. Note that some of the
|
|
|
|
information may be out of date and may be available in a different
|
|
|
|
version when updating to newer versions of Service Now.
|
|
|
|
The following links can be used to learn more. Note that some of the information may be out of date and may be available in a different version when updating to newer versions of Service Now.
|
|
|
|
|
|
|
|
Robotic Process Automation:
|
|
|
|
<https://www.servicenow.com/products/robotic-process-automation.html>
|
|
|
|
Robotic Process Automation: <https://www.servicenow.com/products/robotic-process-automation.html>
|
|
|
|
|
|
|
|
Artificial Intelligence:
|
|
|
|
<https://www.servicenow.com/now-platform/now-intelligence.html>
|
|
|
|
Artificial Intelligence: <https://www.servicenow.com/now-platform/now-intelligence.html>
|
|
|
|
|
|
|
|
API / Spokes:
|
|
|
|
<https://docs.servicenow.com/bundle/tokyo-application-development/page/administer/flow-designer/concept/spokes.html>
|
|
|
|
API / Spokes: <https://docs.servicenow.com/bundle/tokyo-application-development/page/administer/flow-designer/concept/spokes.html>
|
|
|
|
|
|
|
|
Description of available field types that can be added to forms:
|
|
|
|
<https://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/field-administration/task/t_CreatingNewFields.html>
|
|
|
|
Description of available field types that can be added to forms: <https://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/field-administration/task/t_CreatingNewFields.html>
|
|
|
|
|
|
|
|
Date/timefields:
|
|
|
|
<https://docs.servicenow.com/bundle/utah-platform-administration/page/administer/time/reference/r_UseDateAndTimeFields.html> |
|
|
|
Date/timefields: <https://docs.servicenow.com/bundle/utah-platform-administration/page/administer/time/reference/r_UseDateAndTimeFields.html> |
