Collected scores and com.snc.pa.breakdown_element_cutoff

  • Release version: Zurich
  • Updated July 31, 2025
  • 3 minutes to read
  • 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 Collected scores and com.snc.pa.breakdownelementcutoff

    This documentation explains how thecom.snc.pa.breakdownelementcutoffsystem property affects the display of breakdown elements in the Analytics Hub and KPI Details within ServiceNow's Performance Analytics. It clarifies which elements appear for selected dates based on their scoring history and the configured cutoff value, particularly focusing on collected scores of automated indicators and formula indicators.

    Show full answer Show less

    Key Details and Behavior

    • The number of breakdown elements shown depends on the com.snc.pa.breakdownelementcutoff value and the count of elements that have ever had a score.
    • If the number of elements exceeds this cutoff:
      • For formula indicators, only elements that have had scores across all contributing automated indicators (at any date) are shown.
      • For collected scores of automated indicators:
        • If elements with scores are fewer than the cutoff, all such elements are shown for any selected date, including those with null scores on that date.
        • If elements with scores exceed the cutoff, only elements with a non-null score or a change value on the specific selected date are displayed.
    • Elements with null scores might still appear for real-time scores and formula indicators regardless of cutoff settings.
    • To minimize display of elements with null scores in automated indicators, consider setting com.snc.pa.breakdownelementcutoff to a low value (e.g., 0 or 1).

    Practical Examples

    Using the "Number of open incidents" KPI and its Assignment Group breakdown (around 50 elements), the documentation illustrates these behaviors:

    • Cutoff = 50: Since the cutoff equals or exceeds the number of elements, all elements are displayed for any selected date.
    • Cutoff = 10: Although the number of elements exceeds the cutoff, only six elements have ever had scores (less than 10), so all six are shown for any date, including those with null values.
    • Cutoff = 5: As this is less than the number of scored elements, only elements with a non-null or change value on the selected date appear, varying day-to-day. Null values following a scored date may show as zero with a decline indicator, but elements with consecutive nulls disappear from the display.

    Implications for ServiceNow Customers

    Understanding and configuring com.snc.pa.breakdownelementcutoff helps control the granularity and cleanliness of breakdown element displays in Performance Analytics. Adjusting this cutoff enables customers to:

    • Limit the number of elements shown to improve clarity and relevance.
    • Avoid clutter caused by elements with null or no recent scores.
    • Ensure that scorecards and dashboards reflect meaningful data per date selection.

    These configurations ultimately enhance the interpretability and usability of performance data, supporting better operational decisions based on trends and changes in indicator breakdowns.

    The elements of a breakdown that the Analytics Hub and KPI Details display for a selected date depend on the number of elements and the value of com.snc.pa.breakdown_element_cutoff.

    In general, when the number of elements for a breakdown exceeds com.snc.pa.breakdown_element_cutoff, the Analytics Hub and KPI Details display only the elements that have ever had a score.

    For a formula indicator, the elements that have ever had a score for all the contributing automated indicators are displayed. These scores do not need to be on the same date. The requirement is only that for each contributing indicator, on some date, there was a score for the element.

    For collected scores of an automated indicator—that is, for all scores other than real-time scores—there are two behaviors:
    • If the number of elements that have ever had a score is less than the limit set in com.snc.pa.breakdown_element_cutoff, all of these elements are listed for any selected date. Elements that do not have a score for the selected date are still listed for that date. This behavior is the same as the behavior for real-time scores.
    • If the number of elements that have ever had a score is greater than the limit set in com.snc.pa.breakdown_element_cutoff, only elements that have a score or a Change value for a selected date are listed for that date. Elements that do not have a score or Change value for that date are not listed regardless of whether they have a score for any other date.
    Tip:

    To prevent elements with null scores appearing in the Analytics Hub or KPI Details for automated indicators, consider setting a low value for com.snc.pa.breakdown_element_cutoff, such as 0 or 1. Elements with null scores may still appear however for real-time scores and formula indicators.

    Scores appearing for automated indicators with different values of com.snc.pa.breakdown_element_cutoff

    This example uses KPI Details to explore the Assignment Group breakdown for the "Number of open incidents" indicator. The Assignment Group breakdown on the instance used in the example has just under 50 elements.

    First is the default case, where com.snc.pa.breakdown_element_cutoff=50. This value is higher than the number of elements of Assignment Group. Therefore, for any selected date, all elements of the breakdown group are displayed.

    Figure 1. All elements of Assignment Group shown in KPI Details
    All elements of the Assignment Group breakdown being displayed.

    The next case is where com.snc.pa.breakdown_element_cutoff=10. The number of elements in the Assignment Group breakdown far exceeds this value. However, only six elements have ever had a score. This number is less than the cutoff value of 10, so for any date, all six elements are shown, even when null.

    Figure 2. All elements shown that were never null
    All elements of Assignment Group that ever had a score being displayed.

    Finally, there is the case where com.snc.pa.breakdown_element_cutoff=5. This number is less than the number of elements that have ever had a score. Now only the elements with a non-null value or a change value on the selected date are shown on that date. Different elements are thus shown for different dates. If there is a null value for the collection period after one with a value, a value of zero and a change symbol appears for that day.

    Figure 3. Scoresheet for Number of Open Incidents showing which null scores are shown as 0 with a change icon and which are not shown at all
    Scoresheet for Number of Open Incidents showing which null scores are shown as 0 with a change symbol and which are not shown at all.

    On March 18, six elements are shown. The Hardware element, which has a null value, shows a value of 0 and a symbol that it declined.

    Figure 4. Assignment Group elements shown on March 18
    Assignment groups shown on March 18.
    On March 19, five elements are shown. Hardware is not shown, because it has had a null value for two days running. The Network element, which now has a null value, shows a value of 0 and a symbol that it declined.
    Figure 5. Assignment Group elements shown on March 19
    Assignment Group elements shown on March 19.
    On March 20, five different elements are shown. Network is not shown, because it has had a null value for two days running. The Openspace element, which now has a null value, shows a value of 0 and a symbol that it declined.
    Figure 6. Assignment Group elements shown on March 20
    Assignment Group elements shown on March 20
    On March 21, five different elements are shown. Network now has a value and is shown. Openspace has had a null value for two days running, so is not shown.
    Figure 7. Assignment Group elements shown on March 21
    Assignment Groups shown on March 21.
    On March 22, six elements are shown. Openspace now has a non-null value so is shown again.
    Figure 8. Assignment Group elements shown on March 22
    Assignment Group elements shown on March 22