Property reference

com.glide.history_walker.max_history_count

The com.glide.history_walker.max_history_count property sets the maximum number of history records to process when retrieving audit data. Admins should review this setting to optimize performance when the number of field updates exceeds the defined threshold, ensuring efficient data retrieval.

Default
Not stated
Type
Not stated
Application
Not stated

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do? This property determines the maximum count of history records the checkpoint walker processes, influencing whether it uses the sys_audit or sys_history_set table for optimal performance.
What area does it affect? Audit history retrieval
What does the default mean? No default value is stated in the ServiceNow documentation.
When should you review it? Review this property when experiencing performance issues with history data retrieval or when the number of field updates is high.

Property record

Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.

Property name com.glide.history_walker.max_history_count
Type Not stated
Application Not stated
Default value Not stated
Description Not stated

Sources

Official references and nearby text excerpts where this property appears.

Context preview Snippet 1
the system property com.glide.history_walker.max_history_count. If the record to walk has a sys_mod_count that exceeds the value set in this property, default value = 1,000, the checkpoint walker uses the sys_audit table to obtain history ...

More in com.glide

Other properties in the same namespace.

All 831 properties in com.glide →