FlexNet Code Insight Forum
How do you handle auditing large projects since workspaces are no longer available in V7?
In V6 we could create a multitude of workspaces for each project. In our case we would create at least two workspaces. One for the project artifacts that get pulled into the build, and the other for project sources. This allowed us to concentrate o...
FNCI (2018 – 2019.R1) “Upload Project Codebase” and “Version Control Instances” do not coexist?
“Upload Project Codebase” and “Version Control Instances” do not coexist under the same “numbered” Directory Structure.When using “Version Control Instances” to automatically download GitHub sources, if you have other codebase stored under the projec...
FNCI 2019.R1 - "MySQL New Character Set Default is utf8mb4" and /etc/my.cnf settings.
MySQL server running on CentOS 7. I upgraded my core/scan server from FNCI 2018.R4 to 2019.R1In the FNCI-RN-2019R1.pdf file, page 8 states the new character set: "MySQL New Character Set Default is utf8mb4""For upgraded instances, the character set ...
FNCI 6.13.0 - "Save as Standard Notice Data" - ERROR: "Component Version can not be blank"
Anyone Encountered this error when using the Palamida Detector on FNCI 6.13.0 and trying to "Save as Standard Notice Data"?I upgraded my FNCI scan and core from 6.11.3 to 6.13.0. and the update was successful.(my setup - OS CentOS 6.5, MySQL 5.7)Flex...
Open New Case: Missing version numbers for FNCI 2019.R1 and FNCI 6.13.0
Last week I opened couple of cases related to FNCI 2019.R1 and FNCI 6.13.0 and could not find the versions associated to this releases under "Get Support" -> "Open New Case"Latest versions listed are FNCI 6.12.3 and FNCI 2018.R3.Thank you,LP
