--- sourceDocument: Australia Impact sourceDocumentLink: https://www.servicenow.com/docs/r/impact Release : - australia ft:locale : - en-US ft:publication_title : - Australia Impact ft:clusterId : - ipact bundleId : - ipact --- # Configure Scan Engine parameters # Configure Scan Engine parameters {#ariaid-title1} * Release version: Australia * * Updated June 11, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Configure the primary scanning capabilities and configuration options for scheduled, on-demand, and real-time scans. ## Before you begin Review these properties before you [Run your first scan with the Scan Engine](https://www.servicenow.com/docs/Ug3wL8kV1lhvNcFR~h4qhg "An initial full Scan Engine completion is required to set a baseline from a series of tasks performed that tune the instance environment to complete future scans quickly and efficiently.") or to make changes to Scan Engine behavior. Role required: scan_engine_admin and Impact _admin ## Procedure 1. Navigate to ALLImpactConfigurationScan Engine Properties. 2. Select Activate Scan Engine to ensure the Scan Engine runs against your instance. 3. Select Run Scheduled Scan to schedule nightly, weekly, or monthly scans and configure these options. {#configure-scan-engine-properties__table_rs4_qpx_2hc__entry__2} | Field | Description | |-|-| | Run | Daily, Weekly, or Monthly scheduled scan run times. | | Day of Week | The day of the week on which to run weekly scans. | | Day of Month | The day of the month on which to run monthly scans. | | Time Zone | Your time zone. | | Time | * Field type = `glide_utc_time` * The time the scan should begin in 24-hour format (HH:MM:SS). {#configure-scan-engine-properties__ul_x5q_rmc_jhc} | [Table 1. Schedule options] {#configure-scan-engine-properties__table_rs4_qpx_2hc} 4. Configure scan scope and finding tracking configuration settings. {#configure-scan-engine-properties__table_a4y_xpx_2hc__entry__2} | Field | Description | |-|-| | Scan Non-Configuration Records | Includes non-configuration tables (which do not extend `sys_metadata`) in the scan. | | Scan Read-Only Records | * Includes read-only records in the scan. * scan_read_only: Default: `true`. * Read-only records are scanned by default. {#configure-scan-engine-properties__ul_tym_kmc_jhc} | | Track Resolved Findings | Logs any resolved findings as part of the scan and includes them in the View Resolved Findings module of the dashboard. | | Scan Findings Limit | * scan_findings_limit * The maximum number of findings that can be generated for each definition during a scan. * The limit is applied per applicable table. For example, if the limit is set to 100, a maximum of 100 findings will be generated for each applicable table. * Prevents excessive or redundant findings and optimizes scan performance. {#configure-scan-engine-properties__ul_khc_fqx_2hc} | | Custom Workday | By default, technical debt is calculated as a 24-hour day, which allows you to specify a number of hours for a workday. For example, developer workdays can be set to 8 hours instead of 24. Note: This is used to calculate various metrics that appear in the Analytics Dashboards. | | Average hourly rate of development | This figure calculates the cost of technical debt that displays on your dashboard by multiplying it by the estimated time to resolve each finding in the system. | | Batch Record Size | * full_scan_batch_size * Default: 50,000 records. * Specifies the maximum number of records allowed to be analyzed in a single batch scan for an applicable table. * This value does not limit the total number of records that can be scanned. When a table's record count exceeds this threshold (50,000), the table is assigned to its own dedicated batch during scan processing to optimize performance. * This value determines when an applicable table warrants its own batch during scans. Note: This is a read-only system property that cannot be modified through the UI. {#configure-scan-engine-properties__ul_nrm_mnc_jhc} | | Scheduled Scan Logging Frequency | * Default: `false` * Leave blank to disable verbose logging. When set, logs scan progress after processing the specified number of records {#configure-scan-engine-properties__ul_fdl_vsc_jhc} | | Days of scan finding histories to keep | * keep_days_finding_history * Sets the retention period for finding history records. Note: This controls how long historical scan data is retained, not the findings themselves.The default value is 30 days. {#configure-scan-engine-properties__ul_r5l_j4c_jhc} | | Include review findings in technical debt | Displays findings on the dashboard where the level of the rule is equal to Review. | | Enable instance specific definitions | * instance_specific_definitions * Select to restrict scan definitions to run only on designated instances. * When disabled, all active definitions run on all instances. * When enabled without matching instances: * If the *sn_se_my_sn_instances**table is empty, all definitions run (system assumes feature is not in use)* * If the *sn_se_my_sn_instances**table **has entries** but the current instance is not listed, only 'All Instances' definitions execute"* Note: Configuration option that controls whether definitions run only on specified instances. {#configure-scan-engine-properties__ul_wwc_z4c_jhc} | | Scan Non-Configuration Records | * scan_non_configuration_records * Default: `true` * When enabled, includes non-configuration tables (tables that do not extend sys_metadata) in full scans. {#configure-scan-engine-properties__ul_zbp_nsc_jhc} | [ ] {#configure-scan-engine-properties__table_a4y_xpx_2hc} * **[Configure scanning properties per persona](https://www.servicenow.com/docs/SCRT~mW6b_P32mcWo~d~HQ#teamdev-scanning-properties)** You can view and configure a variety of information, formatted into lists, that the Scan Engine uses to permit users, team leads, and admins to access content. * **[Configure application scanning properties](https://www.servicenow.com/docs/d7POPRkCxCi4RSrs~WNvew)** The Scan Engine provides options to configure application scanning and enhance governance over Team Dev push approval. Configure which applications are scanned, the parameters applications must have to satisfy Team Dev approval, and whether developers can use Suite Scans for faster, focused validation. * **[Configure update set scanning properties](https://www.servicenow.com/docs/1ScAsbBdkKQ2Ed~Ybs6lqg)** The Scan Engine provides several options to further configure update set scanning and enhance the governance over update set management. Update set scanning occurs during scheduled instance scans and when developers attempt to mark update sets complete. * **[Define My SN Instance environments](https://www.servicenow.com/docs/c2jxENFv69D3iFVssDEcsQ)** Configure instance integration settings to define the different environments for your ServiceNow instances and to take advantage of exception processing, definition syncing, and user story tracking in Impact. * **[Manage definition properties](https://www.servicenow.com/docs/day629fpwNIrcct_rHWX2g)** You can configure additional capabilities and configuration options for the definition ruleset. * **[Configure real-time scanning properties](https://www.servicenow.com/docs/veNSOP4lshZDfG5V4UU6fg)** Real-time scanning properties allow control over which users have access to real-time scanning, and how the scan operates within their environment. Perform the following procedure to configure real time scanning properties. * **[Configure real-time code resolution with AI](https://www.servicenow.com/docs/ZOG5jGRwtIW1UG5zmBFKiA)** Follow these steps to configure real-time code resolution with AI suggested fixes for Impact Platform Health. * **[Configure exception reason properties](https://www.servicenow.com/docs/k4b~I5SG5QnWft0pzNNTdA)** When real-time enforcement, `enforce_real_time_validation` is set to `true`, Recommend level findings require an approved exception reason before the form can be saved. *[\>]: and then