question Re: On the change template creation form i want to hide/restrict all fields that do not currently exist on the Change form in Developer forum

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

Rajesh PanneerS — Mon, 25 Jul 2016 09:59:11 GMT

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

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

Chuck Tomasi — Mon, 25 Jul 2016 10:27:30 GMT

Hi Rajesh,

You can restrict read access on those fields using ACLs so users cannot see the fields and they will not be available to pick them.

This does require you to manually set ACLs to sync with the fields on your form and keep them updated as new fields are added/removed from your form view(s) which can be tedious and possibly prone to conflict.

Reference:

Using Access Control Rules - ServiceNow Wiki

Security Best Practices - ServiceNow Wiki

Contextual Security - ServiceNow Wiki

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

Rajesh PanneerS — Mon, 25 Jul 2016 10:34:51 GMT

Hi Chuck,

So the ACL should be on the sys_template table and then i should create one for each read only field. Can you please provide an example ?

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

Chuck Tomasi — Mon, 25 Jul 2016 10:38:38 GMT

The ACL should be on the table your template points to (e.g. change_request.)

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

Rajesh PanneerS — Mon, 25 Jul 2016 10:54:15 GMT

Hi Chuck,

But creating an ACL will hide the fields not only on the Change request template creation form right?

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

Chuck Tomasi — Mon, 25 Jul 2016 11:00:17 GMT

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.

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

Rajesh PanneerS — Mon, 25 Jul 2016 11:17:54 GMT

Hi Chuck,

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

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

Chuck Tomasi — Mon, 25 Jul 2016 11:25:01 GMT

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.

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

Rajesh PanneerS — Mon, 25 Jul 2016 11:49:20 GMT

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.

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

Chuck Tomasi — Mon, 25 Jul 2016 11:59:56 GMT

Hi Rajesh,

What release of ServiceNow are you using?

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

Rajesh PanneerS — Mon, 25 Jul 2016 12:57:55 GMT

Hi Chuck,

Am using Eurekha patch 5

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

Chuck Tomasi — Mon, 25 Jul 2016 13:05:50 GMT

Hi Rajesh,

I don't have a Eureka instance to test this on at the moment. Based on the fact that Eureka is no over to years old and three major releases behind, I recommend upgrading to avoid this and potentially other issues.

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

Rajesh PanneerS — Tue, 26 Jul 2016 07:54:36 GMT

Hi Chuck,

So is there anyway to block non editable fields being set using the change template?

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

Chuck Tomasi — Tue, 26 Jul 2016 10:10:25 GMT

Hi Rajesh,

I just tried a template on Eureka that attempts to set two read-only fields and two editable fields. Both read-only fields are protected by ACL (not the read-only attribute on the dictionary.) In both cases, the read-only ACL was respected.

I submit that your field is not being protected (made read-only) by an ACL, but possibly by a UI policy or client script.

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

Rajesh PanneerS — Tue, 26 Jul 2016 15:27:39 GMT

Hi Chuck,

Yes, in my case the fields are made readonly using UI policy. Is it possible to restrict the change template being applied to the read only fields.

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

Chuck Tomasi — Tue, 26 Jul 2016 15:48:08 GMT

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

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

Pradeep Sharma — Tue, 26 Jul 2016 15:53:09 GMT

Hi Rajesh,

I agree with Chuck on this one. You will have to adjust access permission via ACL instead of UI policies.