Property reference

`glide.hub.process.sync.capture.non_interactive.changes`

The glide.hub.process.sync.capture.non_interactive.changes property determines whether non-interactive changes are captured during Remote Process Synchronization. Admins may want to disable this feature to ignore changes made by scheduled jobs, ensuring only relevant updates are synchronized.

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 configures the synchronization behavior to include or exclude non-interactive changes in Remote Process Synchronization.
What area does it affect?	Remote Process Synchronization
What does the default mean?	No default value is stated in the ServiceNow documentation.
When should you review it?	Review this property when configuring synchronization settings or troubleshooting data synchronization issues.

Property record

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

Property name	`glide.hub.process.sync.capture.non_interactive.changes`
Type	Not stated
Application	Not stated
Default value	Not stated
Description	Not stated

Sources

Official references and nearby text excerpts where this property appears.

Brazil docs View supporting context

Context preview Snippet 1

... are associated. 2487 Note: RPS captures both interactive and non-interactive changes. You can configure RPS to ignore non-interactive changes, such as changes made via a scheduled job, by setting the glide.hub.process.sync.capture.non_interactive.changes property to false. For more information, see the How to configure Remote Process Synchronization (RPS) framework to ignore non-interactive changes to records [KB1565025] article in the Now Support Knowledge Base. ...

More in `glide.hub`

Other properties in the same namespace.

glide.hub.flow.inbound_email_trigger.show_advanced This property allows multiple inbound email triggers to be processed in a specified order, enhancing workflow glide.hub.internal.process_sync.use.inbound_queue_record.merged.table This property enables or disables the use of a merged inbound queue table for inbound processing, impacting ho glide.hub.process.engine.secure.store.clean.data.invalid.context This property enables or disables the cleaning of data linked to flow contexts that are absent in the sys_flow glide.hub.process.engine.secure.store.delete.data.limit This property defines the threshold for the number of entries that can be deleted from the secure store in a s glide.hub.process.sync.debug This property enables detailed debug logging for synchronization processes, helping to diagnose issues during glide.hub.process.sync.jobs.inbound.context_reporting This property configures inbound scheduled jobs to use the standard FlowAPI, facilitating detailed logging of glide.hub.process.sync.jobs.inbound.process_maxtime This property limits the execution time of inbound scheduled jobs, helping to manage system performance and jo glide.hub.process.sync.jobs.inbound.subflow.execution_timeout This property defines the maximum time allowed for inbound subflow executions before they are terminated, impa

All 26 properties in glide.hub →