---
sourceDocument: Australia Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/impact

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Exception reason integration

# Exception reason integration {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

You can synchronize exception reasons from sub-production to Production instances once a record is created or updated.

## Vorbereitungen

Role required: sn_se.scan_engine_admin, sn_se.scan_engine_read_user, sn_se.internal_rest_integration

## Prozedur

1. Register your instances.  
   See [Register your instance](https://servicenow-prod.fluidtopics.net/zdbxNAOl1bkmxGMVrfe6HA "Integrate with your other environments running Impact and utilize Scan Engine diagnostics.You can connect your instances with a one-time configuration, available in both Basic Auth and OAuth 2.0.").
2. Navigate to ALLImpactConfigurationScan Engine Properties.
3. Configure the settings on the Exception reason properties tab.  
   For more information, see [Configure exception reason properties](https://servicenow-prod.fluidtopics.net/2pxP7WKHt4pDQe~NZkP3vA "When real-time enforcement, enforce_real_time_validation is set to true, Recommend level findings require an approved exception reason before the form can be saved.").