Context Menu Actions Panel
In the Context Menu Actions panel, Administrators can view built-in context menu actions, and add, edit, or delete custom context menu actions that appear as options in a context menu.
Workflow
What do you want to do?
Role | I want to ... | Show me how |
---|---|---|
Administrator | Custom Context Menu Actions panel | Add Custom Context Menu Actions. |
Quick Look
The following figure is an example of the Context Menu Actions panel.
1 | Displays the Context Menu Actions Panel. |
2 | Toolbar allows you to Add, Edit, Delete Context Menu Actions. |
The Context Menu Actions panel has a list and a toolbar. The following table describes the toolbar options and grid features.
Features | Description |
---|---|
Displays the Context Menu Configuration dialog, in which you can create a new context action. | |
Refreshes the list. | |
Deletes the selected context actions. NetWitness does not request confirmation that you want to delete the action. The selected actions are immediately deleted with no opportunity to cancel. | |
Displays the Edit Context Action dialog, in which you can edit an existing context action. | |
Visibility | Displays whether the context menu action is enabled or disabled. |
Action Name | The name of the context menu action as it appears on the meta when a user right-clicks to initiate action. |
Action Group | The action group under which this context menu action is grouped. |
Component | The UI component to which the Action Name and Action Group belong. |
Meta Keys | The names of the modules in which the context action is available. Currently all built-in context menu actions are for the Investigation module. When creating a context menu action, the parameter is modules. Here is a line of sample code: "modules": [ "investigation" ], |
CSS Classes and Examples
CSS classes can be meta keys and non-meta keys.
Meta Key CSS Classes
One type of CSS class that you can add is meta keys. For meta keys that have a period, change the period to a dash when defining a CSS class. For example, the meta key alias.host becomes the CSS class alias-host. The meta key ip.src becomes the CSS class ip-src.
Non-Meta Key CSS Classes
Built-in non-meta key CSS Classes are also available. The classes in the following table define actions and the part of the user interface where the action is available.
CSS Class | Type | Description |
---|---|---|
meta-value-session-link | Action | Open on meta session count number |
meta-value-name-link | Action | Open on meta value name |
nw-event-value | Action | Use for reconstruction context actions on meta value |
UAP.investigation.navigate.view. NavigationPanel |
User interface | Applies to Navigate view |
UAP.investigation.events.view. EventGrid |
User interface | Applies to Event View |
UAP.investigation.reconstruction.view. content.ReconstructedEventDataGrid |
User interface | Applies to Event Reconstruction View |
Example
This is a commented example of a context menu action to validate the user agent from the Client Application (client) meta key. The comments are removed automatically once applied in the Administration System view. The new menu item is displayed after restarting the browser.
{
"displayName": "User Agent String Lookup”, <!-- What name shows up in NW UI -->
"cssClasses": [
“client” <!-- What meta key to launch from -->
],
"description": "",
"type": "UAP.common.contextmenu.actions.URLContextAction",
"version": "1",
"modules": [
"investigation"
],
"local": "false",
"groupName": "externalLookupGroup”, <!-- What group to show link in. Remove line to show in main list -->
"urlFormat": "http://www.useragentstring.com/?uas={0}&getText=all”, <!-- The {0} gets replaced with whatever was right clicked on -->
"disabled": "",
"id": "UserAgentStringAction",
"moduleClasses": [
"UAP.investigation.navigate.view.NavigationPanel”, <-- Enabled in Navigate pane-->
“UAP.investigation.events.view.EventGrid” <-- Enabled in Event View pane -->
],
"openInNewTab": "true",
"order": "15"
}