- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2016 04:25 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2016 04:49 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2016 04:59 AM
Hi Rajesh,
What release of ServiceNow are you using?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2016 05:57 AM
Hi Chuck,
Am using Eurekha patch 5
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2016 06:05 AM
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.