Effects of Scan-Setting Changes on Rescans

One type of change event that, by default, does result in a full rescan by either Automated Analysis or Advanced Analysis (or both) is an update to settings in the scan profile associated with the rescan. Depending on which settings have changed, the full rescan could be more expensive (requiring more time and resources) than other full rescans.

Note the following:

• If you have applied a new scan profile to your project, only those profile settings that are different from the settings in the previously associated profile will impact the rescan.

• If an override of the default rescan behavior is in effect (see Configuring Rescans to Always Skip Unchanged Files), no full rescan is performed even if any of the scan profile settings listed below have changed. The rescan skips unchanged files and scans only those files that have changed.

• If the following table shows that a change to a specific setting results in a full rescan for Advanced Analysis, note that the full rescan is performed only if, in addition to the setting change, either the CL version has changed or an NG-bridge update has occurred. Otherwise, the setting change results in a scan of only changed files.

The following table provides a list of the scan profile settings and the type of full rescan to expect should any of the settings be updated prior to a codebase rescan.

Scan Profile Settings	Automated Analysis	Advanced Analysis
A change to any of these settings: Perform Package/License Discovery in Archive Dependency Support Automatically Add Related Files to Inventory	Full rescan	—
A change to any of these settings: Source Code Matches Related fields: Include System Identified Files Include Files with Exact Matches Minimum Source Code Matches	—	Full rescan (expensive)
A change to any of these settings: Exact Matches Search Terms Scan Inclusions	—	Full rescan (expensive but less expensive than that performed when Source Code Matches or related fields change)