Frequently Asked Questions

FlexNet Code Insight 6.13.2

The following questions are often asked about FlexNet Code Insight Auto-WriteUp:

How are Auto-WriteUp™, FlexNet Code Insight Rules or High-Volume Rules Groups Marked?

Each group created by Auto-WriteUp™ is marked as a System group. The Owner column in the FlexNet Code Insight Detector Client lists the forge associated with the group. The FlexNet Code Insight forge indicates a group was created with rules manually verified by FlexNet Code Insight analysts. Other forges indicate the group was created by auto- generated High-Volume Rules.

Each group has information in the Detection Notes field that describes the rules used to create the group.

How can I tell which files were detected by Auto-WriteUp™?

Files detected by Auto-WriteUp™ have a Detection Evidence tag indicating they were detected by Auto-WriteUp™.

Why did Auto-WriteUp™ create duplicate groups?

Auto-WriteUp™ does not create duplicate groups. However duplicate components may exist on forges. In that case it may appear that Auto-WriteUp™ created duplicate groups.

Why did Auto-WriteUp™ create groups with unpopulated fields?

Groups created from FlexNet Code Insight Rules will always be filled out. Groups created from auto-generated High-Volume Rules include as much (or as little) information as can be gathered from the forge associated with the group.

Why did Auto-WriteUp™ create groups without versions though I included the DO_VER option in the Auto-WriteUp™ configuration?

Not all rules can be associated with appropriate versions.

How can I tell if a group contains envelope issues without creating envelope groups?

The External Notes field of the group will contain information about any embedded issues.

After editing an Auto-WriteUp™ group, will I lose the changes if I rescan the workspace?

No, Auto-WriteUp™ will not remove any changes to the group as part of a rescan.

Open topic with navigation