Thanks for  the feedback,  we appreciate the input.  We are always looking for ways to reduce false positives and make the review of scans faster.  I sent you information on how you can fine tune snippet matches in my previous post.  In v7 we have added a confidence level to our matches so that you can choose at which level you automatically publish items. I will share you ideas with our product team.   thanks! ... View more

We actually use all three depending on our situation.  For example, if we have multiple people reviewing the same scan, the person who is responsible for following up on text and license matches to "gpl" will often create an unpublished group called "not gpl" so that if other people working on the scan are reviewing other indicators they can see that someone has already identified the gpl match is a false positive.  If I am just working on a scan by myself,  once I have reviewed all the indicators associated with a file I will mark it as reviewed. If you find a search term is creating "too many" false positive you can try to fine tune the text strings that are in the scan settings based on the results you are seeing.  If the false positive is in in-house proprietary code, it might be helpful to create a group called in-house code to mark files that have false positive indicators.  Especially, if you are familiar with the code and know that it was authored by your developers.  It can be a quicker way to remove false positives. Ultimately, practice seems to be the best medicine for quickly identifying false positives and quickly marking them. ... View more

Which version of FNCI are you using?  The answer depends on what you want to accomplish.  If you want only the most recent BOM for your product. Then you will want to upload the newest code, delete the previously uploaded files and scan.  But if you want to keep each BOM for each version, then you will want to look at Copying and Branching projects.  See section 12 in the User Guide (v6.13.1). If you are using v7 2019, it's a little more complicated.  You will need to export your current scan, create a new project, scan your newest version of the code, then import the export from the previous into the new project.  For files that remain the same all the research you do will be copied on top of  the new project. Please let me know if this is helpful.  I can provide more information depending on which version you use. ... View more

Thanks for the suggestion.  I'll pass it along to our product team!!   Cheers,   Dave McLoughlin ... View more

Hi Christine,   When you reached out to support did you also explain the FNCI 6.X was out of date.  I can see FNCI 2019.R1 is available, but the list of versions in opening a case still is out of date for 6.X.   Dave ... View more

Hi,  Can you please send an email with details to support@flexera.com.  Include your name, company name, and user id from the community portal.  Explain that you can not see your cases in the community.  They should be able to associate your username with the correct corporate account information to enable the ability to see your cases.  Please let me know if you have any trouble.   thanks! ... View more

Sorry for the late response.  First, are you still having the issue?  If yes, were you previously able to see your cases?  If not, then you will need to make sure you have properly registered and are signed in to see "My Cases" from the "Get Support" menu.  Let me know and I can check if you are registered or not. ... View more