Standard Change Template (propose a new template) field dependencies are not honored - Support and Troubleshooting

Standard Change Template (propose a new template) field dependencies are not honored Issue  Symptoms Standard Change Template (propose a new template) field dependencies are not honored

Release All

Cause This is the expected behavior. When you are proposing a new template you are using a record producer. The sys_dictionary requirements are not enforced on the record producer because the selections are variables that will be mapped into the values on the form once the template is applied to a record.

Resolution Just like on any other record producer, if you wish to filter the options available for one field selection based on the value of another, you will have to write a Catalog Client Script or UI Policy on the Record Producer "Propose a new Standard Change Template" that will enforce this filtering of the options.

Additional Information Create a Service Catalog Client Script:

https://docs.servicenow.com/csh?topicname=t_CreateACatalogClientScript.html&version=latest

Create a Service Catalog UI Policy:

https://docs.servicenow.com/csh?topicname=c_ServiceCatalogUIPolicy.html&version=latest