To save scores from a table according to a regular frequency, create an automated
Role required: pa_admin, pa_power_user, and pa_data_collector
An automated indicator is based on an indicator source.
The indicator source specifies a table and a frequency at which scores from this table
are saved. After you select the indicator source and specify other properties, choose
scheduled jobs to collect data for the indicator.
This form provides all the many options for creating an automated indicator. To
create a simple automated indicator quickly, see Create an indicator and related records.
Navigate to New.
In the Name field, give the indicator a descriptive
name, such as Number of Critical Incidents.
Select the indicator source.
In the Frequency field, filter the selection of
indicator sources by their frequency of data collection.
The frequency of the indicator is set automatically based on the
frequency of the selected indicator source, such as
Daily, Weekly, or
Monthly. Filling in this field limits the
list of indicator sources to the ones whose frequency matches the field
value. This field is hidden after you select the indicator
Scroll to the
Source tab and select an Indicator
Typing a partial name in the field filters the list of available
indicator sources accordingly.
In the Aggregate field, select the aggregate function to
apply when calculating the indicator on the indicator source.
Count counts the number of records. Count
distinct counts the number of unique values rather than the
total number of records. For example, if the name of a user appears more than
once in a list, the user is only counted once. Other choices perform the
specified aggregate operation, such as summing or averaging the values in a
field across records.
If the indicator score is supposed to increase or decrease over time, select
Maximize or Minimize,
respectively, in the Direction field.
Specify any of the remaining indicator properties:
||The unit of measurement for the score, such as number, days, or
||The number of digits behind the decimal separator.
scores in the thousands and millions, the score is displayed as the
number of thousands or millions with a k or an M, respectively. For
example, a score of 612,875 with a precision of 0 is rendered as
613K. A score of 8,546,937 with a precision of 1 is rendered as
For more information, see Rounding and precision in indicators.
||Identifies the indicator as a key indicator. Used only to filter the
list of scorecards in
In the Source tab, complete any
These fields are available only if Aggregate is not set
||A check box to indicate if the value should be aggregated based on a
script. This option is available only if
Aggregate is not set to
Count. Clear the
Scripted check box to aggregate the values in
||The field to perform the aggregate operation on. This field appears
only if Aggregate is not
Count and Scripted is
not selected. You can select only numerical fields, including duration,
time, and currency.
||Select a script or create a new script for the aggregation. This
option is available only if the Scripted check
box is selected.
For more information, see Scripting in Performance Analytics.
|Value when nil
||The value that is inserted as the score when no value is collected.
This value applies only to the indicator score. It does not
impact scores for breakdown elements.
In the Additional Conditions tab, add conditions to
limit the set of records that the indicator evaluates.
The conditions in the indicator apply in addition to the conditions in the
In the Access control
tab, set whether to publish this indicator to a scorecard, and whether to limit
the visibility of the indicator by user, group, or role.
The scorecard enables analysis of the indicator through graphics.
In the Other tab, set various miscellaneous
|Default time series
||A predefined analytical function, like a 7-days running average, to
display the indicator instead of showing the actual values of the
|Live group profile
||Live group profile that indicates the live group where the indicator
scores are published.
||Number indicating the order in which scorecards are displayed.
Indicators with the lowest value are displayed at the top of the
scorecard list. If no values are provided in the
Order field, scorecards are displayed from a
to z using the Name field. To use the order
field, you must enter order numbers for all indicators. If you put in
numbers for only a few indicators, the order in which scorecards are
displayed reverts to a to z.
|Default chart type
||Set a default chart type (line, column, spline, or area) for this
indicator. When opening the detailed scorecard for the first time, the
default chart type is used. If the chart type is changed in the detailed
scorecard, that preference is remembered.
|Render continuous lines
||When selected, scorecards displaying this indicator show unbroken
data lines, even when there is no data for a specific date. This
behavior may be useful when displaying data sets with varied starting
dates or data that is not regularly updated, such as stock
|Show real-time score
||When selected, scorecards displaying this indicator show the score
in real time, as well as the current state of associated records. Clear
this check box when indicator data is not available in real time, such
as in an integration that uses data from a third-party source.
||When selected, enables reporting of historic records when viewing
this indicator on a detailed scorecard. You can filter the data to
display only the current data, only the historical data, or the data
shared between both sets.
In the Collect breakdown matrix fields tab, you can
enable second-level breakdowns for the indicator, such as Open Incidents by
Category by Priority.
Enabling second-level breakdowns can significantly impact performance.
In the Collection periods tab, override the properties
that set the maximum number of periods prior to today for which scores and
snapshots are collected and kept.
To see the properties that you would override, go to
In the Forecasting tab, set
the forecast method, the number of data collection periods to forecast, and the
amount of historical data to base the forecast on.