logo

NJP

Master ServiceNow List Editing in Minutes! ServiceNow Step-by-Step Configuration Guide

Import · Oct 03, 2023 · video

Foreign [Music] Because I see a lot of people are not 
familiar with this particular use result,   we will see what all things we can 
do in terms of list editing. So,   without wasting any further time, 
let's jump onto the instance. So,   what exactly is list editing? First of 
all, understand. For instance, if I go to: Incident table You can see the list of records over 
the module. And if you double-click   on any of these entities, for 
example, "short description",   you have the capability to edit it. And 
to change it, for example, if I make it   "admin" and if I click save, it will get updated 
over the record. The same thing you can do over   any field which you get. Not all the fields, okay, 
but you will be seeing in some time. So you can do   the same. You can see the record got updated with 
"admin". The same way you can do for priority,   refresh field, and so on. So today, we'll 
be diving deep into this list editing part,   how we can control this on the platform. 
If you want to make the settings global,   if you want to disable the settings or make 
certain fields non-editable across the platform,   you can do it. What you have to 
do is just go to system property. And over here, you can see the UI properties. Just 
click on that. And over here, you have to search   because there are tons of properties. Search for 
the setting, and you will see two properties. The   first property is "enable list". What exactly 
does it mean? By default, it's selected to   "yes". That's the reason we are able to do the 
list editing. If it's not selected to "yes",   then we will not have the capability across the 
platform to edit anything on the list. If you   want to see the demo, let's do this. I've just 
deselected it, and I will scroll down to save. So the property got saved. 
Now if we go to "incident",   what we were able to edit now ideally will not 
be editable for us. So if I click over here now,   I'm just clicking over the list, but nothing is 
happening. Why? Because it's not editable for   me. I have clicked on this thing, this thing, 
and so on. This is the first property. Now,   coming back to the properties itself, if you 
want to make it, I will just make it "yes".   The next property is "list of element type, 
comma-separated, cannot be edited in the list   editor". Here you can add if your project has 
any requirement that this type of field should   not be editable on the list view. You can add 
it over here, maybe a reference, document ID,   or even a string field. You can restrict it 
from here. Out of the box, there are a few   fields which are already restricted for 
the list view, like HTML, document ID,   template, and so on. You can manipulate these 
things from the list editor. You can try it on   your own. I've just enabled this list. And make 
sure whenever you enable this particular property   or whenever you are playing around with this 
property, as it's under system properties, it will   be applicable for the entire system. It will not 
be on a single table. Be very cautious whenever   you are making any decision to play around with 
this. Another question which might be buzzing in   your mind is, for instance, if I want to disable 
certain list editing only on one table, how   can I do that? We will be exploring that option. 
For instance, let's go to the incident table. And now we want to disable the listing, not for 
the entire system but just for this particular   table. How can you do that? We have this control 
defined on the table. To navigate to that,   right-click on the list, go to "configure", and 
there is a "list control". Go to the list control. It's just loading. We'll give it some time. 
Alright, let's continue. The place where you   can play around with it is here. You can make some 
configurations which will be applicable to your   list for that particular table. You can see there 
is a table entity out there, "table incident".   Whatever you do here will be applicable only for 
the incident table and will not apply to any other   table. Over here, "list editing type", you can see 
"save immediately". So whenever you double-click,   pour some values out there, as soon as you click 
on this check mark, it will immediately get saved.   We have seen this earlier. We have another option, 
"save data by row". What happens is that if you   are editing multiple columns, it will save as 
one entity. It won't have multiple updates. But   down there, there is an option called "disable 
list editing". If we click that option,   it will disable the listing for this 
table only, no other table. Let's do that. I have saved it. Now if we go to   "incident.list" and now if I click, 
see, nothing is happening again. That's the power of this editing. Now if I go to 
this kind of login and let me just disable it.   I will just go here and "save immediately" 
on the "save rate mode". I just saved it. You can also define the rules which are 
mandatory to do the list edit over here.   Here you can see the "edit rules". If I go back 
to the incident, not over here, to the incidents,   and if I double-click now, I should be able 
to save the record, to update the record. So I went over here. If I click now, you can see 
this particular thing. We are able to edit it now.   This is one way. Now if you want to   try another option where we can define certain 
access controls, yes, definitely you can define   this other list editing. I will show you. 
First of all, I have to elevate my role   because "security admin" is necessary whenever 
you are playing around with access controls. Just update it. This has just refreshed my session, 
so I have those privileges now. Now if you want to define access controls, 
you can configure security rules. And you can click simply. Now what I want, for instance, type is "record". And we will go with the list editor. Let's edit   on which particular table we want to 
define it. I will just go to "incident". And just type it out. It's taking some 
time. "Incident", and I'll go with this. So "form" is, it's applicable for all. And 
I want to define a certain role for it.   I want it to be editable only for "admin". Okay, so if I save this,   it creates some security settings at the backend. 
And what it will do is that now, in order to   play around with the list, list edit, we need 
to have that role with us on the incident table.   Let's verify it. So if I go to "incident.list",   watching it gets saved. Continue. Okay, now if I go again to "incidents" and if I 
try to edit it, I'm able to edit. Why? Because I   have that role. Let's try to impersonate with some 
other person. So I will just go to "impersonate"   and let's select "Eve". "Tutor" set user. Okay, I don't want this experience. And   now if I go to "incident.list", it has only one 
list. And now if I try, I'm trying to edit it out,   but it's grayed out for me. You can see "security 
prevents writing into this particular field". So   because we don't have the admin access for "Eve's" 
account, this particular error message is coming   out. Let's end the impersonation. This is how you 
can add the roles or restrict the list editing for   a particular role on a particular table. And 
now we will jump back to the access controls. I have to elevate the role I need. Update. Now if you want to make this setting 
only for certain fields, how can you do that?   For example, if you don't want anyone, apart from 
admin, to make changes on the "caller" field,   you can select the "caller" out there. And then, 
in order to update the "caller" in the list view,   you need to have that role. And you can try 
it yourself and check it out. It will work.   So these are the different methods for list 
editing control. This is how we have seen how   we can make list editing disabled over the entire 
system, or we can make certain fields list editing   disabled from the system properties, under system 
property, the UI properties. Then if you want to   disable certain things on an individual 
table, we have list controls. And if you   want to go more granular, to the rules, and to 
certain fields, then we can do it through access   controls. This is all for today's tutorial. 
I hope you liked it. Please let me know if   you need more information on it. And please 
subscribe to my channel so that you will get   notified of my upcoming videos. Till then, stay 
safe, stay happy, and have a nice day. Thank you.

View original source

https://www.youtube.com/watch?v=qktI3jDDM8s