Scan Engine Platform Owner dashboard

  • Release version: Australia
  • Updated March 12, 2026
  • 3 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 Platform Owner Dashboard

    The Scan Engine Platform Owner dashboard provides essential insights into the Scan Engine's performance, including unresolved findings, health scores, lines of code scanned, and ongoing update sets. It allows Platform Owners to monitor key metrics and manage findings effectively.

    Show full answer Show less

    Key Features

    • Outstanding Findings: Displays the number of unresolved findings from the Scan Engine.
    • Health Score: Indicates the percentage of definition occurrences without findings, calculated as 1 - (F / D) 100.
    • Lines of Code Scanned: Total lines of code analyzed, including script fields and base system records.
    • In Progress Update Sets: Shows unfinished update sets being developed.
    • Findings by Impact to Instance: Categorizes total findings by their impact level, allowing quick access to detailed findings.
    • Open Findings by Team: Lists teams with their corresponding open findings, facilitating accountability and management.
    • Trend Charts: Includes visual representations of technical debt, findings by team, and real-time preventions.

    Key Outcomes

    By utilizing the dashboard, ServiceNow customers can:

    • Quickly identify and address unresolved findings to improve system health.
    • Evaluate the technical debt associated with findings and prioritize resolution efforts.
    • Monitor team performance and accountability through open findings metrics.
    • Customize view settings and time periods for more relevant data analysis.

    Access to this dashboard requires the impact.admin or impact.platform.owner role, ensuring that only authorized personnel can manage critical findings and metrics.

    The Platform Owner dashboard includes trend charts and the following overview modules.

    Table 1. Platform Owner dashboard overview
    Information module Description
    Outstanding findings The number of unresolved findings identified by the Scan Engine that have not been addressed.
    Health score

    The health score represents the percentage of definition occurrences used across the platform that did not return any findings. It is calculated as:

    1 - (F / D) * 100

    • F: The number of findings
    • D: The number of definition occurrences which is the total number of times a definition has been executed by the Scan Engine to generate findings.
    Lines of code scanned The total number of lines of code analyzed by the Scan Engine, including all script field code and any scanned base system records.
    In progress update sets The number of unfinished update sets currently being worked on by developers.
    Findings by impact to instance
    • The total findings for the instance, grouped by impact to instance.
    • Impacts to instance range from 1 (minor impact) to 10 (significant impact). You can select a bar on the chart to list the findings for that impact to the instance in a new browser tab.
    Open findings by team All available teams configured on the instance through the Team Leads related list on the Scan Engine Properties page. You can select a team from the list to show their corresponding information in the module and trend charts.
    Note:
    The number next to the team name is the number of open findings held by that team.

    Platform Owner trend charts

    The Platform Owner dashboard includes the following trend charts.

    Table 2. Platform Owner dashboard trend charts
    Chart Description
    Technical debt
    • The amount of development time required to resolve all findings.
    • You can customize the time period using the date selector.
    Technical debt by team
    • A team's total technical debt, represented as the estimated amount of development time required to resolve all team findings.
    • You can configure the teams displayed on this chart in the Scan Engine properties.
    Findings by team
    • The number of findings by team, classified by state and category.
    • Select a number to see the list of findings for that team in a new browser tab.
    Findings by impact to instance
    • Findings listed in order of highest impact to your instance with the lowest time to resolve. Address these findings first to achieve the highest impact with the lowest effort.
    • Select any finding number to view its details in a new browser window.
    Real time preventions
    • The findings that were corrected during development for each team.
    • The default time span for these preventions is 30 days. You can customize time spans using the date selector.
    Real time preventions trend
    • All real-time preventions by a team during the selected time period. A real-time prevention is when the Scan Engine prevents a finding from being saved.
    • You can customize the time period using the date selector.
    Findings by file type
    • A heatmap of findings by file type. Lets you quickly identify development areas that need the most attention.
    • Select a number in a cell to see the full list of violations for that file type/category.
    Update sets
    • A list of update sets on all configured instances for the selected time period.
    • You can customize the time period using the date selector.
    • You can add and configure instances in the My SN Instances related list in the Scan Engine properties.
    Exception reasons The number of exception approval requests by status for each team.
    Findings by suite
    • The number of findings by category, classified by suite.
    • Lets you identify findings within top-level suites and engage the relevant process owners.
    • Select a table entry to view the list of findings for that category in a new browser tab.

    Platform Owner dashboard data sources

    The following tables show the data source for each module and trend chart in the Platform Owner dashboard.
    Note:
    All components require either the impact.admin or impact.platform.owner role to use.
    Table 3. Platform Owner overview data sources
    Component Data Source
    Outstanding findings sn_se_scan_result
    Health score sn_se_scan_result
    Lines of code scanned sn_se_scan_result
    In progress update sets sn_se_scan_result
    Findings by impact to instance sn_se_summary_scan_detail
    Open findings by team sn_se_summary_scan_detail
    Table 4. Platform Owner trend chart data sources
    Component Data Source
    Technical debt sn_se_summary_scan_detail
    Technical debt by team sn_se_summary_scan_detail
    Findings by team
    • sn_se_summary_scan_detail
    • sn_se_summary_resolved_detail
    • sn_se_findings
    Findings by impact to instance sn_se_summary_scan_detail
    Real time preventions sn_se_onsubmit_prevention
    Real time preventions trend sn_se_summary_scan_detail
    Findings by file type sn_se_summary_scan_detail
    Update sets
    • sn_se_scan_result
    • sn_se_my_sn_instances
    Exception reasons sn_se_exception_reason
    Findings by suite sn_se_summary_scan_detail