Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Users are unable to create Standard Change templates as some fields are read-only - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Users are unable to create Standard Change templates as some fields are read-only
KB0856285

Users are unable to create Standard Change templates as some fields are read-only


1590 Views Last updated : Nov 28, 2022 public Copy Permalink
KB Summary by Now Assist

Issue

Users with ITIL role cannot create standard change templates.

The Short description and Description fields are read only on the template form.

Cause

Custom ACLs created to control access to the Short description and description fields on change_request table. (by a preferred partner)

The ACLs work as intended on the change request form but this issue was noticed when the customer decided to start using standard change templates.

Resolution

We found the issue to be caused by two custom ACLs:

change_request.short_description and change_request.description (write)

When these ACLs are deactivated then the fields are editable.

These ACLs were created to control access to the "Short description" and "Description" fields on the change_request form but, when these ACLs are evaluated for templates,

these are done on the field level and not what the value is, so the system is then checking the condition, but active is undefined on the template form so the ACL fails before event getting to the script section.

To fix this, both ACLs conditions were amended to include when Active > is > empty

By amending the ACL to check to see if Active is empty, satisfies this, and therefore can proceed.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.