A. One standard option set for only hardware,
B. One standard option set for only software with FNI without hardware,
C. One scan now option set for hardware, and software with FNI.
1) When software option set (B) runs, FNI goes back up in the Oracle database. This is okay.
2) When scan option set (C) runs, FNI goes back up in the Oracle database. This is okay.
3) When hardware option set (A) runs, all FNI disappears from Oracle database. This is a bug, because they should not disappear at all (see item 4)
4) Now uncheck software in option set (C), it becomes a purely hardware option set like (A) and thus without FNI.
When this scan (modified as above) (new C) runs, FNI does not disappear from Oracle database.
This is okay, but the functioning of the scan now option set (C) is not the same as standard option set (A, & item 3)
There is indeed a bug somewhere because now (A) and (C) are same. It seems the code is not same for a scan with a standard option set (A) and for a scan with a scan now option set (C).
It is very important not to lose FNI.
Product is working as designed. Keeping FNI data functionality is being investigated for future products.
The way to keep the data is:
1. Avoid scans that cause FNI data to be lost,
2. Archive the FNI data via custom reports (in affect building a custom database).