---
sourceDocument: Australia Impact
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/impact

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Submit exceptions for Scan Engine findings

# Submit exceptions for Scan Engine findings {#ariaid-title1}

Release version: Australia  
Updated September 21, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Developers can submit exception requests for Suggest, Review, Recommend, and Act level findings if they determine the finding should not be considered an issue to deter development. The availability of each finding level
depends on the exception reason scope configured by your system administrator.

## Before you begin

Exceptions can be submitted for any finding level, Suggest, Review, Recommend, or Act, depending on the exception reason scope configured by your system administrator. Exceptions require approval from a user with the approval
role. If the exception is approved, the finding is excluded from technical debt.  
Note:  
The record under the Scanned Record field of the finding, sn_se_finding, record should be extending sys_metadata table in order for the Scan Engine Exceptions UI action button to be available. For more information on configuring exception properties, refer to [Configure exception reason properties](https://www.servicenow.com/docs/k4b~I5SG5QnWft0pzNNTdA "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.").

Role required: sn_se.scan_engine_admin, sn_impact_common.Impact Developer, or sn_impact_common.Impact App Admin

## Procedure

1. From a summary scan record or an update set scan, use the Findings related list to view all findings discovered during a scan.
2. When a finding is detected at a level with exceptions enabled, select View finding details in the summary banner to open the Findings panel.
3. In the Findings panel, select the tab for the finding level you want to submit an exception for, such as Suggest, Review, Recommend, or Act.  
4. On the finding card, select Create exception.
5. Enter the reason in the Exception Reason field for why an exception should be made for this finding.
6. Choose how to proceed with your exception:  
   {#submitting-exception-reasons-scan-engine__exception-button-states__entry__3}

   | Button | Purpose | Outcome |
   |-|-|-|
   | Save as draft | * Preserve your exception without submitting for approval. * You can edit and submit later. | Exception state set to Draft. Finding card displays the Draft badge. You can select Update draft or Submit for approval when ready. |
   | Submit for approval | Send the exception to an exception approver for review and approval decision. | * Exception state set to Requested. * Finding card displays the Exception drafted badge. * Exception is submitted for review and you can withdraw the request, if needed. |
   [Table 1. Exception submission button options]

   {#submitting-exception-reasons-scan-engine__exception-button-states}
7. Review your exception state on the finding card:  
   * Exception drafted: Draft created.
   * Select View exception reason to modify your exception reason. or Submit for approval to send it for review.
   * Pending approval: The finding card displays the Pending approval badge with the submission date.
   * An approver will either approve or reject your exception. You can select Withdraw request to cancel the submission.

   You receive notification of the approval decision. If approved, the finding card displays the Approved badge with the approval date and is excluded from technical debt calculations. If rejected, you can submit a new exception request or work to resolve the finding.  
   Note:  
   If the requester name or email notification does not display correctly in the exception record after submission, verify your user account is properly synchronized between development and production environments. The Scan Engine exception workflow requires consistent user identification across instances.
{#submitting-exception-reasons-scan-engine__steps_p5t_s3q_gjc}