[Music] please subscribe to my channel and click on the bell icon to get the regular updates of my channel and do not forget to like comment and share hello everyone welcome back to sas with servicenow this is part of itsm implementation mock training out of the box servicenow does not give lot of mandatory feels however mandatory fields are very much needed to perform better analysis of data and reporting in this video we will configure mandatory fields on incident form and we will start with making fields mandatory in all the condition on incident form and those fields are caller category subcategory configuration item assignment group shot description and if you want you can also make mandatory some other fields as well like maybe description the next task would be making fields mandatory only on only when state of incident is not new or cancelled and that field is assigned to so assigned to should be mandatory if state is not new or cancelled that means in other states assigned to should always be mandatory that's the requirement you have so it is just a mock we want to show you that how exactly you can make fields mandatory on the basis of some conditions or even you can say uh sometime you need to make the fields mandatory forever that means in all the conditions so we will cover both type of conditions one is for all the conditions and one is for a specific state or on the base of some other fields so let's go to the instance and configure these fields and make them mandatory you can make the fields mandatory in service now via various ways you can do it with the help of field dictionary you can make the fields mandatory with the help of ui policy you can make the fields mandatory with the help of client script now in this case we will use field dictionary but in case of field dictionary it's really important to know one thing that if you have a field which is inherited from base stable that means because incident is inherited from task which is the base table of service now so if that field is available and basically it is inherited from that base table and you are going to make the dictionary changes for that field in that case it will impact all other tables which are inherited from task table so for that service now gives you really great option and that's a great feature we have in service now and that's called dictionary override which will basically help you to just make same field mandatory on that particular table where you actually want to make field mandatory and it will not impact any other tables even that field is inherited from base table and if you make the changes with the help of dictionary override you will not impact other tables like change problem and that change that particular change will only visible to on on basically incident form not any other form now how exactly we do that so let's make it so we have to make these fields mandatory like caller category subcategory configuration item assignment group and short description and even the description now caller does not come from task so we will also see that if what fields are coming directly from task and what fields are directly on incident so we will start with caller caller is already mandatory so let's see first whether it is being dragged from task table or not so i will just click on configure dictionary so in order to change the dictionary of a field you have to click select with right click on the field name and then you will go to the configure dictionary and you will see the dictionary of that particular field so here we have so you can see it is directly created in the incident table so we can just go back and it is already mandatory so next field we have is category because we have to make category and subcategory as mandatory so let's see do we need to make changes in dictionary override or we just we can just make these changes directly um in the field dictionary so if i right click here and if i click on configure dictionary let's see so idly because category and sub category they are being they are not dragged from task table they are basically created directly in incident table so you can see we have incident table here so how you will make it mandatory so we will just maybe i will just directly select this check box so if you have to make a field mandatory a dictionary level so you can just select this check box as i said there are other ways as well but if you want to keep it basically same for all type of records then you can directly do it from dictionary and you can make it mandatory and it is it will also not impact any other table because it is this field is directly on incident so what i can do i can just quickly save this in this case category will become mandatory so if i go here again so now you can see category has become mandatory i will go to subcategory now this is also directly created on incident table so in that case you can just check this box again so if i check this box and i click on save so this will make this field mandatory as well at dictionary level so if i click on create new so you can see i think sub category is not let me check there could be some reason i don't know what exactly i okay maybe it did not get saved so i can just click here and i can just save it so you now if i click on this create new you will see that sub category will also be mandatory and yes this is also mandatory next is configuration item now here we will see dictionary override because configuration item field is inherited from task table which is the base table so if i click on this you can see it is showing task here if i will check this check box mandatory it will make this field mandatory in all the extended tables including change problem everywhere whatever tails tables are being extended from task table they will have configuration item field as mandatory but we do not want that because we just want to make sure this change is only applicable to incident table that's it not any other table so for that we will use dictionary override and for that i will go little bit bottom here we already have one one racket created for incident table for dictionary override so i will just open the same record so i will i will open this one so it's open and now here we have override mandatory i will check this checkbox i will make it mandatory i have to check this checkbox again and then i can just click on save it's saved so now if i click on create new you will see that that this become has become mandatory but how will you make sure that this is not impacting any other table so for that what you can do you can go to problem and we will see if this field is mandatory or not on problem so not really you can see here so configuration item is not mandatory on problem it is just mandatory on incident form that means that validates our change so whatever change we did validation is done because it is only mandatory on incident form not any other form so validation is done so next field is assignment group so i will go to assignment group now story with assignment group is also same so configure if i click on configure dictionary you will see that assignment group will be available on task table and i will not check this check box what i will do i will go to incident again i will open this record and i will make it mandatory from here and i will click on save and then i will click on create new you will see yes it is also mandatory and if you want to make description description is also inherited from tasks but let's leave it for now so because i just want to show you that how exactly you can make the fields mandatory in all the condition from dictionary level and that is also with the help of dictionary override and if you want to do it directly and but you have to make sure that you're not impacting other fields or other tables which are basically extended from the base table so as of now we are done with the making fields mandatory in all the condition now we have to make another field mandatory which is assigned to field but there is a condition with it that this should be mandatory if state is not new or cancelled if there is any other state like in progress then assigned to field should be mandatory but you can see as of now it is not mandatory so how we will achieve this particular requirement for that we can use maybe uh client script or ui policy idli ui policy is the best way because ui policy is basically configurable you don't have to write any script so in that case we will use ui policy to make this field mandatory so what i will do i will right click here and i will click on this ui policies i will click on leave and here i will create a new ui policy so once i will click on that it will open up the new form for ui policy where we can create the new ui policy so it's there now it's taking a little bit more time to load so yes it's done now i can just give it a name so maybe i will provide a mock dot set assigned to mandatory this is the name i have given here i have to check the condition and the condition would be if state a state is not is not one-off new or cancelled so if state is not new or cancelled if i click here both are selected you can see both are selected so if the state is not one of new that means if state is not new or cancelled then it should be mandatory so i can just click on save and that's that's the reason ui policy is really good because you don't have to write any script you can still write the script in ui policy depend on the use case but overall you can definitely achieve a lot of things without a script so now what i will do i will go to ui policy action so we have just created the ui policy now i will create ui policy action to make that field mandatory so i will click here and then i will select that field and if i will select that field where is that field assigned to so we have assigned to right here it's selected and here in mandatory i will make it true now important point here is that ui policies are basically used to make fields mandatory visible or read-only that's the main purpose of a ui policy so if you have to make fields mandatory visible or read only then you will always use always uh use ui policy so now what i will do i will just click on submit so that our ui policy and ui policy action will be created properly but you have to remember one thing once you create the ui policy action you have to note that is the any you have to check basically that is there any red dot just beside that field name and you can see we have one what is the reason behind it the reason is i am 100 sure that there should be one another ui policy where we are using the ui policy action on the same field that's the reason you get this kind of alert now how you can remove this there's a better way to find it you can basically change the order of this particular ui policy if you will change the order it will automatically be fixed because if you will have same order so i can show you that what exactly uh order we have so maybe let me go to the create new and let's check this first whether it is happening or not if i go to in progress okay it is making it it is making this field as mandatory but we don't want that uh extra icon which was available over there for that what i can do i can go to ui policies and i will just change the order so here we have uh this one let me check yeah this is the one we just created you can see we have a lot of ui policy with the same order hundred so what i will do i will make it let's say um 300 i will make it different so it's 300 now and i'm sure this time you will see that you will you will not get that particular red dot beside that field so if i reload this ui policy absolutely you can see this got removed now if i click on create new again and see if i change this let's say if i select in progress absolutely you can see now assigned to is mandatory that is also on the basis of some condition where state is not in progress or cancelled then assignment assigned to field should be mandatory else not so if you have it is matching the condition it will work as expected as per the configuration you have mentioned in your ui policy so now you are done with making fields mandatory for both type of situation that means for all the conditions that means every time that field has to be mandatory and even on the basis of some conditions where you have put in some logics and uh conditions that on the basis of those conditions your fields should be mandatory thanks for watching this video please like share and comment and do not forget to subscribe to my channel thank you and have a great day