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.
Catalog UI Policy conditions can not be saved properly when using "is different" - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Catalog UI Policy conditions can not be saved properly when using "is different"
KB0715731

Catalog UI Policy conditions can not be saved properly when using "is different"


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

Description

Catalog UI Policy can not be saved when using the condition "is different".

Steps to Reproduce

1. Open the OOB record producer "Create Incident" 
/sc_cat_item_producer.do?sys_id=3f1dd0320a0a0b99000a53f7604a2ef9

2. Add 2 "reference" type variable: 
2.1 
Type: Reference
Question: Who is the caller?
Name: u_caller
Order: 500
Reference: sys_user tables
Reference qualifier condition: active is true;
2.2 
Type: Reference
Question: Who will be assigned to this incident?
Name: u_assignee
Order: 600
Reference: sys_user tables
Reference qualifier condition: active is true;

3. Open the RP "Create Incident" again, create a Catalog UI Policy, put the condition
"u_assignee" "is different from" "u_caller"

Notice you can not save the Catalog UI Policy with that condition.

Workaround

The problem ticket associated with your incident has been reviewed by ServiceNow. After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or future releases. We do not make this decision lightly, and we apologize for any inconvenience.



Related Problem: PRB1307725

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.