Comparison of Standard and Inventory-Only Imports

FlexNet Code Insight 2020 R2

The type of target project for an import determines the type of import that is run (see Target Project Types). For example, if the target project was created as a standard project in FlexNet Code Insight (that is, its Type attribute is Standard), then the import will be a standard import process. If the target project was created as an inventory-only project (that is, its Type attribute is Inventory Only), then the import will be an inventory-only import process. In turn, the import type then controls import behavior and the type of data imported to the target project, as described in the following table.

Comparison of Standard and Inventory-Only Imports

Import Behaviors and Usage	Standard Import	Inventory-only Import
Import scope	Performs a full import (that is, both inventory and codebase files are processed): • Processes all inventory items (published and unpublished). • Per inventory item, provides inventory details, status, and associated repository item (component-version-license). • Lists associated file paths for inventory.	Performs a partial import: • Processes inventory only. • Does not process codebase files (reviewed or unreviewed).
File processing	Does the following: • Processes all codebase files marked as reviewed in the import data file. • Provides absolute file paths and MD5s for processed codebase files. • Does not import unreviewed codebase files.	Does not process codebase files (reviewed or unreviewed).
Custom-data processing	Imports custom versions, custom licenses, and custom mappings of versions and licenses to third-party components.*	Imports custom versions, custom licenses, and custom mappings of versions and licenses to third-party components.*
Required type for target project	Requires a project created with the Standard attribute.	Requires a project created with the Inventory Only attribute.
Target project codebase requirement	Requires a codebase that is uploaded (or synchronized) to the target project and scanned before the import.	Requires no codebase.
Access to imported inventory and codebase files	Provides direct access to the following in the target project once the import completes: • The imported inventory, displayed in Project Inventory and Analysis Workbench. • Imported codebase files, displayed in Analysis Workbench.	Provides direct access to imported inventory in Project Inventory only.
Usage	Produces a full project copy that can be used for the following (for ongoing scanning and analysis): • Full project backups. • Application of analysis work from one product version to another (for branching or versioning purposes).	Provides a means to create inventory from the following: • An external system. • A Code Insight inventory-only project that is configured to scan remotely using a Jenkins plugin or another scan agent plugin.

* The import does not process custom components. Instead, to represent inventory with custom components, the import assigns the inventory with an inventory type of either work-in-progress (WIP) or the license-only.