Hi Chuck,

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

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.

Hi Chuck,

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

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.

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.