glide.event_processor.all_events_upgrade_safe The glide.event_processor.all_events_upgrade_safe property determines whether all events are processed during a platform upgrade. Setting it to true ensures that no events are missed, which is crucial for maintaining system functionality during upgrades.
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? | This property, when enabled, allows the processing of all events during a platform upgrade, ensuring comprehensive event handling. |
|---|---|
| What area does it affect? | Event processing during upgrades |
| What does the default mean? | No default value is stated in the ServiceNow documentation. |
| When should you review it? | Review this property before performing a platform upgrade to ensure all necessary events are processed. |
Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.
| Property name | glide.event_processor.all_events_upgrade_safe |
|---|---|
| Type | Not stated |
| Application | Not stated |
| Default value | Not stated |
| Description | Not stated |
Official references and nearby text excerpts where this property appears.
glide (other)Other properties in the same namespace.
glide.escalation.notes
This property configures the escalation engine to log activities in task work notes, providing a record of act
glide.escalation.sticky
This property controls the timing of escalation assignments, allowing them to be fixed at ticket creation or r
glide.escalation.verbose
This property configures the system to log verbose messages related to escalations, providing more detailed in
glide.evaluation.enabled
This property controls the availability of the A/B Evaluation Testing framework, impacting how experiments are
glide.events.stuck_states.virtual_agent
This property configures the recovery of specific sysevent states from the virtual_agent queue during node cra
glide.expert.checkout.twostep
This property determines whether the two-step checkout process is utilized when users place Catalog Orders thr
glide.fdih.retry.max_count
This property configures the maximum number of retries for failed data imports, ensuring efficient handling of
glide.gig.client.endpoints
This property defines a comma-separated list of GIG gateway endpoints in host:port format, determining where t