Create a Report showing Mandatory fields for all items on a form

[Lisboa]

I've been asked to build a report to show which fields are mandatory on a form.  This is for the ITSM space, so think of a report that shows the form name (ex: Incident), the field name on the form (ex: Impact) and then a true/false flag as to whether or not the field on the form is mandatory.  Well aware mandatory state can be configured through multiple means within the platform, so I'm really not confident of an answer here.

1. Is this even possible?
2. Is this something that can be reported from a master table (kind of like Tasks), or is this a rinse and repeat where I need a report per form/module?

Appreciate any help or insights folks might have on how to rapidly assemble the data.

[kriangkrai]

Hi @Lisboa 

1. Possible
2. There are several ways to set mandatory field on form so it depends on your instance configuration. I would suggest you exploring sys_dictionary and sys_dictionary_override first.

Another way is UI Policies which I'm afraid it's unable to run report on this.

Hope this help.

Oat

[Dr Atul G- LNG]

Hi @Lisboa 

1. Is this even possible?

Atul: Yes and No. Bcz a field can be make mandatory via tables level, via UI policy , Client script and BR as well. So you will get 100% accurate report is tough. Also few fields mandatory in some conditions.

1. Is this something that can be reported from a master table (kind of like Tasks), or is this a rinse and repeat where I need a report per form/module?

Atul: No, as said above, tough.

[AndersBGS]

Hi @Lisboa ,

In general no. As you can see from earlier replies, ServiceNow utilize Client scripts, UI Policies, Dictionary etc. etc. to change field behavior, hence you will no be able to make a consistent report on this.

If my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.

best regards

Anders 

[Lisboa · Accepted solution]

The real answer is, "No".  There is no "one-stop-shop" view to see all fields made mandatory on a field due to the numerous ways in which a field may be coded to become mandatory.

There are workarounds to get to some information, but none of them are foolproof, and none will give "all".