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.
Standard change template with special characters (^) is not saved - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Standard change template with special characters (^) is not saved
KB0722933

Standard change template with special characters (^) is not saved


651 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Description

Templates that contain ^ in one of the field values do not work.

Steps to Reproduce


Steps to reproduce demonightlyhelsinki and demonightlyistanbul , demonightlylondon
Create change template:
1) In a field (for example, Test Plan), add: crontab -l|grep -v "^#"
2) Fill in a Category (mandatory field).
3) Click "Request Approval"
4) When click Save or Request Approval, a field is automatically added "Active is true". I removed it.
5) Approve it in Related Link at bottom.
6) Then create a standard change with the template that was just created

Special characters are not there. It is truncated to: -l|grep -v "

On some customer's instances, they try to create a change from a standard template with special characters, and the page just blanks out.

Workaround

After carefully considering the severity and frequency of the issue, and risk of attempting a fix, it has been decided not to address this issue. We do not make this decision lightly, and we apologize for any inconvenience. If you have any questions regarding this problem, contact ServiceNow Customer Support. The reason for this is 

"This is a limitation of how values are stored in template fields. We need a character to differentiate conditions in what is stored in the DB as a plain text string, and we've always used carrots (^) for this in our filter code. Changing this would be extremely high risk (as it would impact our basic filter and queries in addition to templates), and we would just need to use a different character that would still end up triggering this behavior.


Related Problem: PRB1072397

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.