After You Save the License Mapping

When you select Yes on the Update License Mapping window to save the license mapping for the component version at the system level, Code Insight remembers this mapping when creating all future inventory for the component version across projects. This section describes what else occurs when this option is enabled.

General Results

Because the component-version-license combination is saved to the database, it is made available in other locations as described below.

•

The License dropdown for the inventory item to which you mapped the license (as well as any subsequent inventory generated by the system for the component version) shows the license as either User Preferred License or User Preferred and System Suggested License.

•

The component-version-license combination is saved to the database and made available in the Versions for <component> window and in the Lookup Component window (as a registered version with a user-preferred-license icon).

•

In the Lookup Component window, only the instance using the user-preferred license is visible for the given component version. Instances for the same component version but mapped to other licenses are not displayed.

Project Scan Behavior

The following describes what happens during project scans if you have selected to save the license mapping for the component version at the system level:

•

In general, scans on projects should create any new inventory for the component version using only the preferred license.

•

During any type of scan in general, user-edited or manually created inventory items are not impacted by the new license mapping.

•

Any scan subsequent to the fresh (initial) scan will result in duplicate inventory items for the component version. These items include:

•

The existing inventory item for the component version mapped to the old license.

•

The new inventory item for the same component version mapped to the user-preferred license.

•

After a full scan (subsequent to a fresh scan), an existing system-generated inventory item that is a duplicate mapped to the old license (see the previous bullet) will no longer have associated files. Only the item having the same component version but mapped to the user-preferred license will have associated files. (As previously noted, edited or manually created inventory items using the same component version stay the same.)

•

A fresh (initial) scan does not create duplicate inventory items for the component version.

•

When a user-preferred license mapping and a custom detection rule exists for the same component version, the resulting inventory item uses the name from custom rule but is mapped to the user-preferred license.