Rescan Scenario: Handling of Files Manually Disassociated from Inventory Before Rescan

The following scenario demonstrates how the rescan process handles files that you manually disassociated from a system-generated inventory item before the rescan.

In this scenario, the initial scan on your codebase generated the inventory item log4j 2.6 and associated the files file1.jar and file2.jar with the item. However, after analyzing the inventory, you realize that file2.jar should be associated instead with log4j 2.11, an inventory item that does not exist in your current inventory. To remedy this, you perform the following steps:

1.

Create an inventory item named log4j 2.11.

2.

Disassociate the file2.jar from log4j 2.6.

3.

Associate file2.jar with the inventory item log4j 2.11 that you just you created.

On rescan, your edits remain intact:

•

The file file1.jar remains associated with the inventory item log4j 2.6.

•

The inventory item log4j 2.11 that you created is preserved along with its association with the file file2.jar.

The rescan also results in the creation of a new system-generated inventory item, log4j 2.10. However, the rescan does not associate the file file2.jar with the new inventory item.