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.
List control configurations do not work in Agent Workspace - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • List control configurations do not work in Agent Workspace
KB0787199

List control configurations do not work in Agent Workspace


3631 Views Last updated : Mar 6, 2024 public Copy Permalink
KB Summary by Now Assist

Description

List control configurations such as "Omit new button" are not working in Agent Workspace.

Steps to Reproduce

  1. Open any incident record from workspace List
  2. Open same Incident record and scroll down to the related list
  3. Make sure both workspace record and Platform are in the same view
  4. Right click on Incident Tasks >> Configure >> List Control
  5. Uncheck 'Omit New condition' and add below script in 'Omit new condition':
    answer=true;
  6. Reload the incident record and scroll down to related list 'Incident Tasks'. As per the list control configuration, there is no 'New' button available.
    7. Reload the same record in the workspace. See the 'New' button under related list 'Incident Tasks'.

Workaround

This is expected behaviour in currently supported releases. Workspace lists do not support the list control, the buttons are driven by declarative UI Actions.

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 near future releases. We do not make this decision lightly, and we apologise for any inconvenience.


Related Problem: PRB1338639

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.