Collected scores and com.snc.pa.breakdown_element_cutoff

  • Release version: Xanadu
  • Updated August 1, 2024
  • 2 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 document explains how thecom.snc.pa.breakdownelementcutoffproperty controls which breakdown elements are displayed in the Analytics Hub and KPI Details for a selected date. The display behavior depends on the number of breakdown elements and their scoring history, affecting both automated and formula indicators.

    Show full answer Show less

    Key Details

    • If the number of breakdown elements exceeds the com.snc.pa.breakdownelementcutoff value, only elements that have ever had a score are shown. For formula indicators, this applies across all contributing automated indicators.
    • For collected scores of automated indicators (non-real-time scores), two cases apply:
      • If the number of scored elements is less than the cutoff, all such elements are listed for any selected date, including those with null scores on that date.
      • If the number of scored elements exceeds the cutoff, only elements with a score or a change value on the selected date are displayed. Elements without a score or change value on that date are excluded.
    • For real-time scores and formula indicators, elements with null scores may still appear regardless of the cutoff value.

    Practical Implications for ServiceNow Customers

    • Adjusting the com.snc.pa.breakdownelementcutoff setting allows you to control the volume and relevance of breakdown elements shown in analytics views, improving clarity and performance.
    • Setting a low cutoff value (e.g., 0 or 1) can help prevent elements with null scores from cluttering your Analytics Hub or KPI Details for automated indicators.
    • The elements displayed can vary by selected date when the cutoff is lower than the number of scored elements, showing only those with meaningful data or changes on that date.

    Example Scenario

    Using the "Number of open incidents" indicator with an Assignment Group breakdown of just under 50 elements:

    • When cutoff = 50 (greater than number of elements), all elements appear for any date.
    • When cutoff = 10, but only 8 elements have ever scored (less than cutoff), all 8 elements are displayed for any date, including null scores.
    • When cutoff = 5 (less than scored elements), only elements with a score or a change value on the selected date are shown, which varies by date.
    • Elements with a null score but a change value from previous periods (e.g., Analytics Settings Manager) may still appear.

    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.

    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 eight elements have ever had a score. This number is less than the cutoff value of 10, so for any date, all eight elements are shown, even when 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.

    Only non-null and changed elements of Assignment Group being shown for each date.

    Note:

    The Analytics Settings Manager element is shown for March 7 despite having a null value. It is shown because it had a value of 5 for the previous collection period and thus has a change value of -5 for March 7.

    Number of Open Incidents with Assignment Group: Analytics Settings Managers at zero for today and 5 for yesterday.