Conditions

Conditions are objects that return a single Boolean value based on the evaluation of an analysis or of a Key Performance Indicator (KPI).

What a condition evaluates depends on whether it is based on an analysis or on a KPI, as follows:

For an analysis, it evaluates the row count of the analysis.
For a KPI, it evaluates the status of the KPI.

For example, a condition might evaluate whether the results of an analysis return a number of rows greater than 0:
If the analysis returns at least one row, then the condition evaluates to true.
If the analysis does not return any rows, then the condition evaluates to false.

Condition Uses

You use conditions to determine whether:

Agents deliver their content and execute their actions
Actions links (which when clicked run actions) are displayed in dashboard pages
Sections and their content are displayed in dashboard pages

For example, a sales manager wants to deliver a Monthly Sales Report to his direct reports only when sales drop below $2 million. You might create a condition that is based on an analysis that shows sales that are below $2 million and add it to an agent whose delivery content is the Monthly Sales Report. When the condition evaluates to true (that is, the analysis contains rows where sales are below $2 million), the agent is triggered to deliver the Monthly Sales Report.

You can also use a different kind of condition to determine whether action links are enabled in analyses. For information, see Conditionally Enabled Actions Added to Analyses.

Condition Elements

A condition consists of the following elements:

An analysis or KPI.
The criteria to use when evaluating the condition:
- For an analysis, the criteria is a row count and an operator to apply to the row count; for example, the row count equals 100.
- For a KPI, the criteria is a KPI status, for example, the KPI status is OK.
Values for any prompted filters that are associated with the analysis or values for KPI dimensions that were set to Set in watchlist in the KPI.