Running a plugin requires knowing the kind of plugin and the target of the plugin (for graphs, ireports, and metrics). You can view that information in the Plugin Manager by looking at the tags.
Some plugins can be run directly from the plugin manager with the run button at the top of the description. The question mark next to the run button also gives information on how to run that kind of plugin, even when run is disabled.
The following sections describe how to run plugins outside the plugin manager.
Running Architecture Plugins
Architecture plugins are more like interfaces and can be generated multiple times with different options. See your current architectures from the Architecture Browser (Architectures -> "Browse Architectures"). Create new automatic architectures from Architectures -> "New Automatic Architecture" or from the "Add New Automatic Architecture" button in the architecture browser.
Running Graph Plugins
Graph plugins always have a target. Note that graph plugins may have additional requirements to be visible. For example, a “Calls” graph will probably have “Target: Functions” but it may also require that the target function has a call reference. So if a graph does not appear in the expected location, check the plugin description for more information on requirements.
Project Graphs
Access project graphs from Graphs->Project Graphs.
Architecture Graphs
Access architecture graphs by right clicking on an architecture and using the "Graphical Views" submenu. Use Architectures-> “Browse Architectures" to open the Architecture Browser.
Entity Graphs (Target: Files, Target: Functions, Target: Classes, and Target: Objects)
Access entity graphs by right clicking on an entity and using the "Graphical Views" submenu. The "Entity Filter" (View -> “Entity Filter") is a good place to look for entities.
CodeCheck Graphs
CodeCheck graphs cannot be accessed directly. They are only available from the draw function of interactive report plugins.
Running Interactive Report (IReport) Plugins
Like graph plugins, interactive report plugins always have a target. IReports can have additional requirements. For example, an IReport for Git Authors would require that the project be associated with a Git repository. If an IReport does not appear where expected, check the plugin description for additional requirements.
Project IReports
Access project interactive reports from Project-> "Interactive Reports" or Reports -> "Interactive Reports".
Architecture IReports
Access architecture interactive reports by right clicking on an architecture and using the "Interactive Reports" submenu. Use Architectures-> “Browse Architectures" to open the Architecture Browser.
Entity IReports (Target: Files, Target: Functions, Target: Classes, and Target: Objects)
Access entity interactive reports by right clicking on an entity and using the "Interactive Reports" submenu. The "Entity Filter" (View -> “Entity Filter") is a good place to look for entities.
CodeCheck IReports
Access CodeCheck interactive reports from the context menu of a CodeCheck inspection. View and run inspections from Checks -> "Open CodeCheck". They can also be accessed from the reports icon in the "Violation Browser (Checks -> "Browse Violations").
Running Metric Plugins
Open the Metrics Browser from Metrics -> "Browse Metrics" or from the "Browse Metrics" option in the context menu of an entity or architecture. Enabled metric plugins that apply to the "Metrics Browser" selection will be displayed. Note that some metrics may have requirements in addition to the target. For example, coverage metrics will only be shown if a coverage file was placed in the expected location. So check the plugin description if metrics are not shown when expected.
Places that list metrics, like an export (Metrics -> “Export Metrics") and graph metric color scales will show enabled, applicable metric plugins.
Running CodeCheck Plugins
The plugin manager shows CodeCheck configurations. A configuration contains a list of CodeCheck checks which are also plugins. Check plugins are only visible when editing a configuration (Checks -> Select Checks) and are not directly runnable.
A configuration can be run manually or run automatically in the background.
Manual Inspections
A manual inspection is saved in your list of inspections and is a snapshot of violations at that point in time. Use this option when you want to compare results over time, or if you’re exploring options and want to be able to quickly cancel and/or delete results.
To run a configuration manually, use “Checks -> Open CodeCheck” to open the CodeCheck dialog, select the configuration from the list, and use the inspect button.
Automatic (Background) Configurations
Background configurations are run automatically by Understand every time your code is analyzed. So, they stay up to date with your code, but do not have a history. Violations from background configurations are always shown in the Violation Browser and in editors. Use this option if you’re editing code so that you can quickly fix violations as they get added.
To run a configuration in the background, use “Checks -> Select Checks” to open the configurations dialog. Right click on a configuration and check the “Run in Background” menu option.
