Dashboards : Configure dashboard components : Assign data sources to dashboard components : Assign data sources to Traffic Light
Assign data sources to Traffic Light
You can use a Traffic Light to display the status of a KPI. A coloured marker shows the threshold range in which a KPI value is located.
To use a Traffic Light you have to assign a data source to the component at first. Then you select a numeric column of your data source representing the KPI and you set thresholds to define the numeric ranges of your traffic light.
The component requires an Event, BigMemory, CSV, XML, ARIS Table or JDBC data source.
Procedure
1. Create or open a dashboard in MashZone NextGen Dashboard.
2. Click an inserted Traffic Light. The relevant properties dialog is displayed.
3. Click the Assign Data icon to edit the data source assignment.
The Edit Data Souce dialog will be displayed. Here you can select a data source and create dynamic Input Parameters. The Data Flow box shows an overview of the data source configuration.
4. Optionally you can create input parameters.
You can define dynamical and reusable input parameters for XML data sources, RAQL queries and ARIS table, see Create Input Parameters.
5. Select a data source operator in the Add a data source area and specify your settings.
a. Assign Event data source.
SeeAssign Event data source for details.
b. Assign BigMemory data source.
See Assign BigMemory data source for details.
c. Assign CSV data source.
See Assign CSV data source for details.
d. Assign XML data source.
See Assign XML data source for details.
e. Assign ARIS Table data source.
See Assign ARIS Table data source for details.
f. Assign JDBC data source.
See Assign JDBC data source for details.
6. In addition to the data source operator you can add further operators to transform the source data.
See Data transformation operators for details.
a. Select an operator, e. g. Change data type, in the Add data operations area. The relevant operator will be displayed.
b. Specify your settings.
c. You can display a preview of the transformed source data of each operator. This enables you to track all data changes step by step. Click the Calculate peview icon of an operator.
7. Click Next.
8. Assign Data columns to Traffic Light.
a. Assign a data column from the data source to the Data Column field via drag and drop.
b. Enter a Display Name.
c. For numeric values you can change the Aggregation type if necessary. Default is Avg (Average value).
d. Select an output Format in the drop-down menu or enter a format manually. The Format option is only available for columns of type number.
e. Activate the Round numerically option to round numeric values.
9. Set thresholds to define traffic light phase for KPI values.
a. Click on Thresholds bar.
By default there are three traffic light phases plus the inactive phase.
b. Click on Plus button to add a traffic light phase or click on Minus button to remove a phase.
c. Enter a threshold value for each traffic light phase.
You can either enter fix threshold values or you can choose numeric columns from your data source representing the threshold values. Assign a data column from the data source to a traffic light phase field via drag and drop.
d. Click on a Shape box to select a Color and a Shape for each traffic light phase.
e. Select an operator for each traffic light phase to define the KPI value range, e. g. < (less than).
f. You can use custom images instead of the colored shapes. Click on the drop-down menu and select Image. Then click on a Shape box and enter an URL to the relevant image.
g. By default the traffic light phase is also visible if it is inactive (A KPI value is not available.). Deactivate the Inactive state option if the traffic light phase should not be visible. You can also change the color of the inactive traffic light phase. In case of a selected image you can only deactivate the Show inactive state option.
10. Click Edit Data Source to change the source settings.
11. Click OK.
The chart will be displayed with real data of the assigned data source.
Copyright © 2013-2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback