- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2023 10:07 AM
Hi Folks,
I'm new to ServiceNow and have completed the theoretical course (Full admin course from SAASWITHSERVICENOW) which is a good course available on Youtube now I want to practice some tasks on Instance. Could anyone please share the screenshot of Lab tasks so I can practice on my instance? I'm yet to buy a voucher for my CSA exam. If anyone has already bought a voucher for a first-time exam or their delta exam, it would be appreciated if you could share the screenshot of lab tasks in reply.
Your assistance will be greatly appreciated.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2023 09:23 PM
@Ali Asghar Here are some tasks which you can try to practice on your PDI.
ServiceNow Tasks After System Administrator Training | ||
Task# | Task Name | Task Description |
1 | User | Configuration - Set Up Users with the appropriate roles Create an Admin user account for yourself using the following convention: 'admin.<first name>' Create a Fulfiller user account for yourself using the following convention: 'itil.<first name>' Create an ESS user account for yourself using the following convention: 'ess.<first name>' Set the user 'admin' as Inactive |
2 | My Banner | Set the instance banner and list caption background color to be: #552233 Set the banner text to be: SPLI - Instance |
3 | Configure User Group | Create a new group called: "Follow the Sun" Add itil role to the created group Create 3 test users and add them as group members so they will inherit the group roles Note: name your users: test.User1, test.User2, test.User3 |
4 | Core Data - Locations | The Customer Locations are all the ones that have San Diego as City. All the other location records need to be removed. Note: To keep the Location hierarchy, do not remove the locations: California, North America, Americas |
5 | Configure State choice list | Deactivate/Remove 'Awaiting Problem' option from 'State' field for incidents |
6 | Identify caller | The Caller on the Incident needs to be searchable by First Name, Last Name, Email and Username |
7 | Remove Subcategory from Form | Remove the Subcategory field from the Incident Form (Default view) |
8 | Remove Request as an Incident Option | Deactivate/Remove 'Request' option from Category field for incidents |
9 | Client Scripts | Every time the Configuration Item changes on the Incident, the value of the Assignment group field should be set to the value of the Support group from the selected Configuration Item |
10 | Configure Incident Lists | Add the fields Updated and Updated by to the default view incident list Add the Updated and Updated by fields to My Work and My Groups Work default lists |
11 | Parent Incident | Add the existing field 'Parent Incident' to the incident form (Default view) under the Related Records section Add the Related List 'Incident -> Parent Incident' to the Incident form (Default view) |
12 | Notification Inactive | Make the following notifications INACTIVE: Incident Survey CI Affected Location Affected Cost Center Affected |
13 | SLAs | Modify the existing Incident SLAs to follow the criteria: P1 - 4 Hours P2 - 3 Day P3 - 5 Day |
14 | Major Incident field | Add new field 'Major incident' check box (Display - Major Incident, Field name u_major_incident) to the incident table |
15 | Configure the Problem Form | When removing a Form field, consider any referencing UI Policies or Client Scripts. |
16 | Attachments Related List | Add Attachments Related List to Problem Form (Default View) |
17 | Amend type options | Relabel the Change Type options as followed: Standard -> Common Normal -> Routine Emergency -> Emergency |
18 | Remove Category from the Change Form | Remove the Category field from the Change Request form (Default view) |
19 | Make fields mandatory | Disable the UI Policy Hide Fields - Approval. When Approval state is to 'Requested', the fields Configuration item and Short Description must become mandatory Note: A UI policy is required here. |
20 | Make requested by always Mandatory | The field Requested by must always be Mandatory |
21 | Hide the Impacted Services related list | Remove the Impacted Services Related list from the Change Request form (Default view) |
22 | Assignment Group auto populate from CI | Every time the Configuration Item changes on the Change Request, the value of the Assignment group field should be set to the value of the Support group from the selected Configuration Item |
23 | Remove Demo Data | Delete demo data for the processes to be implemented Incident table must be empty Problem table (and child tasks) must be empty Change request (and child tasks) table must be empty Note: Do not delete all the Tasks! |
Hope this helps.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2023 09:23 PM
@Ali Asghar Here are some tasks which you can try to practice on your PDI.
ServiceNow Tasks After System Administrator Training | ||
Task# | Task Name | Task Description |
1 | User | Configuration - Set Up Users with the appropriate roles Create an Admin user account for yourself using the following convention: 'admin.<first name>' Create a Fulfiller user account for yourself using the following convention: 'itil.<first name>' Create an ESS user account for yourself using the following convention: 'ess.<first name>' Set the user 'admin' as Inactive |
2 | My Banner | Set the instance banner and list caption background color to be: #552233 Set the banner text to be: SPLI - Instance |
3 | Configure User Group | Create a new group called: "Follow the Sun" Add itil role to the created group Create 3 test users and add them as group members so they will inherit the group roles Note: name your users: test.User1, test.User2, test.User3 |
4 | Core Data - Locations | The Customer Locations are all the ones that have San Diego as City. All the other location records need to be removed. Note: To keep the Location hierarchy, do not remove the locations: California, North America, Americas |
5 | Configure State choice list | Deactivate/Remove 'Awaiting Problem' option from 'State' field for incidents |
6 | Identify caller | The Caller on the Incident needs to be searchable by First Name, Last Name, Email and Username |
7 | Remove Subcategory from Form | Remove the Subcategory field from the Incident Form (Default view) |
8 | Remove Request as an Incident Option | Deactivate/Remove 'Request' option from Category field for incidents |
9 | Client Scripts | Every time the Configuration Item changes on the Incident, the value of the Assignment group field should be set to the value of the Support group from the selected Configuration Item |
10 | Configure Incident Lists | Add the fields Updated and Updated by to the default view incident list Add the Updated and Updated by fields to My Work and My Groups Work default lists |
11 | Parent Incident | Add the existing field 'Parent Incident' to the incident form (Default view) under the Related Records section Add the Related List 'Incident -> Parent Incident' to the Incident form (Default view) |
12 | Notification Inactive | Make the following notifications INACTIVE: Incident Survey CI Affected Location Affected Cost Center Affected |
13 | SLAs | Modify the existing Incident SLAs to follow the criteria: P1 - 4 Hours P2 - 3 Day P3 - 5 Day |
14 | Major Incident field | Add new field 'Major incident' check box (Display - Major Incident, Field name u_major_incident) to the incident table |
15 | Configure the Problem Form | When removing a Form field, consider any referencing UI Policies or Client Scripts. |
16 | Attachments Related List | Add Attachments Related List to Problem Form (Default View) |
17 | Amend type options | Relabel the Change Type options as followed: Standard -> Common Normal -> Routine Emergency -> Emergency |
18 | Remove Category from the Change Form | Remove the Category field from the Change Request form (Default view) |
19 | Make fields mandatory | Disable the UI Policy Hide Fields - Approval. When Approval state is to 'Requested', the fields Configuration item and Short Description must become mandatory Note: A UI policy is required here. |
20 | Make requested by always Mandatory | The field Requested by must always be Mandatory |
21 | Hide the Impacted Services related list | Remove the Impacted Services Related list from the Change Request form (Default view) |
22 | Assignment Group auto populate from CI | Every time the Configuration Item changes on the Change Request, the value of the Assignment group field should be set to the value of the Support group from the selected Configuration Item |
23 | Remove Demo Data | Delete demo data for the processes to be implemented Incident table must be empty Problem table (and child tasks) must be empty Change request (and child tasks) table must be empty Note: Do not delete all the Tasks! |
Hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2023 12:40 PM
Hi Sandeep,
Did these tasks come from a SN official resource? Wondering if there are guidelines that go along with the tasks.
Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-21-2023 06:20 AM
@Randy_ No these tasks are not from the official source. Also, there are no associated guidelines, I have attempted these tasks during my ServiceNow Administrator training and they are easily doable on a PDI instance.