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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Configure update set scanning properties

# Configure update set scanning properties {#ariaid-title1}

* Release version: Australia
* 
* Updated July 10, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

The Scan Engine provides several options to further configure update set scanning and enhance the governance over update set management. Update set scanning occurs during scheduled instance scans and when
developers attempt to mark update sets complete.

## Before you begin

Update sets are scanned in two scenarios:

* During scheduled instance scans
* When a user attempts to mark an update set as Complete

{#update-set-scanning-properties2__ul_uds_scan_scenarios}

Role required: scan_engine_admin

## Procedure

1. Navigate to ALLImpactConfigurationScan Engine Properties.
2. Select the Update Sets tab.
3. Configure the update set scanning condition using the condition builder.  
   These conditions determine which update sets to scan. By default, conditions
   filter out non-active and default update sets.
4. Select the Enforce update set validation check box to require update sets to meet completion conditions.  
   When enabled, update sets must meet the conditions specified in the
   Conditions for completing an update set
   field.

   When enforcement is enabled, a completion enforcement message appears in the scan modal warning users of requirements to complete the update set. Message content changes based on the scan type and enforcement condition. For example, if a specific suite is required, the message directs the user to select that suite.  
   Warning:  
   Update sets can't be marked complete until conditions are met.
5. Configure conditions for completing an update set using the condition builder.  
   These conditions determine whether an update set can be marked complete.
6. **Optional:** Configure additional update set scanning options.  
   {#update-set-scanning-properties2__entry__2}

   | Field | Description |
   |-|-|
   | Enable update set summary scan synchronization | Allows update set summary scans to be synced between instances defined in the multi-instance communication API integration. |
   | Table for update set scanning condition | Specifies which table the scan condition builder references. By default, this is the Update Set \[sys_update_set\] table and is typically not changed. |
   | Override Environment Check for Update Set Scans | Enables all active definitions to run during update set scans regardless of instance-specific settings. Useful for validating update sets before promoting them to production. |
   | Allow Suite Scan for update sets | * When selected, developers can choose between Full scan and Suite scan. * Suite Scan runs only selected definitions for faster validation. * Full Scan runs all active definitions for comprehensive validation. * When cleared, only Full scans are available. * If completion enforcement is enabled and requires a specific suite, users must select that suite from the dropdown to meet the completion condition. For example, if the condition requires the Scan Engine suite, users must select Scan Engine from the suite list. |
   [Table 1. Additional update set scanning options]

7. Select Save.
**Related tasks**   

* [Customize Scan Engine definition suites](https://servicenow-prod.fluidtopics.net/pKXcsp_Hre6e43l_VSMZ9A#create-scan-engine-definition-suites "Follow these steps to create or modify Scan Engine definition suites.")
* [Configure application scanning properties](https://servicenow-prod.fluidtopics.net/d7POPRkCxCi4RSrs~WNvew "The Scan Engine provides options to configure application scanning and enhance governance over Team Dev push approval. Configure which applications are scanned, the parameters applications must have to satisfy Team Dev approval, and whether developers can use Suite Scans for faster, focused validation.")
* [Initiate update set scans](https://servicenow-prod.fluidtopics.net/kak8jXbYp1vGT_NCgEuIzw "Scan open update sets for findings to gain insights into what you're importing and exporting across your environments. When Suite Scan is enabled, choose between scanning all active definitions or a curated suite.")

*[\>]: and then