QlikView Reference Manual.pdf - QlikCommunity - QlikView

1. Applying the selection relevant to the alert.
2. Calculating the condition expression value.
3. Restoring original selections.
The time needed to perform action 1 and 3 is of course each equal to the normal “click times“ if the selections
had been applied interactively. The time needed for step 2 is the same as if the expression had resided
e.g. in a sheet object. Added together, the time needed to check an alert can be quite substantial in large documents.
This may be of less importance for single alerts triggered on opening or reload, but caution should
be exercised when using large amounts of macro-triggered alerts, so that the document does not become sluggish.
Opens the Alerts (page 150) dialog where all QlikView alerts are created and maintained.
17.3 Alerts
The easiest way to define an alert is by using the Alert Wizard (page 154) that can be invoked from the
Tools menu.
The Alerts dialog is opened from the Tools menu. This dialog is used for managing alerts, which are stored
as part of the QlikView document. Alerts can be triggered from any Windows version of QlikView (that is,
not from AJAX clients).
An alert is a composite entity typically consisting of three basic parts:
1. A condition, i.e. a QlikView expression forming a logical condition, that can be either true or false.
2. A logical state (bookmark, clear all or current selection state) that should be applied before checking
the state of the condition expression.
3. One or more actions to be performed when the condition is checked and evaluates to true. Typical
actions include showing a message in a pop-up window or sending a message as an e-mail to one or
more recipients. Further actions can be programmed via macros.
When an alert is checked and the condition is met and the action(s) performed, it can be said that to have
fired. QlikView alert checks can be triggered in three different ways:
a. Automatically in the QlikView layout when there is a probability that the document’s data has
changed, i.e. when the document is opened, when the script has been executed or when a Reduce
Data operation has been performed.
b. Manually from a Internal Macro Interpreter (page 873) via special Automation APIs. Refer to the
QlikView file APIguide.qvw (a very useful QlikView file describing the use of the macro functionality
in QlikView, which is normally installed with the program) for details.
c. Externally from programs running QlikView in batch mode which have a special Automation API to
retrieve a list of fired alerts from a given context.
Use caution when creating alerts, large amounts of macro-triggered alerts can make the document sluggish!
150