Scan Engine for the Impact Store Application

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
    • Summarize
    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, integrated with the Impact Store App, enables ServiceNow customers to proactively manage instance quality, compliance, and performance. It automates real-time code inspections to identify deficiencies, enforce leading practices, and improve overall platform health. The engine scans ServiceNow instances for findings based on active definitions stored in the Scan Findings table and supports role-based visibility and controls to enhance security and user experience.

    Show full answer Show less

    Key Features

    • Real-time enforcement: Automatically enforces coding and workflow standards, blocking saves when issues are detected to prevent developer errors.
    • Automated scanning types: Supports multiple scan types including initial diagnostic (full) scans, on-demand delta scans, update set scans, and application scans to identify issues before publishing.
    • Comprehensive findings management: Allows viewing of existing, resolved, summarized, and detailed scan results to monitor code quality over time.
    • Technical debt calculation: Provides metrics such as progress percentiles and estimated resolution times to help prioritize code fixes.
    • Developer feedback and training: Automates feedback through rule evaluations, empowering proactive quality monitoring instead of reactive corrections.

    Practical Benefits

    • Improves platform performance, security, and maintainability by enforcing best practices.
    • Reduces manual code review efforts and associated human errors.
    • Supports smoother upgrades and more effective problem management.
    • Offers role-based controls to manage development activities transparently and efficiently.
    • Helps reduce development and maintenance costs by catching issues early and providing actionable insights.

    Scan Types and Use Cases

    ServiceNow customers can configure different scan types depending on their needs:

    • Initial Diagnostic Scan: A full scan run either on schedule or on-demand to establish a baseline and identify all issues.
    • On-demand Diagnostic Delta Scan: Scans only updates since the last scan to detect new or unresolved development issues.
    • Update Set Scan: Focuses on specific update sets to find issues, with subsequent scans targeting only changed records.
    • Application Scan: Checks applications for findings before publishing to ensure quality and compliance.

    Next Steps for ServiceNow Customers

    To leverage the Scan Engine effectively, customers should:

    • Configure scan parameters based on their environment and development workflows.
    • Run initial full scans to establish a quality baseline.
    • Use on-demand and scheduled scans to continuously monitor and improve code quality.
    • Review scan findings regularly to reduce technical debt and improve maintainability.
    • Utilize analytics dashboards for insights into platform health and development progress.

    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

    • 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.

    Scan definitions

    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.

    Scan types

    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.

    Table 1. Scan Engine scan types and descriptions
    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 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 parameters 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 for details.
    Application scan Scan applications to identify definition findings before publishing to the application repository.
    Note:
    See Initiate application scansfor details.

    Configuration overview

    For more information on configuring and running the Scan Engine, see Running on-demand scans, and Analytics Dashboards.