On the change template creation form i want to hide/restrict all fields that do not currently exist on the Change form

Rajesh PanneerS · ‎07-25-2016

Users are able to see all the fields in the change request template creation form. In the below screenshot, Activity due field is not available in the change form but it is visible here. So my requirement is to show only the fields visible on the change form. Is it possible to hide or make these fields read only

Chuck Tomasi · ‎07-26-2016

Hi Rajesh,

Thank you for confirming. The templates do not respect UI policies because they are evaluated on the client side and can be variable depending on almost any condition. The template is imported on the server side. So - short answer "no".

I know that's not the answer you were looking for, but it is an answer. If you would be so kind... please mark it as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.

If you are viewing this discussion from your "inbox", use the "mark as correct" option under actions. If you are viewing it directly from the thread use the Correct Answer link (red with a star).

Thank you

View solution in original post

Chuck Tomasi · ‎07-25-2016

Hi Rajesh,

It could have impact on other areas as well. I haven't tested this specifically for templates. You will have to do some testing to see if list filters, reports, etc are impacted. You may also need to change the ACL for the operation 'report_on' rather than read. See my earlier links.

Rajesh PanneerS · ‎07-25-2016

Hi Chuck,

Is there any way to block the change template from being applied to read only fields in the change request form?

Chuck Tomasi · ‎07-25-2016

Hi Rajesh,

Based on what I just tested, I don't think you need to worry about read-only fields (as long as they are read-only based on ACL or dictionary attribute.) UI policy is a different scenario.

I just created a template on the incident field as an ITIL user (Beth Anglin). I tried to set the number field to "BETH". Since the number field is read-only, it would not apply the template. I got the error seen below.

If someone tries to do something they shouldn't through a template, it does not let them.

Rajesh PanneerS · ‎07-25-2016

Hi Chuck,

I created an template with Approval as approved and Urgency as critical. When i applied the temmplate urgency and appravl was set. I tried this with an ITIL user and we have an ACL for the Urgency field.

Chuck Tomasi · ‎07-25-2016

Hi Rajesh,

What release of ServiceNow are you using?