Out of the box artefacts that read this property. Append the path to your instance URL to open the record and see how the value is used.
Script include: EmPopulateImpactedServices
The process reads this integer setting to determine the bulk batch size for impacted-service records, letting admins adjust how many are handled per batch. It uses 500 when no value is configured.
/sys_script_include.do?sys_id=71c4aa147f54221097bef39c6d866552
Script include: EmSyncSeveritiesInImpactedServices
It reads this integer setting as the batch-size value, which is intended to change how many impacted-service records are handled per batch; the shown code does not show its later effect. If no value is provided, it uses 500.
/sys_script_include.do?sys_id=ea45124bffba221097beffffffffff2d
Script include: HealthLicenseReportPopulator
The report reads this property to set the batch size for processing health configuration items; changing it affects how many items are handled in each batch, not the report’s licensing rules. If unset, the code uses 500.
/sys_script_include.do?sys_id=a67566eeb79d201018c58129ce11a995
Script include: HealthLicenseReportPopulatorWithOTOM
/sys_script_include.do?sys_id=35633486eb44301031fbba2706522807
Script include: HealthLicenseReportPopulatorWithOTOMStore
/sys_script_include.do?sys_id=1a7986bbb742701046df8985de11a95d
Fix Script: EM - populate impact_status_key value
The script reads this property as an integer to set the batch size for processing impact-status records with no key. If it is unset, the script uses 500; changing it changes the batch size, not the records’ impact status.
/sys_script_fix.do?sys_id=87c55cca5fe133003f7b822b3f731366