Conditional filters and operators for indicators and breakdowns
Summarize
Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
Summary of Conditional filters and operators for indicators and breakdowns
This content explains how conditional filters and operators work within indicators and breakdowns in ServiceNow, specifically in the Zurich release. It highlights best practices for applying conditions to optimize data collection, the limitations on operators at different levels, and special considerations for indicator configurations in data visualizations.
Show less
Conditional Filters on Indicators and Indicator Sources
- Conditions can be applied both at the indicator source and individual indicator levels.
- For efficiency and clarity, conditions common to all indicators sharing the same source should be applied at the indicator source level.
- To ensure conditions are well designed, review the Conditions field when listing indicators for an indicator source, ensuring at least one indicator uses only the source-level conditions to avoid collecting unused data.
- Avoid referencing the Roles table in indicator conditions; such references are allowed only in indicator source conditions.
- Indicators with conditions that reference only dot-walked fields must have at least one breakdown associated.
- Minimize dot-walking to sysid or display values as this creates unnecessary table joins and impacts performance.
Unsupported Operators on Indicator Conditions
Certain operators are not supported directly on indicator conditions but can be used on indicator source conditions instead. These include:
- keywords
- greater than field
- less than field
- greater than or is field
- less than or is field
"Is one of" and "Is (Dynamic)" Operators on Breakdown Conditions in Data Visualizations
When filtering indicator scores by breakdown elements in data visualizations, availability of the "is one of" and "is (dynamic)" operators depends on indicator and breakdown configurations:
- "Is one of" operator requires that the indicator’s aggregation method is neither AVG nor COUNT DISTINCT. This applies to automated indicators and formula indicator contributors. For formula indicators, the option Allow aggregation of multiple breakdown element scores must be enabled.
- "Is (dynamic)" operator also requires the aggregation method not to be AVG or COUNT DISTINCT, and:
- The breakdown source field must be a reference field.
- An elements filter with a dynamic conditional filter must be defined on the breakdown source (e.g., the "Me" elements filter).
- For formula indicators, Allow aggregation of multiple breakdown element scores must be enabled.
Conditional filters for indicator data cascade from indicator and breakdown sources up to data visualizations. Where conditions are applied can affect data collection efficiency. Some condition operators are only available at some levels, or in some conditions.
Conditional filters on indicators and indicator sources
Conditional filters can be applied to both automated indicators and indicator sources. In general, conditions that are applied to all indicators with the same source should be applied on the indicator source. To verify that your
conditions are well designed, list the indicators for an indicator source and include the Conditions field in the view. You should have at least one indicator that only uses the conditions on the indicator source. Otherwise, your
indicator source is probably collecting unused data. In this case, consider moving common conditions from the indicators to the indicator source, or splitting the indicator source.
Warning:
To avoid a data collection job completing with errors, follow these limitations:
- Do not add a condition that references Roles to an indicator. You can reference the Roles table only in an indicator source.
- If you define conditions that refer only to dot-walked fields, you must associate at least one breakdown with the indicator.
In general, try to avoid dot-walking to sys_id or the display value of a table, as doing so creates unnecessary table joins.
Unsupported operators on indicator conditions
The following operators are not supported on indicators. You can use these operators on the indicator source conditions instead:
- keywords
- greater than field
- less than field
- greater than or is field
- less than or is field
"Is one of" and "Is (Dynamic)" operators on breakdown conditions in data visualizations
When you select an indicator data source for a data visualization, you have the option to filter the scores by breakdown element.
The availability of the "is one of" and "is (dynamic)" operators depends on how you configure the indicator. The indicator must support multi-element aggregates. The required configuration settings follow:
- Is one of
-
- The aggregation method must not be AVG or COUNT DISTINCT. This requirement applies to automated indicators including the contributing indicators of formula indicators.
- If the indicator is a formula indicator, the Allow aggregation of multiple breakdown element scores option must be on.
- Is (dynamic)
-
- The aggregation method must not be AVG or COUNT DISTINCT. This requirement applies to automated indicators including the contributing indicators of formula indicators.
- The field in the breakdown source must be a reference field.
- An elements filter must be defined for the breakdown source, and this elements filter must have a dynamic conditional filter. For an example, see the Me elements filter on an instance. For more information, see Element filters.
- If the indicator is a formula indicator, the Allow aggregation of multiple breakdown element scores option must be on.