Notifications

19 views

Description

Build information:
New York and previous

Issue Description:
From a List view, when --none-- is defaulting or otherwise selected as the current value of a dependent field, ALL choices are listed on the depending fields. This is the opposite behavior from Form View of the same fields, where NO choices appear until the dependent field has a value other than --none--.

Business Impact:
- It may be expected that no choices are available on the depending choice list, until a valid value is selected per the [sys_choice.dependent_value] configuration.
- This is how the platform works on the Form view of the same fields.
- The difference in behaviors is confusing.

Symptoms:
1. In a list view, an end user is able to see all choice options for a field which should be restricted based on the value of a dependent field.
2. This happens when the dependent field's choice is defaulting or otherwise set to none.

Steps to Reproduce

1. Navigate [incident.list] for a list of incident records.
2. If needed, personalize the columns to ensure the 'category' and 'subcategory' columns are displayed.
3. Filter the list where 'category' is '--none--' (There should be a few on an OOB instance)
4. Try cell-editing either the subcategory or category column.

Expected:
No options should be available for subcategory, since no no subcategory choices are configured for a '--none--' category.

Actual:
All choices are available.

Notes:
If you now select one of the records to open the form view, you will notice the subcategory is empty until a valid category is selected.

Workaround

This problem is currently under review and has no workaround. To receive notifications when more information will become available, subscribe to this Known Error article by clicking the Subscribe button at the top right of this form. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.


Related Problem: PRB1378649

Seen In

SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - GRC Workbench - New York 2019 Q3
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Vendor Risk Management - Madrid 2019 Q1
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Security Incident Response UI Patch - London 2019 Q2 v.6.2.3
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - VR - Qualys - New York 2019 Q3
SR - VR - Vulnerability Response - New York 2019 Q3

Intended Fix Version

Paris

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-04-09 05:13:33
Published:2020-04-09