Proactive Code Check analytics for the Impact Store Application

  • Versão de lançamento: Australia
  • Atualizado 12 de mar. de 2026
  • 1 min. de leitura

    • Platform Owners use Proactive Code Check to track compliance against coding best practices and organizational standards. Owners can review detailed findings and audit the status of issues that were uncovered during the scan. Historical data is available up to six months.

    Por Que e Quando Desempenhar Esta Tarefa

    Nota:
    Starting with Impact Zurich version 6.0.8 ServiceNow Store release, Proactive Code Check is being prepared for future deprecation. It will be hidden and no longer installed on new instances but will continue to be supported. For details, see the Deprecation Process [KB0867184] article in the Now Support Knowledge Base.
    • Identify recurring issues and trends in unresolved findings.
    • View progress on resolving technical debt over time.
    • Prioritize remediation efforts using a severity-based categorization of findings.

    Antes de Iniciar

    Role required: Impact_platform_owner, sn.mif_mif_read

    Procedimento

    1. Navigate to All > Impact > Platform health > Diagnostics.
      The Proactive Code Check overview displays with data from the last 30 days.

      The PCC analytics page with findings summaries displayed.

    2. Select View Dashboard to view additional information about the scans.
      • Filter by instances or by time period.
      • The Prevented findings charts display metrics related to findings that were resolved prior to moving an update set to a production completed status.Chart of the findings that were prevented in non-production update sets.
      • The Unresolved findings section displays metrics related to findings that remained open after an update set was moved to a production completed status.Chart of the findings that were unresolved in non-production update sets.
      • Compare Trends in Resolved vs. Unresolved Findings.
    3. Select View all findings to view all findings related to Proactive Code Check.
      List of all findings detected.
      • View All Findings Across Instances.
      • Filter and Group Findings by Severity, Type, or Check.
      • Identify Checks Producing the Most Findings for Targeted Improvements.
      • Analyze Findings Across Time Periods to Track Trends and Recurring Issues.
        Tabela 1. Findings count and state across time periods
        Findings category State
        Count of Findings (Findings Resolved) Muted and Created on Today
        Count of Findings Unresolved Recurring or New and Updated on Today
        Count of Findings Resolved Resolved and Updated on Today
        Count of Findings New New and Updated on Today
        Count of Findings Muted Muted and Updated on Today