Effects of Scan-Setting Changes on Rescans

FlexNet Code Insight 2019 R1

One type of change event that does effect 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 • Keep in mind that, 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.

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.

Types of Full Rescan to Expect Should Scan Profile Settings Change

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 

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)