Action Tracker

This page describes how to configure the Action Tracker component .

The Action Tracker is a self-contained alerting application used by KX Stream. The following screenshot illustrates an Action Tracker with horizontal layout

Set up an Action Tracker

To set up an Action Tracker, click-and-drag the component into the workspace and configure the Action Tracker properties described in the next section.

Action Tracker properties

The following sections provides details on how to configure the properties of the Action Tracker component.

Basics

Open the Basics properties on the right and configure the properties described in the following table.

Columns

Configure the properties, described in the following table.

Selection & Routing

Configure the properties, described in the following table.

Action

Refer to Actions for details.

File Export

Configure the properties, described in the following table.

Filters

This defines which of the Action Tracker data columns (visible and hidden) are available to the user in Search. Values can be mapped to View State Parameters.

Filter

Define the characteristics for each search filter.

History

Configure the properties, described in the following table. These properties are used to display historical alerts in separate panel.

Overrides

Filters applied to the main grid are also by default applied to the historical grid. This section helps to override those filters.

Highlight Rules

These properties are used to apply color updates to notify users of changes in grid values, as shown below.

Configure the properties, described in the following table

Action Type Cases

Users can create individual actions, which can be (optionally) associated/linked with other actions to form a case. Action creation requires Case Management in the Basics properties to be enabled. The Case Management UI calls dxATCreateItem with 3 parameters, these are:

1. The Action Tracker

2. Action Tracker Parameter Dictionary

3. Action Tracker Payload Dictionary ( that is, any new columns added to the properties section)

    

   Example:

    

   If the following parameters are specified in the UI: description, sym, alertkey, source, alertClass, tag1, tag2 and tag10, then the dictionary key look like:

   q

   Copy

   `sym`alertkey`source`description`alertClass`tag1`tag2`tag10

Create a Case

1. Select an Action Type from the dropdown. This is a list of available Action Trackers and is the only required parameter.

   

2. Standard editable actions are: description sym alertkey source alertClass, but these are not required parameters.

3. Add each supported Action Type for a case. More than one Action Tracker can be added.

   

4. Click Create Action (or the name defined in the Case Button Text property) to add an action.

   

5. Click + to add additional properties to a case. Added properties appear in the case property panel.

New column items are added to dxATAlert.

Tags can be used and renamed in Dashboard Column Properties.

View action (use filters if necessary); it will have it's own unique ID.

An option to link the created action with other actions is available as a tab.

When adding a link, select from Link type and Items (Action ID). Available link options are relates to, derives to, is derived from, is dependent to, depends on, is blocked by, blocks, duplicates, is duplicated by

Linked actions can be viewed with a double-click. This also opens a tab for linked actions.

All linking activity is recorded in the Activity tab

Payload

Configure the content and layout of the payload panel. The properties are described in the following table.

<div><span>{{payload.breachLevel}}</span><span>{{payload.sym}}</span></div>

Hidden Properties

Configure the properties to hide (hidden properties remain available in the template).

Tabs

Configure which tabs are active and their order. Supported options are Properties, Activity, Links and one custom/user-defined tab. The first tab on the list is opened by default.

Style, Format, Margins

Configure the properties, described in the following table.

{{formatTimeStamps "Sample date: 2019.12.31D15:30:11.000000000" "MM-DD-YYYY HH:mm:ss.SS"}}
<!-- results in:  "Sample date: 12-31-2019 15:30:11.00" if timezone is set to UTC --> 
<!-- results in:  "Sample date: 12-31-2019 10:30:11.00" if timezone is set to New York --> 
<!-- results in:  "Sample date: 01-01-2020 00:30:11.00" if timezone is set to Tokyo -->

Refer to Format for common settings and Templates for configuring property panels.

Virus scanning

Files uploaded via the Upload component, and attachments uploaded via the Action Tracker, may be screened for viruses.

For virus scanning to work you need:

1. ClamAV installed on the appserver box with up-to-date definitions.

2. Virus scanning enabled in delta.profile as follows.

   bash

   Copy

   DELTAAPPSERVER_VIRUS_SCAN_ENABLED=true

3. To check the status of virus scanning: Use the following command to check the status of the running Tomcat process. From the output displayed check if DdeltaAppServerVirusScanEnabled is either true or false. bash $ using ps -ef | grep tomcat

   With virus scanning is enabled (set to True), uploaded files are automatically scanned. If they fail the virus check, the upload is aborted and an error is reported on the dashboard.

4. Restart the appserver to pick up any changes to the above environment variable.
   

Further Reading

• Navigate Dashboards workspace

• Configure data source connections

• Use view states

• Publish & Export a dashboard