Create the Request Form
Purpose
ServiceNow offers multiple ways to create a user experience for submitting a form. In this exercise, we will learn one quick way to get users off paper forms and emails.
-
Go to App Home tab, "App home Telework"
-
On the application homepage, locate the Experience section and click the ⨁ Add icon
This takes us to a selection where we can identify the type of experience we wish to create.
-
Select the Record Producer option.
infoA record producer is a specific type of catalog item that allows end users to create task-based records from the service catalog.
-
This launches the record producer creator.
-
Click on the
button -
Set the following values (💡 double-click, copy & paste into the form)
Field Name Field Value (1) Name Apply for Telework (2) Short Description Use this form to apply for Telework (3) Click on the
button -
Click on the
button -
Click on Destination , then type Tel, and select the Telework Case table
-
Click on Location , then under Catalogs, click on Browse.
-
Click on Service Catalog , then click on the right arrow to move the item over to the Selected list
-
At the bottom, Click on the
button -
Under Categories , click on Browse
-
Move Can We Help You? to the right-hand side and Click on the
buttonYour screen should look like below
-
Let's add questions to the form
infoUnlike in a paper-based form, we don't need to ask users to fill personal information like first name, last name, …, or date of request. That information will be automatically attached to the case. This makes filling forms so much faster.
-
We want to allow users to open a case on behalf of another individual, so let's start by asking users " Who is this request for?" and " When do you need this?"
-
Click on Questions
-
Click the arrow next to Insert new questionthen click "Question set"
-
Select "Standard Employee Questions" and click Submit
This will add two frequently asked questions on forms
-
One key information we need users to provide is the type of arrangement they are applying for.
- Click Insert new question
- For Question type, select Choice
- For Question subtype , select Record reference
-
Scroll down to the Details section
-
In the Details section, enter the following information: (💡 double-click, copy & paste into the form)
Field Name Field Value Map to a specific field We want to store that information so let's check the box Table field choose Arrangement Question label What type of Telework arrangement are you applying for? Mandatory Checked infoNotice the Question Preview that shows what the question will look like to the user.
-
Click on Continue to Additional details →
-
In the Additional details section, set the Source Table to the Arrangement table we imported earlier. as options for this question.
-
then Click on the Annotation tab
-
Today, the team is spending a lot of time correcting and manually re-routing applications due to people confusing the different types of Telework arrangement. Let's fix that.
-
We'll use the Annotation tab to provide users with additional instructions for the question.
-
Check the box Show** instructions**
-
Open the file: telework form annotation.docx
-
Copy all the text in the file ( ⌘ Cmd or CTRL+A, CTRL+C )
-
Paste it into the Annotation section of the Telework Form (⌘ Cmd or CTRL+V )
-
Click on the
button
-
Back to the main form, Click on the
button -
When users select the arrangement type Situational , we'll prompt them for the number of days per week.
-
So, let's go ahead and in the Type section set the following values:
Field Name Field Value Question type Text Question subtype Single line -
Scroll down to the Details section
-
In the Details section, enter the following information: (💡 double-click, copy & paste into the form)
Field Name Field Value Map to a specific field Checked Table field Days per week Question label Number of Days per Week? -
Click on Additional details
-
In the Additional details section, for the Text validation field, select Number
-
Click on Insert Question
-
-
Back to the Questions page, we're going to define the dynamic behavior of this question based on the answer to the previous question.
- Click on the behavior icon
- Click on the Define new behavior icon
-
In the Actions tab, we'll specify the behavior we need:
Field Name Field Value ① Make the question mandatory Yes ② Make the question visible Yes ③ Click on the Conditions tab
-
In the Conditions tab,
-
Set the filter to [arrangement] [is] [Situational Telework]
-
Click on the
button
-
-
Back to the questions page,
-
Click on the
button -
Click on Preview
-
-
The Preview page allows to visualize what our form will look like in different experiences. (You can interact with the item but not submit it).
Mobile Portal -
Close the Preview by clicking on the X on the top right
infoIf you want to preview your catalog item in the Virtual Agent you will need to activate the plugins_ _ Glide Virtual Agent and Service Management Virtual Agent Topic Blocks. Additional setup beyond that is required to get NLU to perform a topic conversation via the Virtual Agent. Feel free to experiment this after completing the entire lab.
-
Let's publish the form to the Service Portal
- Click on Review and Submit
- Click on Submit
-
Congratulations. The form is published on your development instance.
-
Let's see how users can easily find it on the Service Portal
-
Go to the tab with ServiceNow Admin Home page
-
and then open the Service Portal
- Click All
- Type Portal
- Click on Service Portal
-
In the portal, search for "Telework"
-
The catalog item is found.
-
Click on the item to apply for Telework
-
In the Details section, enter the following information: (💡 double-click, copy & paste into the form)
Field Name Field Value (1) Who is this request for? David Loo (2) When do you need this? This week (3) What type of arrangement? Situational (4) Number of days per week? 3 - Click on the button
Exercise Recap
In this exercise, we learned how to use App Engine Studio (AES) to easily create customized Catalog Items that users can access in Service Portal and on mobile devices.
Our next exercise will focus on taking the building blocks created to this point and making them actionable to drive automation and process optimization