---
sourceDocument: Brazil Platform Analytics
sourceDocumentLink: https://www.servicenow.com/docs/r/now-intelligence

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Collected scores and com.snc.pa.breakdown_element_cutoff

# Collected scores and com.snc.pa.breakdown_element_cutoff {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
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](https://www.servicenow.com/docs/SAYEkH1d7Qjsj7I4aT4WVg#gloss-contributing-indicator "An indicator that is used in the formula of a formula indicator. A contributing indicator can be an automated or a formula 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.
{#collected-element-display-cutoff__ul_atz_q3x_5sb}  
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 {#collected-element-display-cutoff__example_wzj_slx_5sb}

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

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

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

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  
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  
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  
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  
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