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.
Sequential xmlhttp requests causing performance issue in CAB definition due to Condition Builder - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Sequential xmlhttp requests causing performance issue in CAB definition due to Condition Builder
KB0745113

Sequential xmlhttp requests causing performance issue in CAB definition due to Condition Builder


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

Description

CAB definition with a lot of picklist/ dropdowns in condition builder causing performance issue

Steps to Reproduce

1. Go to "CAB definition" table list.
2. Open any "CAB definition" record/ create new with a lot of conditions in condition builder having a drop-down.
For Example: Type > is > Standard || Risk > is > Moderate || Category > is > Network etc.
Make at least 10-12 dropdown/ picklist type conditions.
3. Save the form.
4. If Record is in "Global" application then keep "global" or else if it is in "Change Management - CAB workbench" application, change the application to "Change Management - CAB workbench" so that record loads in edit mode.
The issue is only visible when the record is opened in edit mode and not read-only.
5. If on chrome, keep the "Network" tab in "Inspect" open and reload the page.
Observe the behavior of "xmlhttp" requests generating for picklist.
They are getting triggered sequentially.
If there are too many requests and the server is slightly slower then this leads to a huge performance issue.

Workaround

As a workaround, remove the condition builder from the default view and create a 'with conditions' view used when you need to modify the conditions.

This will cause the conditions not to load when users are viewing the record normally thus eliminating the impact of this issue.


Related Problem: PRB1330826

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.