Conditional filters and operators for indicators and breakdowns
Summarize
Summary of Conditional Filters and Operators for Indicators and Breakdowns
Conditional filters for indicators enable efficient data visualization and collection by applying specific criteria to both indicators and their sources. Proper use of these filters can enhance data relevance and minimize unnecessary data collection.
Show less
Key Features
- Conditional Filters: Apply conditions to automated indicators and their sources, ensuring efficiency in data collection.
- Design Verification: List indicators for an indicator source and include the Conditions field to confirm the effectiveness of applied conditions.
- Operator Limitations: Certain operators are restricted to indicator sources, such as keywords and comparative operators (greater than, less than).
- Breakdown Conditions: Use “is one of” and “is (dynamic)” operators in data visualizations for filtering by breakdown elements, contingent upon specific configurations.
Key Outcomes
By understanding and correctly implementing conditional filters, customers can expect improved data accuracy and efficiency in their ServiceNow indicators. Proper configuration will prevent errors during data collection and ensure that visualizations accurately reflect the intended data sets.
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
- 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
- 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
- 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.