- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-05-2017 11:26 AM
I'm hoping this is something minute that I'm missing. itil role users are unable to write the "Change Template Values" field when they are creating a Standard Change Proposal. Apart for ACLs and UI policies, is there anything else I should be checking?
I have reviewed the Script Include as well and made sure that none of those are blocking access when the state is NEW.
ACL debug results on template_value field.
Do you know of something else I should check?
Appreciate any help!
Solved! Go to Solution.
- Labels:
-
Change Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-06-2017 06:38 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-05-2017 01:24 PM
I would verify that you do not need template editor role to make the changes, We do not use the standard change catalog here
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-06-2017 06:05 AM
Thanks but the test account I am using has the template_editor role. This must be something else.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-05-2017 01:37 PM
Check below client script
Set template value read only
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-06-2017 06:07 AM
Thanks. We have not modified that Client Script. I don't see why that would block access for itil role.