Issue
A change request is created from the standard template then the change record is showing the risk as low which is a default value set in the dictionary but after the record insertion the risk field value is being empty or null
Steps to reproduce:
1.Set the risk field to readonly in dictionary and the default value is low
2.Configure a template with the fields having value
3.Open the template where the change request will be created
4.Check the risk field if the value is set to low or not
5.save the request
6.Check the risk value in the request
Cause
There is a property which is used to check the fields mentioned in that property to see if they are present in the template and assign that value to the field based on the value in the template by
The above-mentioned value setting process for readonly is done by the business rule 'Restrict fields from Standard Change' which is calling the script include 'StdChangeUtilsSNC' and setting the read-only values
Resolution
Check the read only property in the below mentioned link
https://<instance-name>.service-now.com/std_change_properties.do?sys_id=527b5dafff700200b18affffffffff89&sysparm_view=&sysparm_record_target=std_change_properties&sysparm_record_row=1&sysparm_record_list=&sysparm_record_rows=1
As there is no value set for the risk field in the template it sets the value as empty or null;
Business rule : Restrict fields from Standard Change
Related Links
The other possibilities where the risk value is being set to empty
check if there are any client scripts which are setting the risk field to empty
check if there are any Business rules which are setting the risk field to empty
