---
sourceDocument: Yokohama Impact
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/impact

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Configuring Proactive Code Check

# Configuring Proactive Code Check {#ariaid-title1}

* Release version: Yokohama
* 
* Updated February 27, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Impact Platform Health features Proactive Code Check that can be activated to perform a code review in your instances.

Proactive Code Check single instance scanning is supported with the ServiceNow Washington DC release and later. Synchronizing between multiple instances and viewing results on the dashboard are features supported with the ServiceNow Yokohama release and later.

## Single instance scanning {#configuring-proactive-code-check__section_av2_mqy_m2c}

Developers can execute Proactive Code Check (PCC) on update sets in non-production instances to reduce technical issues from being introduced into production. The Impact Health Store Application is installed as part of the Impact Store App. For additional details on the installation process, see [Configuring the Impact Store Application](https://www.servicenow.com/docs/lTWcK5qRySp0L2vZT96PJA "The tasks are outlined that are required to install and configure the Impact Store Application.").

## Multiple instance synchronization {#configuring-proactive-code-check__section_rkn_nqy_m2c}

Proactive Code Check allows synchronizing between production and non-production instances and viewing results on the Platform Health dashboard. This functionality requires an initial trust relationship between the
production instance and the identified non-production instance.

For details on the configuration, see [Configure the Multi-Instance Framework for Proactive Code Check](https://www.servicenow.com/docs/JE0ieM09Ob8J1jttkbmpwg "Configuring the Multi-Instance Framework explains how to connect data movement from non-production instances to production instances. The mTLS must be installed and configured to connect non-production instances to production instances to allow data movement and synchronization. Before creating trust profiles, managing instances must also be configured.").  
Important:  
The Impact Store App must be installed on any non-production instance to conduct code checks, as well as in a reporting or production instance.