Category · 479 properties
ServiceNow Performance, Limits & Scheduling properties
This group covers system properties related to performance, resource limits, caching, job scheduling, and processing capacity across ServiceNow. Admins and developers can consult these properties when investigating slow or resource-intensive workloads, adjusting operational constraints, or reviewing how scheduled and parallel tasks are managed, including settings such as com.glide.closure_max_rows_per_table and com.glide.cs.auto_resolution.simulation.max_parallel_blocks_to_run.
Most common namespaces: com.glide 65 com.snc 51 glide (other) 36 sn_nxui_framework 18 evt_mgmt 16 glide.db 16
com.glide.amb.flood_mitigation.processor_ids |
It specifies a list of AMB processor IDs that are considered for flood mitigation, affecting which channels can benefit from this feature. |
com.glide.appsee.uxaapp_migration_current_retry_count |
This property defines the maximum number of retries allowed during the UXA application migration process, influencing how the system handles migration failures. |
com.glide.closure_max_rows_per_table |
This property limits the number of rows allowed in a table to optimize performance and prevent excessive data load. |
com.glide.communications.httpclient.usage.collection |
This property determines whether usage metrics for the outbound HTTP client are collected, impacting how usage data is tracked and reported. |
com.glide.core.fix_invalid_claimedby_jobs |
This property enables or disables the automatic correction of invalid job assignments related to the 'claimed by' field. |
com.glide.cs.auto_resolution.simulation.max_parallel_blocks_to_run |
It configures the limit on how many simulation blocks can run simultaneously in the auto-resolution process. |
com.glide.cs.cache.node_details.size |
This property sets the integer value for the size of the node details cache, impacting how much data can be stored for quick access. |
com.glide.cs.click_metrics.crypto_module.cache.max_size |
It defines the maximum allowable size for caching KMF crypto modules, impacting how Click Metrics handles cryptographic operations. |
com.glide.cs.click_metrics.zdt_enabled |
This property activates ZDT support for Click Metrics, allowing for seamless updates without downtime. |
com.glide.cs.collab.card_cache_manager_size |
This property configures the maximum size of the card_cache_manager cache to optimize memory usage during sidebar conversations. |
com.glide.cs.conversation_max_idle_age |
It defines an additional grace period for conversation timeouts, ensuring that conversations are not prematurely terminated while still managing resource usage effectively. |
com.glide.cs.enable_link_unfurling_cache |
This property determines whether the system caches link unfurling results, impacting the speed and efficiency of link previews. |
com.glide.cs.expression_cache_optimization.enabled |
This property activates caching optimization for expressions used by the virtual agent, enhancing response times and reducing processing load. |
com.glide.cs.max_query_result_size |
This property limits the number of records returned by database queries executed in Virtual Agent server processes, enhancing performance and resource management. |
com.glide.cs.performance_logging_enabled |
This property controls whether performance analytics are recorded in the sys_cs_analytics table, providing insights into request processing times. |
com.glide.cs.performance_node_logging_enabled |
It configures the system to log detailed performance analytics for request stages in node logs, aiding in performance monitoring. |
com.glide.cs.task.cache.enabled |
This property enables or disables caching for task data, impacting how quickly tasks are retrieved and processed. |
com.glide.cs.timed.enabled |
This property enables or disables the functionality for timed events within the ServiceNow platform, affecting how scheduled tasks are managed. |
com.glide.cs.va_caching_service.require_lock_to_flush |
This boolean property determines whether a conversation lock is necessary for flushing cached changes to the database at the end of worker thread transactions. |
com.glide.cs.worker.hybrid_queue.mode |
This property sets the operational mode of the HybridQueue, allowing messages to be processed by priority or in a strict sequence. |
com.glide.cs.worker.hybrid_queue.priority_adjustment_ms |
This property sets the time adjustment for the effective timestamp of higher priority messages in the hybrid queue, ensuring they are processed first. |
com.glide.event_handler.impex_parallel_job_handler |
This property configures the class responsible for executing parallel jobs within the event handling framework, impacting job processing efficiency. |
com.glide.event_handler.rw_deferred_responder |
This property specifies the handler used for managing deferred actions when the memory queue cannot accept new requests due to capacity limits. |
com.glide.event_manager.acc_response_queue.reset.rhino_context |
This property enables or disables the auto scaling feature for ECC queue processing, impacting how resources are allocated during high-demand periods. |
com.glide.event_manager.devops.event.queue.claim_limit |
This property limits the number of events that can be claimed simultaneously from the event queue, impacting event handling efficiency. |
com.glide.event_manager.devops.event.queue.hard_limit |
This property defines the hard limit for the event queue size, ensuring that excessive events do not overwhelm the system. |
com.glide.event_manager.discovery.sensor.reset.rhino_context |
This boolean property controls the resetting of the Rhino context, impacting how events are processed in the system. |
com.glide.event_manager.dsb_operation.even.load.distribution.enabled |
It determines whether load distribution is active for event management operations, impacting how events are processed across the system. |
com.glide.event_manager.flow_engine.hard_time_limit |
It specifies the maximum duration events can stay in the event queue before they are re-queued for processing, impacting event handling efficiency. |
com.glide.event_manager.grc_metrics_queue.claim_limit |
This property limits the number of events that one worker thread can handle from the event queue, impacting event processing performance. |
com.glide.event_manager.grc_metrics_queue.even.load.distribution.enabled |
This property controls the load distribution of events in the GRC metrics queue, ensuring balanced processing across worker threads. |
com.glide.event_manager.sidebar_notification.claim_limit |
This property defines the limit on the number of events processed in each batch from the sidebar notification queue, impacting notification delivery speed. |
com.glide.event_manager.territory_overlapping_queue.claim_limit |
This property defines the limit on the number of claims processed simultaneously in the territory overlapping queue, impacting system resource allocation. |
com.glide.event_manager.territory_overlapping_queue.even.load.distribution.enabled |
It determines whether balanced load distribution is applied to events in the territory_overlapping_queue, affecting how events are processed. |
com.glide.event_manager.territory_overlapping_queue.hard_limit |
This property defines the hard limit for overlapping territories in the event manager's processing queue, impacting how events are managed. |
com.glide.event_manager.va_notification_batch.claim_limit |
It limits the number of sys events assigned to a node for execution in one transaction, impacting how events are processed. |
com.glide.http.idle_connection_monitor.async.async.effectively_idle_check.enabled |
It activates the feature that closes idle connections, optimizing performance in the Async HTTP Client framework during streaming. |
com.glide.index_suggestion.enable_periodic_collection |
It configures the system to periodically gather column statistics, enhancing the effectiveness of index suggestions. |
com.glide.job.batched.window_end |
This property defines the end time for the IP Address field Normalization job in HH:mm:ss format, impacting when the job ceases operations each day. |
com.glide.job.batched.window_start |
This property sets the start time for the IP Address field Normalization job in local time, formatted as HH:mm:ss. |
com.glide.max_query_size |
This property limits the number of queries a client script can make, helping to manage system performance and resource usage. |
com.glide.one_extend.cacheable_capabilities |
This property specifies which capabilities can be cached, influencing how data is stored and retrieved for improved performance. |
com.glide.one_extend.enable_capability_caching |
It configures the system to cache capability responses, enhancing efficiency in processing requests. |
com.glide.one_extend.eval.batch_run.enable.throttling |
This property controls whether throttling is applied to batch run evaluations, impacting how resources are allocated during these processes. |
com.glide.one_extend.eval.batch_run.max_in_flight |
It defines the maximum number of records that can be processed concurrently in batch evaluations, impacting system performance and efficiency. |
com.glide.one_extend.eval.batch_run_task_counter_update.max_spins |
It configures the maximum spins allowed for the mutex during batch run task counter updates, impacting concurrency control. |
com.glide.one_extend.eval.batch_run_task_counter_update.spin_wait_ms |
It configures the duration in milliseconds that the system will wait while trying to acquire a mutex for updating the batch run task counter. |
com.glide.one_extend.pattern_match_timeout |
This property defines the maximum time allowed for regular expression matching operations in One Extend, with a configurable range from 0 to 10000 milliseconds. |
com.glide.oneapi.hybrid_queue.push.retry |
It sets the maximum retry attempts for pushing messages to the Hybrid Queue, impacting message delivery success rates. |
com.glide.oneextend.batch_result_cancellation_timeout_minutes |
It specifies the duration after which idle batch result records in a progress state are automatically cancelled. |
com.glide.pad.core.model.scheduledTrigger.maxQueryLimit |
This property defines the upper limit for query executions when the Scheduled Records Processing trigger is activated in Playbooks. |
com.glide.process.adaptive_events.enabled |
This property controls the activation of adaptive event processing, allowing events to be processed more efficiently. |
com.glide.processing.framework.slow_queues |
This property specifies queues that experience slow event processing, preventing additional job creation for those queues to avoid unnecessary delays. |
com.glide.request_manager.active |
This property enables the cancellation of long-running transactions by users, enhancing control over ongoing processes. |
com.glide.schedule.recurrence.num_occurrences_max |
This property limits the number of occurrences returned by scheduling APIs, preventing overload by capping the results at a specified maximum. |
com.glide.stats.daily_snapshot.diff_iostats |
This property controls whether the daily stats snapshot job calculates differences for daily I/O statistics, impacting performance analysis and trend tracking. |
com.glide.stats.storage_disk_usage.information_schema |
This boolean property affects the querying method used by the StatsGatherer job for gathering table statistics. |
com.glide.sysevent.priority.enabled |
This property determines whether events are processed in order of priority, with lower values indicating higher priority. |
com.glide.system_parallel_job.thread_run_time |
This property configures the maximum run time for system parallel jobs, influencing how long these jobs can execute before being terminated. |
com.glide.system_parallel_job_auto_retry |
This property determines whether failed parallel jobs are automatically retried, enhancing job reliability in the system. |
com.glide.system_parallel_job_inactive_time_minutes |
This property defines the timeout period for parallel jobs, determining how long they can run before being automatically reset to a pending state. |
com.glide.system_parallel_job_max_retry_count |
This property determines how many times a parallel job can be retried before it is marked as an error, impacting job completion rates. |
com.glide.transaction.run.with.master |
This property configures the execution context for transactions, enabling concurrent processing by using the main GlideSession when set to true. |
com.glide.update_operation.parallel_operation_enabled |
This property enables or disables parallel execution of certain operations in ServiceNow, affecting how quickly tasks are processed in the system. |
com.glide.update_operation.queue_upgrade_window |
This property sets a customizable window, defaulting to two hours, during which the Application Operation Queue pauses message processing before an upgrade. |
com.snc.actsub.activity.rate.count.limit |
This property defines the cap on activity creation within a designated time period, helping to manage system load and performance. |
com.snc.actsub.activity.rate.time.limit |
This property defines the maximum duration in seconds that activities can be created before the system prevents further activity creation. |
com.snc.actsub.activity.stream.cache.enable |
It activates caching for the ActivityFeed, enhancing data retrieval speed while requiring cache clearance to prevent stale data. |
com.snc.actsub.activity.stream.inactive.disabled |
This boolean property controls whether activity fanouts are sent for user streams that are inactive, helping to reduce unnecessary processing. |
com.snc.actsub.activity.stream.inactive.duration |
This property specifies the number of days of inactivity after which activity fanouts for user streams are disabled, helping to optimize system resources. |
com.snc.actsub.activity.stream.inactive.streams |
It specifies a list of stream names that are considered inactive after a period of inactivity, impacting how the system handles these streams. |
com.snc.availability.v2 |
This property enables or disables the use of the Availability V2 engine for calculating system availability, impacting how performance metrics are generated. |
com.snc.awa.cache.enabled |
This property controls whether the Advanced Work Assignment feature utilizes caching to enhance performance and reduce data retrieval times. |
com.snc.cluster.scheduler.dedicated_node_bypass |
It controls the execution of child jobs on dedicated nodes, impacting job scheduling and processing efficiency. |
com.snc.documents.external.permission.batch_size |
It sets the batch size for processing external document permission requests, with a default of 50. |
com.snc.notify.async_participants_threshold |
This property defines the maximum number of participants allowed before an asynchronous notification action is initiated. |
com.snc.notify.should_use_async |
This property determines whether the system should use asynchronous processing for calls involving a large number of participants, enhancing performance and responsiveness. |
com.snc.on_call_rotation.calendar_macro |
This property defines the macro that enables calendar features for managing on-call rotations, defaulting to the DHTMLX scheduler. |
com.snc.on_call_rotation.calendar_span.max_date_range_days |
This property limits the date range for on-call rotation visibility in the calendar to a specified number of days, defaulting to 30. |
com.snc.on_call_rotation.factor_daily_rotation_interval_all_day |
It configures the timing of daily rotation changes for all-day schedules, either at midnight or at the defined start time. |
com.snc.on_call_rotation.landing_page.group_limit |
This property configures the maximum number of On-Call schedules loaded per view, improving the efficiency of schedule management. |
com.snc.on_call_rotation.show_legacy_calendar |
It toggles the visibility of the legacy On-call calendar within the ServiceNow platform. |
com.snc.pa.dc.max_records |
This property defines the upper limit of records retained during data collection, impacting data management and system performance. |
com.snc.pa.dc.query_time_limit |
This property defines the time limit in minutes for executing a data collection query before triggering a warning. |
com.snc.pa.dc.recordwatcher.filter |
This boolean property determines whether record watchers apply filtering to the records they monitor, impacting data visibility and performance. |
com.snc.pa.dc.use_lazy_collection |
This property toggles the use of lazy collection in data collection, impacting how data is managed in memory during processing. |
com.snc.pa.migrationHealth.refreshInterval |
This property configures the interval at which the migration health monitor refreshes its data, impacting the timeliness of health reports. |
com.snc.pdf.caching_fonts.enabled |
This property enables or disables the caching of fonts used in PDF exports and HTML to PDF conversions, impacting their processing speed. |
com.snc.project.batcher_enable |
This property determines whether the Batcher functionality is active for managing project tasks, impacting overall system performance and task handling. |
com.snc.project.default_schedule |
It defines the default project schedule by referencing a specific sys_id, impacting how projects are scheduled within the system. |
com.snc.project.schedule_cache |
This property controls whether project schedule data is cached, affecting how quickly start and end dates are retrieved. |
com.snc.project.schedule_cache_end |
It defines the maximum year for which project schedule data is cached, impacting how project timelines are managed. |
com.snc.project.schedule_cache_start |
This property sets the initial year for caching project schedules, impacting how project data is retrieved and displayed. |
com.snc.project.task.check_date_span_years |
This property restricts the range of dates that can be entered for project and project task records to a maximum of 10 years into the future or past. |
com.snc.project.task.max_task_duration |
This property limits the maximum duration for project tasks to 2600 days, affecting how long tasks can be scheduled. |
com.snc.project.use_new_engine |
This property determines whether the new recalculation engine is utilized for project financial calculations, impacting efficiency and accuracy. |
com.snc.resource_management.batch_size |
This property sets the batch size for record insertions and updates in the resource management module, impacting data processing efficiency. |
com.snc.resource_management.default_schedule |
This property defines the default schedule name for resource management, which is applied when no specific schedule is assigned to a user. |
com.snc.resource_management.enable_batching |
This property activates the batching feature, allowing multiple resource management tasks to be processed together, improving performance and efficiency. |
com.snc.resource_management.exclude_events_from_schedule |
It defines a comma-separated list of event types that should not be considered when calculating resource availability and scheduling allocations. |
com.snc.resource_management.exclude_status_from_availability |
It allows administrators to define a list of resource assignment states that will not impact the calculation of resource availability, ensuring more accurate planning. |
com.snc.resource_management.generate_daily_aggregates |
This property configures the system to generate and store daily aggregates of resource data in the resource aggregate daily table. |
com.snc.resource_management.max_dur_resource_finder |
It limits the duration in months for which resource details are visible in the Resource Finder, impacting how far ahead resources can be planned. |
com.snc.resource_management.number_of_records_to_fetch_at_a_time |
It sets the limit on how many records are retrieved in a single server call within the Resource Grid, defaulting to 30. |
com.snc.resource_management.number_of_users_to_fetch_in_finder_at_once |
It sets the maximum number of user records retrieved in a single call within the Resource Finder feature. |
com.snc.resource_management.plan.auto_async_threshold |
This property limits the number of daily resource allocation records handled synchronously, enhancing performance when the volume is high. |
com.snc.resource_management.plan.max_duration |
This property restricts the duration for resource plan creation, with a default value of 3660 days if not specified. |
com.snc.resource_management.run_state_changes_async |
This property determines whether resource management actions are processed asynchronously, improving performance during confirmation and allocation tasks. |
com.snc.samp.lifecycle.max_workers |
This property configures the limit on concurrent worker threads, impacting system performance and task processing efficiency. |
com.snc.schedule_loader.expire_cache_minutes |
This property determines the expiration time for cached schedules, defaulting to 720 minutes, after which unused schedules are invalidated. |
com.snc.schedule_loader.project_management.cache_years_after |
It specifies how many years into the future project management schedules are cached, impacting system memory usage. |
com.snc.schedule_loader.project_management.cache_years_before |
It sets the cache duration for project management schedules, impacting memory usage and performance. |
com.snc.schedule_loader.resource_management.cache_years_after |
It specifies how many years of resource management schedules are cached, impacting system memory usage. |
com.snc.schedule_loader.resource_management.cache_years_before |
It sets the cache duration for resource management schedules, impacting how far back historical data is retained. |
com.snc.sdlc.scrum.pp.default_sprint_length |
This property specifies the default number of days for a sprint when the length is not calculable, impacting sprint planning and execution. |
com.snc.sla.condition_class.caching.enabled |
This property enables or disables caching of SLA condition script instances during SLA processing, affecting how quickly conditions are evaluated. |
concurrent.dist.download |
This property limits the number of concurrent downloads to enhance system stability and performance. |
contract_compliance_check_job.batchSize |
It defines the number of records processed in each batch for the Contract compliance check job, optimizing the job's performance based on the specified batch size. |
diagnostics.condition.events |
This property defines the condition that triggers a flag for pending events based on their count, helping to manage system performance. |
diagnostics.condition.node.scheduler.is.running |
This property indicates the running status of a node's Scheduler, affecting task scheduling and execution. |
diagnostics.condition.node.scheduler.queue.length |
This property sets a condition to trigger alerts when a node's Schedule Queue Length exceeds the defined limit, which is greater than 10 by default. |
dp.job_sent_to_queue |
This boolean property controls the queuing of jobs for processing, impacting how tasks are handled within the system. |
event.limited.queues |
This property configures the queues that are restricted for event processing, impacting how events are managed within the system. |
evt_mgmt.connector_eventcollection.eccprobe_priority |
This property defines the priority for processing event connector probe messages in the ECC queue, influencing the order in which events are handled. |
evt_mgmt.connector_metriccollection.eccprobe_priority |
This property defines the priority of the metric connector probe in the ECC queue, affecting how quickly metrics are processed. |
evt_mgmt.em_extra_data_json.max_fetched_records |
This property limits the number of records fetched from the 'em_extra_data_json' table, impacting data processing efficiency. |
evt_mgmt.event_processing_stats_period |
This property configures the interval for the XMLStatsEm script to collect event processing statistics, allowing for performance monitoring and resource management. |
evt_mgmt.event_processor_enable_multi_node |
This property allows the system to process events across multiple nodes, enhancing performance in environments with high event volumes. |
evt_mgmt.event_processor_job_count |
This property configures the count of scheduled jobs dedicated to processing events, influencing the system's ability to handle event loads efficiently. |
evt_mgmt.event_rules.num_of_events_to_handle |
This property defines the limit on the number of events handled during event rules processing, impacting system performance and event management efficiency. |
evt_mgmt.events_processing_delay_sec |
It configures the delay time before processing events that are in a 'ready' state, ensuring that only older events are processed based on the specified delay. |
evt_mgmt.fetch_limit |
This property defines the integer limit for the number of events fetched by the event processor during each operation, influencing processing efficiency. |
evt_mgmt.impact_calculation.cleanup_age_seconds.em_alert_history |
This property specifies the duration for which alert history records are retained before being automatically cleaned up by scheduled jobs. |
evt_mgmt.impact_calculation.cleanup_age_seconds.em_impact_status |
This property specifies the time period after which records in the em_impact_status table are eligible for cleanup, with a default of 90 days. |
evt_mgmt.max_events_processing_per_job |
This property limits the number of events processed in a single job execution, helping to manage system load and performance. |
evt_mgmt.max_objs_in_alert_query |
This property determines how many events are processed simultaneously in each job, impacting the speed and efficiency of event management. |
evt_mgmt.plugin_activation.table_max_size |
This property customizes the threshold for activating the Event Management Performance Accelerator plugin based on the record count in specific tables. |
evt_mgmt.update_alert_restricted_fields_elapsed_time |
This property defines a 24-hour minimum interval for updating alerts related to identical events, helping to manage alert frequency. |
evt_mgmt.valid_processing_duration_of_event_rule |
This property defines the valid processing duration for events in event rules, influencing how quickly events are evaluated and acted upon. |
glide.ais.ha.refeed_backtrack_max_events |
This property limits the number of historical events considered during a refeed, impacting data accuracy and processing efficiency. |
glide.ais.ha.replication_delay_laxity |
This property sets the maximum allowed replication delay between active and passive AIS connections, impacting system failover capabilities. |
glide.ais.ha.write_mutex_expiry_time_minutes |
It configures the expiry time for write mutexes in minutes, influencing how long concurrent write operations are managed in the system. |
glide.ais.ha.write_mutex_spin_max |
This property defines the upper limit on spin attempts when trying to acquire a write mutex, impacting system performance during concurrent write operations. |
glide.ais.ha.write_mutex_spin_wait_time |
This property defines the spin wait time in milliseconds for acquiring a write mutex in high availability scenarios, influencing how threads manage resource contention. |
glide.ais.ingestion.batcher_queue_size |
This property defines the length of the ingestion batcher queue in terms of record count, impacting how many records can be processed simultaneously. |
glide.ais.monitor.event_queue_size_threshold |
This property defines the threshold for the event queue size, helping to manage system resource allocation and performance. |
glide.ais.monitor.queue_stats_records |
This property configures the integer value that determines how many queue statistics records are monitored, impacting system performance and data visibility. |
glide.analytics.cache.expiration.age.in.seconds |
This property defines the expiration time for cached analytics data in seconds, with a default value of 86400 seconds (24 hours). |
glide.analytics.queryservice.connection.timeout.ms |
This property configures the maximum time allowed for establishing a connection to the analytics query service before timing out. |
glide.analytics.queryservice.max.connections |
This property configures the upper limit for concurrent connections to the analytics query service, impacting system performance and resource allocation. |
glide.analytics.queryservice.socket.timeout.ms |
This property configures the duration for socket timeouts, impacting how long the system waits for a response during analytics queries. |
glide.awa.assignment.parallelization_claim_limit |
This property defines the maximum number of claimed work items a node can reserve, impacting workload distribution and processing efficiency. |
glide.cache.opt_out_unused_cache_removal_list |
This property defines a list of cache names that are exempt from being cleared during unused cache removal processes. |
glide.cache.provider.syscache_metric_retention_policy |
This property specifies the retention policy for metrics stored in the system cache, affecting how long these metrics are kept. |
glide.cache.provider.syscache_metrics |
This property defines the implementation class for the metrics cache, impacting how metrics data is stored and retrieved. |
glide.cache.record_change.storage.max_size.amb_processor_cache |
This property defines the maximum storage size, in megabytes, for the AMB processor cache, impacting how much data can be cached for record changes. |
glide.cache.scoped.private_cache_max_entries |
This property sets a cap on the maximum number of entries in scoped caches, helping manage memory usage effectively. |
glide.cache.size.TopicTypeCacheServiceImpl |
This property configures the maximum allowable cache size for topic types, ensuring efficient data retrieval and management. |
glide.cache.size.com.snc.sla.sla_def_sla_breakdown_cache |
This property defines the integer limit for the SLA breakdown cache size, impacting how SLA data is stored and retrieved. |
glide.cache.size.static_content_disk_cache |
This property configures the size limit for the static content disk cache, impacting how much static data can be stored for quick access. |
glide.cache.size.syscache_schedule |
This property directly controls the size of the schedule cache, impacting how many schedule entries can be stored. |
glide.cache.size.zz_all_terms_cache_yy |
This property configures the size limit for the all terms cache, impacting how many terms can be stored and retrieved efficiently. |
glide.cache.size.zz_all_terms_cache_yy.backup.@@snc_write_audit@@ |
This property specifies the backup value for the all terms cache, impacting how data is stored and retrieved in the cache. |
glide.cacheman.cache_pair_optimizations.enabled |
This property activates enhancements for cache pair management, which can lead to better data retrieval and reduced load times. |
glide.central_scheduler.enable |
This property activates the central scheduler, which manages the execution of scheduled jobs across the platform. |
glide.client.track_transaction_timings |
This property allows the server to log the duration of client transactions, aiding in performance analysis. |
glide.client_metrics.aggregation.enabled |
This property controls whether transaction aggregation is active for the sys_client_interaction table, impacting how client interaction data is processed and reported. |
glide.cluster.cache |
This property activates the synchronization of cache data among clustered nodes, ensuring data consistency. |
glide.cs.adapter.worker_cache_size |
This property sets the integer value for the size of the adapter worker cache, impacting how much data can be temporarily stored for processing. |
glide.cs.runtime.max_silent_fields |
This property defines the maximum number of silent fields allowed in the state machine to prevent infinite loops. |
glide.cs.worker.queue_length |
This property defines the upper limit for the number of messages that can be queued for processing, impacting system performance and message handling. |
glide.cs.worker.thread.timelimit.ms |
This property specifies the time limit for thread execution, defaulting to 10,000 milliseconds, which helps manage resource allocation and prevent long-running threads. |
glide.db.alter_large_table_threshold |
This property defines the maximum size limit for database tables that can be altered, impacting performance and resource allocation during such operations. |
glide.db.clone.schedule_clone_poll_minutes |
This property specifies the wait time in minutes between clone schedule service attempts, with a default of 30 minutes. |
glide.db.dm_job.enabled |
This property enables the DMJob framework, facilitating the parallel execution of jobs to enhance processing speed and resource utilization. |
glide.db.dsb.data_copy_processor.threads |
This property controls the number of concurrent data copy operations for tables in a sandbox environment, impacting setup efficiency. |
glide.db.first_pass_sys_id_list_size.max |
This property defines the limit for sys_ids in database queries, affecting how GlideRecord retrieves data when large lists are involved. |
glide.db.forced.chunk.threshold |
It defines the record count threshold above which chunking is enforced during deletions and updates, ensuring efficient handling of large datasets. |
glide.db.large.threshold |
This property determines the threshold for classifying tables as large, affecting how queries are executed for those tables. |
glide.db.oracle.ps.delete |
This property configures the system to utilize prepared statements for delete operations in Oracle, improving efficiency and reducing risks associated with SQL injection. |
glide.db.oracle.ps.insert |
This property configures the system to utilize prepared statements for executing insert operations in Oracle databases, improving efficiency and security. |
glide.db.oracle.ps.pool.size |
This property sets the number of prepared statements that can be cached per Oracle database connection, impacting query performance and resource utilization. |
glide.db.oracle.ps.query |
This property configures the system to utilize prepared statements for executing queries against Oracle databases, enhancing efficiency and security. |
glide.db.oracle.ps.update |
This property configures the system to utilize prepared statements for updates in Oracle, improving efficiency and reducing the risk of SQL injection. |
glide.db.pooler.connections.max |
This property defines the upper limit for concurrent database connections, impacting application performance and scalability. |
glide.db.rotation_validate_fields |
This property enables or disables the validation of fields when performing database rotation, impacting data consistency. |
glide.db.soft_join_cap |
This property limits the number of joins in database queries, impacting how the system constructs and executes those queries. |
glide.db.stats.threshold |
This property defines the maximum execution time for database queries to be logged as slow, aiding in performance monitoring. |
glide.dev_sandbox.dsb_db_copier_threads |
This property configures the number of concurrent threads for processing table hierarchies in a sandbox, affecting initialization speed. |
glide.discovery.file_discovery.sleeptime.windows |
It defines the pause time between processing batches of files during Windows file discovery, helping to control system load. |
glide.discovery.file_discovery.throttle.windows |
This property configures the file scanning limit for Windows, influencing how many files are processed before the system temporarily halts scanning. |
glide.discovery.max_concurrent_invocations_per_schedule |
It sets an integer limit on how many instances of the same Discovery schedule can run simultaneously, helping to manage system resources effectively. |
glide.hermes.consumer.cache.idle.time.max |
It defines the maximum idle time for a Hermes Consumer, ensuring that inactive consumers are closed to avoid resource leaks. |
glide.http.async.io_thread_count |
This property configures the number of IO threads available for asynchronous HTTP operations, impacting how efficiently requests are handled. |
glide.http.ecc.response_poller.loop_iteration.interval_ms |
This property configures the interval at which the ECC Queue checks for responses, impacting the responsiveness of the system to incoming messages. |
glide.http.expire.days |
This property specifies the number of days before static content expires in HTTP responses, allowing for control over content caching behavior. |
glide.http.response.get_body.limit.enabled |
This property enables a safeguard against OutOfMemoryExceptions by limiting the size of HTTP response bodies processed by the system. |
glide.hub.process.sync.jobs.inbound.process_maxtime |
This property limits the execution time of inbound scheduled jobs, helping to manage system performance and job efficiency. |
glide.hub.process.sync.jobs.outbound.process_maxtime |
This property defines the maximum execution time for outbound scheduled jobs, defaulting to 300 seconds. |
glide.hub.process_sync.inbound_queue.table_cleaner_batch_size |
This property configures the number of inbound queue entries deleted in each batch operation, impacting system performance during cleanup processes. |
glide.hub.process_sync.outbound_queue.ready.ttl.seconds |
This property sets the time-to-live for ready outbound records in seconds, impacting how long they are retained before being purged. |
glide.hub.process_sync.outbound_queue.table_cleaner_batch_size |
This property determines how many outbound queue entries are deleted in each batch operation, impacting system performance and data management. |
glide.invalid_query.returns_no_rows |
This property configures the behavior of queries across the instance, ensuring that invalid queries do not return any records. |
glide.job.eval.condition_script_outside_sandbox |
This property controls the evaluation of job condition scripts outside of the sandbox, with a default setting of false to enhance security. |
glide.legacy.transaction.use_legacy_semaphore_queue |
This property configures the queue mechanism for Semaphore pools, allowing the choice between a new balanced queue and an older sequential processing method. |
glide.oneapi.use.lazy.db.action |
This property configures the use of lazy database actions for OneAPI operations, allowing for asynchronous database writes to enhance performance. |
glide.performance_window.comparison.count |
This property defines the count of query executions used for evaluating performance within a specified window, impacting performance assessments. |
glide.performance_window.comparison.degradation |
This property defines the percentage threshold for acceptable degradation in query execution performance, helping to identify performance issues. |
glide.performance_window.comparison.improvement |
This property defines the minimum percentage improvement required for query execution performance comparisons to be considered significant. |
glide.platform_ml.artifact.cache_size |
This property defines the upper limit for the number of cached artifacts, influencing system performance and memory management. |
glide.platform_ml_di.doc_data_extractor.max_num_of_ocr_jobs |
This property limits the concurrent OCR jobs submitted by the document data extractor, impacting processing efficiency. |
glide.platform_ml_di.doc_data_extractor.max_num_of_pdf_jobs |
This property limits the concurrent submission of PDF jobs to enhance system performance and resource management. |
glide.platform_ml_di.doc_data_extractor.max_number_of_tasks_for_upgrade |
This property limits the number of tasks processed during an upgrade to optimize performance and resource allocation. |
glide.platform_ml_di.doc_data_extractor.max_tasks_processed_per_day |
This property defines the upper limit of tasks that can be processed daily on the instance, influencing task throughput and performance. |
glide.platform_ml_di.doc_data_extractor.prediction_server.ocr.max_limit |
This property limits the number of concurrent OCR requests to the prediction server, impacting how quickly documents can be processed. |
glide.platform_ml_di.doc_data_extractor.prediction_server.pdf.max_limit |
This property configures the maximum allowable PDF requests to the prediction server, impacting how many requests can be processed simultaneously. |
glide.processor.GlideServletUITransaction.process_concurrently_always |
This property ensures that Servlet UI Transaction requests are processed concurrently within the same HTTP session, enhancing the efficiency of user interactions. |
glide.processor.XMLHttpProcessor.process_concurrently_always |
This property configures the concurrent processing of XMLHttpProcessor requests within the same HTTP session, enhancing application performance. |
glide.processor.json.row_limit |
This property specifies the upper limit on the number of rows that can be returned in a JSON query response, with a default value of 10,000. |
glide.quota.manager.heartbeat |
This property determines how frequently the Quota Manager evaluates transactions against quota limits and logs status updates. |
glide.record_watcher.limited_updates_enabled |
This property enables or disables the discarding of record watcher updates to subscribers when the default semaphore queue reaches capacity. |
glide.render.cache.aggressive |
This property configures the render cache to retain entries until they naturally expire, rather than updating them with changes in underlying data. |
glide.render.cache.enable |
This property enables or disables the caching of the homepage render to optimize loading speed. |
glide.render.cache.max.age |
This property defines the time limit for how long cached render entries are retained, impacting cache efficiency and application responsiveness. |
glide.request_manager.cancel_other_transaction |
This boolean property determines whether the Request Manager can cancel previous transactions marked as sysparm_cancelable, affecting transaction management. |
glide.rrd.reader |
This property specifies whether RRDB data is read from the round_robin_database or the Clotho Server, depending on its value. |
glide.rrd.writer |
This property configures the backend storage for time series data, allowing data to be written to various databases based on the selected option. |
glide.scan.max_parallel_scans |
It defines the upper limit for concurrent instance scans, allowing administrators to control system resource usage during scan operations. |
glide.scan.parallel_scan_enabled |
This property determines whether instance scans can be executed in parallel, enhancing the speed of scan operations based on the configured maximum limit. |
glide.scan.process_check.time_out |
It defines the maximum execution time for a scan check, ensuring that checks are canceled if they exceed this limit. |
glide.scan.queue.enabled |
This property determines whether new scan requests can be queued when another scan is currently running, impacting the handling of concurrent scans. |
glide.scheduler.extra_workers.allowed_extra_per_node |
This property sets a limit on the number of additional scheduler workers that can run on each node, impacting task processing capacity. |
glide.scheduler.extra_workers.total_allowed_on_instance |
This property defines the maximum number of additional scheduler workers that can run on a ServiceNow instance, impacting task processing efficiency. |
glide.schedules.fifth |
This property specifies whether to select the last occurrence, the next occurrence in the following month, or to skip scheduling for that month when the fifth occurrence is requested. |
glide.schedules.repeat_nth |
This property determines whether a monthly schedule entry selects the nth week of a month or the nth day of the month for recurring events. |
glide.schedules.schedule_entry_max_span |
This property defines the maximum allowable span for schedule entries, with a default value of 50 years. |
glide.service_modeling.recomputation.max_replication_lag_allowed |
This property determines the maximum replication lag allowed before recomputation jobs are halted, with a default setting of one hour. |
glide.servlet.static_content.cdn_enabled |
This property determines whether static content is served through a CDN, enhancing delivery speed and efficiency. |
glide.servlet.thread.pool.queue_size.loanable_semaphore |
This property configures the queue size for loanable semaphores in the servlet thread pool, impacting how many requests can wait for processing. |
glide.session.max.concurrent.transactions |
This property defines the maximum number of concurrent transactions that can be processed in a single HTTP session, impacting system performance and user experience. |
glide.sys.activity_using_audit_direct |
This property enables the system to utilize the audit file directly when generating activity, potentially improving efficiency in data handling. |
glide.sys.domain.skip_domain_insert_businessrules |
This property configures whether business rules for domain inserts are executed based on the session domain or the newly created domain's hierarchy, impacting performance and behavior during data operations. |
glide.sys.schedulers |
This property sets the maximum number of schedulers available for task processing, impacting system performance and efficiency. |
glide.sys.sparse.update |
It enables physical database updates only for fields that have changed, minimizing write operations. |
glide.tpp.force_indexdescriptor_create |
This property, when set to true, ensures that index descriptors are created automatically, which can enhance query performance and data retrieval efficiency. |
glide.ts.private_pool |
It configures the system to utilize a separate database connection pool specifically for handling text queries, enhancing efficiency. |
glide.ts.query_mode |
It configures the method used for querying time series data, with 'rdbms' as the default setting. |
glide.ui.homepage.parallel |
This property configures the system to render home page elements simultaneously, enhancing user experience by reducing load times. |
glide.ui.homepage.parallelism |
This property determines how many threads can simultaneously render components on the home page, impacting load times and responsiveness. |
glide.ui.js_includes |
This property enables the bundling of JavaScript files to optimize loading efficiency and reduce the number of requests made to the server. |
glide.ui.list.record_watcher_throttle |
This property controls the interval at which record watchers refresh their data in the UI, impacting how quickly updates are reflected to users. |
glide.ui.max.transactions |
This property limits the number of concurrent transactions in the UI, helping to manage system resources effectively. |
glide.ui.mra.threshold |
This property determines the record count limit for asynchronous loading of related list entries, enhancing system responsiveness during data operations. |
glide.ui.performance_monitoring.enabled |
This property activates performance monitoring features specifically for the Classic Workspace, allowing for better analysis of workspace performance. |
glide.ui.performance_monitoring.interval |
This property configures the interval, in milliseconds, at which performance metrics are transmitted to the platform, influencing data collection frequency. |
glide.ui.response_time |
This property controls whether page response times are shown to users, providing insight into system performance. |
glide.ui.sysevent_queue_config_activity.fields |
This property specifies which fields are shown in the Queue Status activity formatter, impacting how job information is displayed to users. |
glide.ui.transaction.long_response.time |
This property configures the time delay before displaying the Transaction Cancel button for transactions that exceed a specified duration. |
glide.ui16.performance.monitoring.enabled |
This property controls whether performance monitoring is active for the Core UI, impacting data collection and analysis. |
glide.upgrade.preview.duration.multiplier |
This property adjusts the duration estimate for upgrades by applying a specified multiplier, allowing for more accurate planning. |
glide.ux.performance.monitoring.enabled |
This property controls whether performance monitoring is active, allowing for insights into system performance metrics. |
glide.uxf.js_server.onDemand.use_proxy |
This property configures the system to utilize proxies for lazy loading, enhancing the efficiency of resource management. |
glide.uxf.lib.batchingOptions.useDataBrokerSingleRequestStrategy |
This property enables batch streaming only when there is one or fewer data broker requests in the batch, enhancing performance management. |
glide.uxf.lib.performance.monitoring.enabled |
This property activates the client-side performance monitoring feature, allowing the system to collect and send performance data. |
glide.uxf.lib.performance.monitoring.interval |
This property defines the interval in milliseconds for persisting UXF interactions, with a default setting of 15 seconds. |
glide.uxf.lib.performance.monitoring.metric.level |
This property configures the metric level for performance instrumentation, allowing values from 1 to 5 to adjust the granularity of monitoring. |
glide.uxf.lib.performance.monitoring.network.latency.cache.ttl |
It sets the time-to-live for cached network latency data, triggering a new ping request if the cached data is older than the specified duration. |
glide.uxf.lib.ux.metrics.clear_interval |
This property configures the interval at which UX metrics are cleared from the browser's memory, impacting how long data is retained. |
glide.uxf.lib.ux.metrics.enabled |
This property controls whether usage and performance metrics are processed, impacting data availability for analysis. |
glide.uxf.minimum_content_client_cache.enabled |
This property activates the minimum content client cache, optimizing resource loading for applications built on the sn-canvas-core. |
glide.uxr.prefetch.limit.default |
This property defines the default integer limit for data prefetching, impacting how much data is loaded in advance for user interactions. |
glide.uxr.prefetch.limit.max |
This property defines the upper limit for prefetch requests, impacting how data is loaded in the user interface. |
glide.xlsx.multiplier |
This property determines the memory allocated for Excel imports by multiplying the file size with the specified multiplier value. |
hermes.metrics.quotalist |
This property specifies which quota metrics are tracked within the Hermes infrastructure, impacting performance monitoring and resource allocation. |
metric_schema_retention_hours |
This property specifies the number of hours that records in the sa_metric_schema_definition table are retained before deletion. |
mid.probe.wait.resources |
It enables MID Server Resource Reservation, allowing administrators to control probe execution based on resource availability, which can minimize the impact of Discovery on target systems. |
roi.processing.active |
This property controls the activation of the Processing ROI Schedule, ensuring that ROI calculations are performed as scheduled. |
sa.lookup_tables.exclusion_tables_for_limited_query |
This property specifies a comma-separated list of table names that are excluded from unlimited lookup queries, allowing for more controlled data retrieval. |
sa.lookup_tables.max_records_to_check |
This property limits the number of records checked in lookup queries to enhance performance and reduce load times. |
sa.lookup_tables.tables_for_limited_query |
This property limits lookup queries to specified tables, inheriting from the defined list, which by default includes cmdb_ci and cmdb_serial_number. |
sa.model_learner.maint_history_batch_size |
This property sets the batch size for storing historical maintenance event data, impacting how efficiently data is processed and stored. |
sa.qbs.batch_size |
This property sets the maximum number of query-based services processed in one batch update, impacting system efficiency during bulk operations. |
sa.service.batch_manual_service_population.max_batch_size |
This property defines the limit on the number of batch items processed by the identification engine during manual service updates. |
sa_analytics.rca.learner_probes |
This property configures the count of concurrent learner probes that the MID server will run, impacting data processing efficiency. |
sa_analytics.rca.mid_max_allowed_space |
This property defines the maximum allowed disk space usage percentage for the MID Server, triggering alerts when the limit is surpassed. |
sa_analytics.rca.purge_probes |
This property configures the maximum number of concurrent purge probes allowed on the MID server, impacting data management efficiency. |
sa_analytics.rca.query_probes |
This property configures the maximum number of parallel query probes that can be run on the MID server, impacting data processing efficiency. |
sm.flapper_strategy_data_table.size_limit |
This property defines the upper limit for the number of entries in the sm_flapper_strategy_data table, impacting data management and system performance. |
sn_adv_apptmnt.retention_days_before_purging |
This property determines how long appointment data is kept before it is purged from the system, with a default retention period of 90 days. |
sn_agent.auto_upgrade.retry_limit |
This property specifies how many times the system will attempt to upgrade an agent before permanently skipping it, impacting both high-volume and selective upgrades. |
sn_ap_apm.exception.engine.max_parallel_thread_count |
This property defines the maximum number of parallel threads that the exception engine scheduler can utilize to process invoice exceptions. |
sn_ap_apm.exception.engine.scheduler_cool_off_period |
This property defines the interval in minutes that the exception engine scheduler waits before checking an invoice again for exceptions, impacting processing efficiency. |
sn_appclient.enable_app_manager_cache |
This property determines whether the application manager cache is enabled, enhancing the efficiency of application management operations. |
sn_appclient.enable_app_manager_checksums_cache |
It configures the caching behavior for app synchronization, enhancing efficiency by storing data temporarily. |
sn_appclient.scheduled_jobs_config |
This property configures the settings for automated polling and scheduling of application upgrades, including enabling or disabling specific checks and defining their operational hours. |
sn_appclient.store.outbound.http.request.limit.enabled |
This property determines if the instance will adhere to the outbound HTTP request limits set by the store, impacting how requests are processed. |
sn_apptmnt_booking.DisableMaxApptLimitForUsersList |
It stores a list of user sys_ids exempt from the daily maximum appointment limit, enabling them to book unlimited appointments. |
sn_apptmnt_booking.max_appointments_returned |
This property limits the number of appointment slots shown to users during the booking process, with a default value of 100. |
sn_apptmnt_booking.use_read_replica_from_ui |
It determines whether to utilize a read replica database for fetching appointment slots from the sn_apptmnt_booking_appointment_booking table when triggered from the UI. |
sn_apptmnt_booking.user_max_new_appointments_daily |
It restricts the number of new appointments a user can book each day to ensure balanced usage of the appointment booking system. |
sn_at_rpt.activity_timer_aggregator_last_successful_run |
This property defines the last successful execution date for the activity timer aggregator, impacting the reporting of activity data. |
sn_atf.custom_ui.wait.dom_mutation_only_interval_ms |
This property specifies the interval to wait after all non-DOM mutation activities are finished, allowing for smoother UI updates. |
sn_atf.headless.request_timeout_sec |
This property specifies the maximum time allowed for a request to Docker before it times out, defaulting to 200 seconds. |
sn_atf.headless.timeout_mins |
This property defines the maximum duration a headless browser can run before timing out, with a default value of 1440 minutes. |
sn_atf.performance.safe_triggers |
This property maintains a list of sys_trigger IDs that are exempt from being deactivated during ATF performance runs, ensuring essential functionality is preserved. |
sn_atf.runner.heartbeat.timeout |
This property defines the timeout period for receiving a heartbeat signal from the test runner, affecting its online status. |
sn_atf.runner.offline_retention.timeout |
This property defines the number of days an offline test runner can remain inactive before being removed from the system. |
sn_atf.schedule.enabled |
This property enables the execution of automated test suites on a scheduled basis, provided that the related test execution property is also enabled. |
sn_atf.scheduler.enabled |
This property enables or disables the ATFScheduler, affecting how automated tests are scheduled within the ServiceNow environment. |
sn_atf.scheduler.max_parallelism |
This property configures the parallel test execution limit for the Automated Test Framework, allowing the ATF engine to optimize performance based on the specified value or default calculation. |
sn_atf_tg.cloud_runner.height |
This property configures the vertical dimension of screenshots taken during automated testing in the cloud runner environment. |
sn_atf_tg.cloud_runner.width |
This property configures the width of screenshots taken by the cloud runner, impacting how visual data is presented. |
sn_atf_tg.disable_cloud_screenshots |
This property allows the use of legacy screenshots during automated testing in the cloud environment. |
sn_atf_tg.num_licensed_cloud_runners |
This property defines the total count of licensed cloud runners that can be utilized in the instance for automation testing. |
sn_build_agent.implementation_job_monitor.enabled |
This property enables or disables the monitoring of implementation jobs without affecting the scheduled job's trigger. |
sn_build_agent.implementation_job_monitor.max_per_run |
This property limits the number of work items the watchdog processes in one run, impacting script execution duration and efficiency. |
sn_build_agent.implementation_job_monitor.stall_threshold_sec |
This property sets the time limit for inactivity in a work item's conversation, triggering a status change if exceeded. |
sn_build_agent.tool.execution.timeouts |
This property specifies the maximum execution time for tools used by the Build Agent, allowing for control over how long each tool can run before timing out. |
sn_ca.add_users.max_run_time |
This property limits the execution time of the scheduled job responsible for updating campaign audiences, ensuring it finishes processing the current item within the specified duration. |
sn_ca.campaign.max_run_time |
It limits the execution time of scheduled jobs related to Content Experiences, ensuring they finish processing current items after the specified time has elapsed. |
sn_ca.notification.max_run_time |
This property limits the execution time of scheduled jobs for sending notifications, ensuring they finish processing the current item without starting new tasks. |
sn_ca.purging.max_run_time |
This property defines the maximum run time for the Content Experiences scheduled job, limiting it to a specified number of seconds. |
sn_ca.purging.max_users_per_job |
This property limits the number of users purged during each execution of the purge job, with a default setting of 25,000 users. |
sn_ca.state_management.max_records_update |
This property limits the number of records updated per job run to enhance processing efficiency and prevent system overload. |
sn_ca.state_management.max_run_time |
This property defines the maximum run time for scheduled jobs related to content state management, influencing how quickly campaigns can transition between states. |
sn_ca.task.max_records_create |
This property limits the number of records created by the Content Experiences scheduled job, impacting how efficiently large batches are processed. |
sn_ca.task.max_run_time |
This property limits the execution time of scheduled jobs, allowing them to finish current tasks without picking up new work once the time limit is reached. |
sn_ca.user_deactivation.max_run_time |
This property defines the maximum duration for the Content Experiences scheduled job that deactivates users, defaulting to 300 seconds. |
sn_ca.user_deactivation.max_users_per_job |
This property limits the number of users deactivated per job run to optimize performance during scheduled deactivation tasks. |
sn_cd.audience.autocount_timeout |
This property defines the timeout duration for the automatic audience count process, impacting how quickly audience records are configured. |
sn_cd.audience_count_threshold |
This property defines the user count limit that triggers the portal's transition to performance mode, helping manage system resources effectively. |
sn_cd.content_community.max_posts |
This property limits the number of forum posts processed in a single Content Publishing job, impacting how quickly posts are published. |
sn_cd.high_performance_event_buffer |
This property configures the lead time in minutes for initiating high-performance events within the content publishing application. |
sn_cd.notification.event_stagger |
This property specifies the delay between events when a scheduled job runs, allowing for better processing of notifications. |
sn_cd.notification.max_events |
It limits the number of events processed during each scheduled job run to optimize performance and resource usage. |
sn_cd.todo.event_stagger |
It configures the delay between events in the Content Publishing application, ensuring that events are staggered to optimize processing time. |
sn_cd.todo.max_events |
It limits the number of events queued per scheduled job run to optimize performance and resource usage. |
sn_cd.todo.max_run_time |
This property defines the maximum run time for scheduled jobs that create to-do items, impacting how long these jobs can process before being terminated. |
sn_ci_analytics.ca.job_max_conversation_count |
This property limits the number of conversations handled per job in the Conversational Analytics application, helping to manage system load. |
sn_ci_analytics.on_hold_conversations_wait_time |
This property defines the wait time in milliseconds for the ETL process to handle 'On Hold' conversations, impacting data availability. |
sn_cld_intg_aws.AWS_METRICBASE_DELETION_CHUNK_SIZE |
This property sets the chunk size for deleting metric base records in AWS integrations, impacting the efficiency of deletion operations. |
sn_cld_intg_aws.max_unprocessed_records_for_ci_placement |
It limits the number of records processed in one batch during the CI Placement from AWS billing data, impacting data handling efficiency. |
sn_cld_intg_aws.min_unprocessed_records_for_ci_placement |
It defines the minimum batch size of records for CI Placement, impacting how data is processed from AWS billing. |
sn_cld_intg_azure.auto_pause_interval |
This property configures the interval in minutes for automatically pausing Azure cloud integrations when they are not in use. |
sn_cld_intg_core.ci_placement_threads_number |
This property configures the integer value representing the number of threads allocated for CI placement during cloud integration processes. |
sn_cld_intg_core.cloudinsights.executionmonitor.spec.pollsec |
This property configures the polling frequency, in seconds, for monitoring execution status within the Cloud Integrations Core application. |
sn_cld_intg_core.flow_launcher.poll_duration |
This property defines the interval at which the flow launcher polls for updates, influencing the speed of integration processes. |
sn_cld_intg_core.hierarchical_flow_launcher.poll_duration |
This property sets the interval for polling updates in the hierarchical flow launcher, impacting how frequently the system retrieves new data. |
sn_cld_intg_core.max_parallel_tasks |
This property configures the limit on concurrent tasks for cloud integrations, impacting processing efficiency and resource utilization. |
sn_clin.max_parallel_tasks |
This property defines the limit on concurrent task execution, impacting system performance and efficiency. |
sn_clin_core.bh_recom_max_chunk_size |
This property defines the maximum number of records in each chunk for workload generation related to rightsizing recommendations, influencing the efficiency of data processing. |
sn_clin_core.bh_recom_num_chunks_per_workload |
This property sets the number of chunks per workload, influencing the total records processed for generating rightsizing recommendations. |
sn_clin_core.budget_status_interval |
This property defines the time interval in milliseconds for checking the status of active budgets, influencing the enabling and disabling of budget reapplication. |
sn_clin_core.budget_workload_batch_size |
This property configures the batch size for budget workload processing, impacting how efficiently threads handle data. |
sn_clin_core.max_days_to_process |
This property limits the billing data processing to a specified number of days, with a default of 31 days. |
sn_clin_core.max_records_to_process |
This property defines the upper limit for the number of billing records processed simultaneously, impacting system performance and efficiency. |
sn_clin_core.report_status_interval |
This property configures the frequency at which the system checks for updates on policy re-evaluations, impacting how quickly changes are reflected. |
sn_cmdb_ws.insight.category.disable_after_failure |
This property sets the threshold for consecutive job failures that trigger automatic disabling of scheduled jobs in the CMDB. |
sn_cmp.capi_cache_size |
This property defines the maximum size of the LRU cache for CAPI objects, impacting how many objects can be stored during cloud operations. |
sn_cmp.cloud_event.parallel_scheduler_count |
This property configures the parallel execution count of Cloud Event Scheduler jobs, allowing for improved event processing efficiency. |
sn_cmp_terraform.max_req_flow_count |
This property limits the number of concurrent request flows that can be processed, helping to manage system load and performance. |
sn_communities.content.views.count.limit |
This property defines the cap on content page views per session, influencing user interaction and content accessibility in the Communities application. |
sn_communities.content.views.time.limit |
This property defines the duration, in seconds, that limits the number of content views a user can have in a session, working in conjunction with the views count limit. |
sn_communities.content_list.initial_fetch_size_multiple |
This property configures the multiplier for the initial fetch size of the content list in the Communities application, enhancing loading efficiency. |
sn_communities.enable_dynamic_application_cache |
This property activates the dynamic application cache, enhancing the efficiency of data retrieval for community users by utilizing Java-based caching mechanisms. |
sn_communities.enable_session_cache |
This property enables or disables session caching for user permissions in the Community Application, affecting how quickly permission changes are reflected for users. |
sn_csm_case_digest.publish.batch_size |
This property sets the batch size for publishing child case PCR records, impacting how many records are processed together. |
sn_data_registry.max_records_to_be_verified |
This property defines the upper limit of records checked for readability, impacting data validation processes. |
sn_devops.bulk_flow_timeout |
This property defines the timeout limit for bulk flow operations, defaulting to 60,000 milliseconds, which can impact data processing efficiency. |
sn_devops.cascade_delete_threshold |
This property defines the limit for cascading deletions in the DevOps Data Model, ensuring that operations do not exceed the specified threshold. |
sn_devops.discover.request.claim.limit |
This property limits the number of discover requests processed in a single job run, impacting the efficiency of the DevOps Data Model. |
sn_devops.enable_metric |
This property toggles the logging of DevOps metrics, impacting how performance data is captured and reported. |
sn_devops.flow.cap.per.node |
This property defines the cap on concurrent DevOps flows per node, influencing system resource allocation and flow management. |
sn_devops.flow.context.count.cache.update.interval |
This property defines the interval, in seconds, for refreshing the flow context count stored in the cache, impacting data accuracy and system responsiveness. |
sn_devops.gcf_event_last_timestamp_for_flow_limit |
This property stores the timestamp of the last GCF event triggered when active flow executions surpass the specified limit, aiding in flow management. |
sn_disco_workspace.taskLimitKanbanBoard |
This property controls the upper limit of cards shown on the Kanban board in the Discovery Admin Workspace. |
sn_dpm.kpi_group.max_parent_kpis |
This property defines the upper limit for the number of parent KPIs that can be included in a KPI group, impacting how KPIs are organized and reported. |
sn_dpm.kpi_group.max_supporting_kpis |
This property limits the number of supporting KPIs for a parent KPI in the Digital Portfolio Management application, ensuring manageable data relationships. |
sn_dpr.max_template_duration |
This property defines the upper limit on the number of days allowed for a release template, affecting how phases can be structured within the template. |
sn_dpr.multi_product.included_products_limit |
This property defines the upper limit on the number of products that can be added as included products in a multi-product release, applicable only when independent releases are allowed. |
sn_em_arm.alert_management.num_of_jobs |
It specifies how many Alert Management processes are allowed to execute simultaneously, with a default value of 2. |
sn_em_connector.eventdata_closedevent_interval |
This property specifies the number of seconds that closed events are retained in the sn_em_connector_event_data table, impacting data management for alerts. |
sn_em_connector.eventdata_openevent_interval |
This property configures the duration for which open events are kept in the Event Management Connectors system before they are closed automatically. |
sn_em_connector.il_metric.overview.data_refresh_interval |
This property configures the interval at which the overview page data for the metric connector is refreshed, with a default setting of 60 seconds. |
sn_grc.execute_indicator_next_actions_async |
This boolean property determines whether pending actions are executed asynchronously using custom queues or processed synchronously with the default queue. |
sn_grc.grouped_questions_limit |
This property defines the upper limit of questions that can be included in a grouped assessment, impacting how attestations and risk assessments are consolidated. |
sn_grc.indicator_max_events |
It limits the number of indicator events fired in a scheduled run, adjusting the batch size if the total exceeds this maximum. |
sn_grc.indicator_min_batch_size |
This property defines the minimum batch size for running indicators, impacting how many indicators are processed together in a single operation. |
sn_grc.item_generation_max_records |
This property configures the upper limit for the number of records processed in bulk item generation, impacting system performance during large operations. |
sn_grc.item_generation_stale_action_threshold |
This property defines the duration after which a running item generation action is reset to prevent queue blockage. |
sn_grc.max_open_indicator_tasks |
This property defines the upper limit for active indicator tasks in the GRC application, impacting system performance when exceeded. |
sn_grc.max_supporting_data_records_to_process |
This property limits the number of records processed by the supporting data collection job to enhance performance and manage resource usage effectively. |
sn_grc.process_indicator_supporting_data_async |
This property configures the system to collect supporting data asynchronously, improving performance by utilizing custom queues for data processing. |
sn_grc.supporting_data_percentage_max_records_limit |
This property establishes an upper limit on the number of records collected during the supporting data collection job for indicators that utilize percentage sampling. |
sn_grc.user_hierarchy_sync_frequency |
This property sets the frequency for recalculating the user hierarchy in the GRC application, allowing for adjustments to daily, weekly, or monthly intervals. |
sn_grc_metric.metric_data_task_schedule |
This property defines the schedule for due date calculations of metric data tasks within the GRC: Metrics application. |
sn_grc_workspace.use_optimized_work_queue_experience |
This property enables an optimized experience for the Work Queue by improving performance through preloading and faster data retrieval. |
sn_hr_core.cache.hrcriteria.ttl |
It configures the duration for which HR Criteria cache entries remain valid before being refreshed or removed. |
sn_hr_core.flow_context_cleaner_event_delay |
This property configures the delay time between iterations of scheduled event updates in the Human Resources Core application. |
sn_hr_core.flow_context_cleaner_query_limit |
This property limits the number of records processed in each cleaning iteration for flow contexts, impacting the efficiency of scheduled cleanups. |
sn_hr_core.hr_criteria.optimize |
This property, when set to true, enhances the efficiency of evaluating HR Criteria, potentially speeding up related processes. |
sn_hr_core.profile.max.tries |
This property defines the threshold for retries before the application stops attempting to create a user, helping to prevent excessive resource use. |
sn_hr_core.restrict_query.limit_inactive |
This property limits access to HR cases based on the number of months since the last update, with a default setting of 12 months. |
sn_hr_core.userSelectionCriteriaCountLimit |
This property defines the integer limit for user selection criteria in the HR Core application, impacting how many criteria can be handled simultaneously. |
sn_hr_ef.purge_stride_length |
This property determines the interval at which purge dates for employee documents are recalculated, impacting document retention management. |
sn_hr_le.activity_set_launcher_timeout |
This property specifies the duration, in milliseconds, that the HR Activity Set launcher will wait before timing out. |
sn_instance_clone.setup.timeout.mif |
This property defines the maximum allowable time for the configuration of MIF instances before marking the setup as failed. |
sn_interview_temp.template_limit |
This property configures the limit on the number of interview question templates loaded at once, with a maximum value of 30 and a default of 20. |
sn_invst_pln.baseline_prefix |
This property specifies the string prefix used for naming baselines created through scheduled jobs in the Financials Core application. |
sn_itom_integ_app.evt_mgmt_tag_suggestion_max_alert_scan_per_instance |
It limits the number of alerts considered for tag suggestions, impacting how effectively tags are generated based on alert data. |
sn_itom_integ_app.evt_mgmt_tag_suggestion_max_scan_time_per_connector |
It defines the time limit for connectors to process alerts and generate tag suggestions, impacting the efficiency of alert management. |
sn_itom_integ_app.overview_page_data_input_stats_auto_refresh_interval_seconds |
It configures the frequency of auto-refresh for data input stats displayed on the overview page. |
sn_itom_licensing.domain_separation_enabled_date |
It sets the date for domain separation in ITOM licensing, ensuring average CI counts are computed correctly rather than using a standard 90-day window. |
sn_itom_licensing.itom_estimator_category_su_ratios_json |
This property provides a JSON string that specifies the service unit ratios for different ITOM categories, influencing licensing estimations. |
sn_itom_licensing.performance.config.bulksize |
This property configures the number of records processed in bulk when handling store app data, impacting performance during data operations. |
sn_itom_licensing.service_operation_bundles |
This property specifies the string values representing bundles relevant to Service Operations calculations, impacting licensing and operational assessments. |
sn_itom_pattern.acp_event_queue_batchsize_per_node |
This property defines the batch size for ACP changes added to the event queue per active node, impacting how changes are processed. |
sn_itom_pattern.acp_processing_time_range_hours |
This property defines the duration for which ACP processes data, influencing how quickly updates are reflected in service mapping. |
sn_itom_pattern.auto_openstack_max_runtime |
This property defines the maximum duration for scheduled tasks in Discovery and Service Mapping Patterns, ensuring they do not exceed 24 hours. |
sn_itom_pattern.auto_openstack_monthly_runon |
This property defines the day of the month on which a monthly scheduled task will execute, with valid options ranging from 1 to 31. |
sn_itom_pattern.auto_openstack_runtime |
This property configures the start time for scheduled operations, allowing for precise timing instead of relying on the default dynamic setting. |
sn_itom_pattern.auto_openstack_runtype |
This property specifies whether automated tasks run daily, weekly, or monthly, impacting the scheduling of Discovery and Service Mapping operations. |
sn_itom_pattern.auto_openstack_schedule_batch_delay |
This property sets the interval, in seconds, between consecutive batch executions for OpenStack scheduling. |
sn_itom_pattern.auto_openstack_weekly_runon |
This property determines which day of the week a scheduled task will run when the run type is set to weekly. |
sn_itom_pattern.container_batch_size |
This property defines the batch size for processing containers in Discovery and Service Mapping, impacting the efficiency of these operations. |
sn_itom_pattern.container_image_batch_size |
This property defines the number of Docker images processed in a single scan batch, impacting the efficiency of image scanning operations. |
sn_itom_pattern.k8s_batch_count |
This property defines how many schedules are executed in a single batch during Kubernetes discovery and service mapping. |
sn_itom_pattern.k8s_current_count |
This property defines the integer value representing the number of schedules processed in one batch during discovery and service mapping. |
sn_itsm_dpm.po_mining.run_frequency |
This property determines how often the process mining remine job is scheduled to run, defaulting to every 7 days. |
sn_nb_action.async_ra_timeout |
This property defines the maximum time allowed for an asynchronous recommended action to complete, helping to prevent prolonged execution times. |
sn_nb_action.ra_processor_number_of_queues |
This property configures the number of queues used for processing recommended actions, influencing how tasks are managed and executed. |
sn_nxui_framework.metricsMarkPruningInterval |
This property defines the interval, in milliseconds, for pruning marks that are no longer needed in the UI Framework. |
sn_nxui_framework.performance.cache.graphql.capacity |
This property defines the maximum number of entries in the LRU cache for caching GraphQL requests on the client side, enhancing performance and efficiency. |
sn_nxui_framework.performance.cache.graphql.enabled |
This property controls whether client-side caching for GraphQL requests is active, impacting response times and resource usage. |
sn_nxui_framework.performance.cache.graphql.max_persist |
It defines the duration for which GraphQL responses are cached before they expire, impacting load times and server performance. |
sn_nxui_framework.performance.cache.http.capacity |
This property defines the maximum number of entries in the LRU cache for HTTP requests, influencing caching efficiency and application responsiveness. |
sn_nxui_framework.performance.cache.http.delay |
It specifies the wait time in seconds for HTTP requests to be refetched, impacting the responsiveness of the UI Framework. |
sn_nxui_framework.performance.cache.http.enabled |
This property controls whether client-side HTTP requests are cached, impacting load times and resource usage in the UI Framework on Next Experience. |
sn_nxui_framework.performance.cache.http.max_persist |
This property defines the maximum time, in minutes, that HTTP cached queries are stored before being discarded. |
sn_nxui_framework.performance.memoize.snabbdom.prop.parts |
It controls whether Snabbdom property parsing uses memoization to enhance performance by caching results. |
sn_nxui_framework.performance.metrics.element.config.enabled |
This property controls whether client metrics configuration is active at the element level, impacting performance tracking. |
sn_nxui_framework.performance.page.opt.out.property.deep.compare |
This property disables the global deep comparison for specific pages, enhancing performance by preventing unnecessary checks. |
sn_nxui_framework.performance.page.opt.out.state.deep.compare |
This property configures which pages can opt-out of the global state deep comparison, impacting how state changes are tracked and compared. |
sn_nxui_framework.performance.property.deep.compare.enabled |
This property determines whether deep comparisons are performed when updating properties, impacting the efficiency of property management. |
sn_nxui_framework.performance.scheduler.queue.counts.enabled |
It controls whether scheduler queue counts are gathered, impacting performance monitoring capabilities. |
sn_nxui_framework.performance.scheduler.stats.enabled |
This property controls whether scheduler statistics are gathered, which can aid in performance analysis. |
sn_nxui_framework.performance.telemetry.marking.enabled |
This property controls whether performance marking is enabled, allowing for detailed performance metrics to be collected. |
sn_nxui_framework.performance.telemetry.window.top.enabled |
This boolean property determines whether window.top is disabled, impacting how the UI Framework interacts with parent frames. |
sn_nxui_framework.scheduler.unchained.defer.off |
This property controls whether unchained scheduler execution is turned off when not visible, impacting the performance of chained timers. |
sn_pa_designer.data_retention_policy |
This property specifies the delay in days before archiving sys_pd_context records after they reach terminal states like COMPLETE, CANCELLED, or SKIPPED. |
sn_pa_designer.enableDataRetentionFeatures |
This property enables or disables features for archiving terminal sys_pd_context data and automating the archiving process according to a defined retention policy. |
sn_publications.max_worker_per_user |
This property limits the number of simultaneous file upload processes a user can initiate for recipient lists, impacting upload efficiency. |
sn_sec_cmn.background_job_max_concurrency |
This property directly controls the concurrency level of background job processing, allowing for adjustments based on system capacity and job types. |
sn_sensitive_data.com.glide.cs.sensitive_data.regex_timeout |
This property defines the maximum time allowed for regex matching operations, with a configurable range from 0 to 10000 milliseconds. |
sn_shop.category_pref_supplier_refresh_interval |
This property defines the interval for refreshing the category and preferred supplier cache, impacting how quickly updates are reflected in the system. |
sn_shop.credit.allocation.batchsize |
It sets the batch size for processing employee records during credit allocation, impacting the efficiency of data handling in the Source-to-Pay process. |
sn_shop.spend.sla.due.days |
This property determines the number of days before a task's due date when a yellow highlight is displayed, indicating that action may be needed. |
sn_shop.supplier.cache.refresh.interval |
This property defines the interval for refreshing the supplier cache, impacting how quickly updates are reflected in the system. |
sn_sm_scoped_app.unified_services_recalculation_schedule_batch_size |
It defines the batch size for processing services in the Unified Service scheduled job, impacting execution efficiency. |
sn_sow_alert_rules.debounce_grouping_rendering.interval_sec |
This property configures the debounce interval for grouping alerts, affecting how frequently alerts are rendered in the Service Operations Workspace. |
sn_sow_exp_app.enable_link_view_cache |
This property controls whether the express list link view API response is cached, enhancing response times for users accessing the Service Operations Workspace. |
sn_sow_exp_app.evt_mgmt.facet.max_returned_records |
This property defines the maximum number of records that can be returned by a facet query, impacting data retrieval efficiency. |
sn_sow_exp_app.view_user_mapping.user_grmember_processing_delay |
It defines the delay time for processing updates related to user group memberships, impacting how quickly changes are reflected in the system. |
sn_uxa_req_manager.cache.expiration_time |
This property defines the cache expiration time in seconds for the User Experience Analytics application, with a default of 7200 seconds. |
sn_wdf_token.job.aggregate.lookbackDays |
This property sets the lookback period in days for the tokenization job to check and recalculate results, with a default of 5 days. |
sn_wsd_core.dxf.rebuild_cache.max_floors |
This property limits the number of floors included in the entity cache, impacting data retrieval efficiency. |
sn_wsd_core.max_buildings_delete |
It limits the number of buildings deleted in a single execution of the scheduled job, ensuring controlled data management. |
sn_wsd_core.max_spaces_delete |
This property limits the number of spaces deleted in a single execution of the scheduled job for deleting workplace locations, helping to control system performance during bulk operations. |
srm_service_metrics_config_group |
This property sets the configuration group identifier used for managing service metrics in the Service Operations Workspace. |
taxonomy.topic.cache_size |
This property configures the size of the cache for topic entries, impacting how quickly topics can be retrieved and displayed. |
taxonomy.topic.image_cache_size |
This property defines the size limit for the image cache in the taxonomy module, impacting how images are stored and retrieved. |
use_accounts_private_cache |
This property configures the caching method for accounts accessible to logged-in users, opting for a private cache when enabled. |
user.role.history.abort.sync.if.no.progress.minutes |
This property determines the maximum duration in minutes for which a sync can run without progress before being aborted, with a default setting of 180 minutes. |
user.role.history.job.batch.size |
This property specifies the maximum number of parallel jobs allowed for processing user role history, enhancing sync efficiency. |
user.role.history.max.records.per.task.if.processing.multiple.roles |
It defines the upper limit of records processed per sync task for multiple roles, with a minimum of 100,000 and a maximum of 500,000 records. |
user.role.history.processing.mode |
This property configures the processing mode for user role history, allowing either SEQUENTIAL or PARALLEL execution. |
user.role.history.record.process.size |
This property defines the upper limit of records that can be processed during a sync job, ensuring efficient data handling within specified thresholds. |
user.role.history.sync.job.timeout.in.days |
This property defines the timeout duration for the user role history sync job, ensuring it completes within a specified range of 1 to 5 days. |
user.role.history.sync.refresh.window.in.days |
This property defines the frequency of the refresh job that syncs user roles and audit records, with a default interval of 90 days. |