---
sourceDocument: Zurich Impact
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/impact

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Scan Engine

# Scan Engine for the Impact Store Application {#ariaid-title1}

Release version: Zurich  
Updated July 31, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Scan Engine for the Impact Store Application

The Impact Scan Engine is a core component of the Impact Platform Health suite, designed to help ServiceNow customers proactively manage instance quality, compliance, and performance.
Integrated with the Impact Store App, it automates real-time code inspections to identify deficiencies, enforce coding standards, and support platform health by scanning ServiceNow instances for issues based on active definitions stored in the Scan Findings table.
Show full answer Show less  
This tool enables customers to monitor and control development activities, enhance maintainability, improve upgrades, and reduce costs by minimizing manual code reviews prone to error. Additionally, it calculates technical debt and estimates resolution times, empowering proactive quality monitoring and developer training through real-time feedback.

## Key Features

* **Real-time enforcement of leading practices and code standards:** Prevents saving records with unresolved issues by blocking problematic changes during development.
* **Role-based visibility and controls:** Enhances platform performance, security, and user experience by tailoring access.
* **Automated scans:** Includes scheduled full scans, on-demand delta scans for recent changes, update set scans, and application scans to identify issues before publishing.
* **Comprehensive scan definitions:** Uses a large set of rules to detect coding and workflow issues and supports continuous quality improvement.
* **Technical debt measurement:** Provides progress percentiles and estimated time remaining on fixes to aid planning and prioritization.

## Scan Types

The Scan Engine supports various scan types to address different needs:

* **Initial Diagnostic Scan (Scheduled):** Full instance scan run on schedule or manually, providing comprehensive findings.
* **Diagnostic On-demand Scan (Delta):** Scans only modified records or application files since the last scan, focusing on previously identified issues.
* **Update Set Scan:** Analyzes open update sets, with initial full scans and subsequent delta scans for changes, including child update set findings.
* **Application Scan:** Detects definition findings in applications before they are published to the repository, ensuring quality before deployment.

## Practical Use and Configuration

Customers can configure and run scans based on their operational needs, leveraging scheduled or on-demand options to maintain continuous quality oversight. Scan results, including detailed and summarized findings, support informed decision-making for development and maintenance activities. For configuration details, customers should refer to specific guidance on running scans and managing analytics dashboards.  
Impact Platform Health uses the Impact
Scan Engine to enable proactive management of instance quality, compliance, and performance. The Scan Engine is integrated with your Impact Store App to support platform health and adherence to leading practices.
The Scan Engine examines ServiceNow instances for findings related to active definitions that are stored in the Scan Findings table. You can view existing or resolved findings that resulted from the instance scans or summarized and
detailed scan information.

Impact
Scan Engine automates your code inspections in real-time so you can identify more deficiencies, improve the quality of your instances, and speed up your development efforts. You can also monitor and control
development activities to proactively improve the quality of the system and support ongoing efforts to improve it over time.

## Benefits and overview {#impact-scan-engine-overview__section_nkt_ypx_lgc}

* Enforce leading practices and code standards in real-time.
* Enhance platform performance, security, and user experience with role-based visibility and controls.
* Improve maintainability, upgrades, and problem management.
* Reduce development and maintenance costs.
* Diminish the need for manual code reviews, which are prone to human error.
* Calculate technical debt and estimate resolution time with scan output findings, progress percentiles, and estimated time remaining on code fixes.
* Empower proactive code quality monitoring and detection versus reactive corrections.
* Automate developer feedback and training through real-time, leading practice rule evaluations.
{#impact-scan-engine-overview__ul_rwc_1qx_lgc}

## Scan definitions {#impact-scan-engine-overview__scan-definitions-overview}

Scan Engine uses a large set of definitions to correct coding and workflow findings in real time and performs scans across your entire instance to detect existing findings. This prevents developer mistakes by
blocking saving a record before issues are resolved. Nightly scans identify existing findings across the entire instance.

For more information, see [Scan Engine definitions](https://www.servicenow.com/docs/JGTbX3_nv5PfQMGYu3Le~w "The Scan Engine uses a large set of definitions to correct coding and workflow findings in real time and perform scans across your entire instance to detect existing findings.").

## Scan types {#impact-scan-engine-overview__section_mqt_vqx_lgc}

There are different types of scans that you can run on your instances. Depending on the type of scan, the properties required during configuration vary.

Refer to the table for information on the available scan types.  
{#impact-scan-engine-overview__section_mqt_vqx_lgc__entry__2}

| Scan type | Description |
|-|-|
| Initial diagnostic scan (Scheduled scan) | * Runs based on defined Scheduled Scan options or on-demand with the Execute Now option. Note: The first executed instance scan is a full scan. See [Run your first scan with the Scan Engine](https://www.servicenow.com/docs/JimyNX6HSxy~cqqn5nUdkw "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.") for first time setup. * View existing or resolved findings that resulted from the instance scans as well as summarized and detailed scan information. |
| Diagnostic scans- On-demand scan (subsequent delta scans) | * Scans for configured updates that occurred since the last scan. * Specifically analyzes application files that have been modified or sys_update_xml records. * Delta scans always look for definitions marked to return one row check per system property. * Scans for specific definitions that were identified as development issues in a previous scan. Note: See [Configure Scan Engine properties](https://www.servicenow.com/docs/2zlFyhVtwSoxB22F1frkEw "Configure the primary scanning capabilities and configuration options for scheduled, on-demand, and real-time scans.") for on-demand scan configuration options. |
| Update set scan | * Scans individual update sets for findings.The initial Update set scan is a full scan of all open update sets. Subsequent scans only scans records that have been modified since the last scan date (delta scan). * Child update set findings are visible from the parent update set findings summary scan record. Note: See [Configure update set scanning properties](https://www.servicenow.com/docs/omt8aNFIdG8FdtNKp~MB1A "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. The settings on this tab define which update sets will be scanned, and the parameters those update sets have to meet in order to be marked complete.") for details. |
| Application scan | Scan applications to identify definition findings before publishing to the application repository. Note: See [Initiate application scans](https://www.servicenow.com/docs/g5lzi5AusmZNEKjXqFcZyw "You can scan applications to identify definition findings before publishing to the application repository. Application scans give insight into health scores, the number of findings, and the total impact of findings within your custom applications. ")for details. |
[Table 1. Scan Engine scan types and descriptions]

## Configuration overview {#impact-scan-engine-overview__config-overview}

For more information on configuring and running the Scan Engine, see [Running on-demand scans](https://www.servicenow.com/docs/YlS8V6kzUxqnzcZzzQlqEQ "You can initiate some scan types on-demand to run whenever they are required."), and [Analytics Dashboards](https://www.servicenow.com/docs/BjJ7FlN~Mw7fKeN~nzQRbg "Analytics Dashboards provide a graphical way to view detailed information relating to findings, both pending and resolved, with the Scan Engine. The dashboards are role-based, allowing for persona-based views of information. They display  key metrics,  charts, and  trend analysis.").

