The alert wizard helps with the task of defining an alert.
The process has the following basic steps:
Step 1 - Name/Describe the Alert
Step 2 - Define the Alert Condition
Step 3 - Define when to Test the Alert Condition
Step 5 - Define the Action(s) to Take when the Alert Fires
Depending on selections, some of the above steps may be skipped.
Starting the alert wizard
Start the alert wizard by choosing Alert
Wizard from the Tools menu.
The first time you start the wizard you will be met by two start pages, the first one describing the concept of alerts and the second one outlining the wizard and the basic steps involved. If you want to skip the start pages when you use the wizard in the future, mark the Don't show this page again check box in either or both pages. Click Next to continue.
Step 1 - Name/Describe the Alert
Enter a name and/or a short text under Alert description, describing the alert you are about to create. This is a commentary field where the creator of an alert can describe the purpose of the alert or any details with regard to the alert. It is only used in the list of alerts in the Alerts dialog. Click Next to continue.
Step 2 - Define the Alert Condition
In this step you define the alert condition and the selection state that should be used when checking the alert condition. Fill in the following fields:
- Alert condition: Enter a QlikView expression that should evaluate to true (non zero) when the alert is to fire.
- Selection
state when testing alert: Here you decide which selection state should be used when testing the
result of the alert condition. There are three choices:
- Current Selection: The alert condition will be tested using whatever selections are made at the time of checking the alert.
- All Clear: All selections will be temporarily cleared before testing the alert condition.
- Bookmark: A specified bookmark will temporarily be applied before testing the alert condition.
Click Next to continue.
Step 3 - Define when to Test the Alert Condition
In this step you define when the alert should be checked. The alert can be manually checked by means of Automation calls at any time. Automatic checks at relevant events can be made with the settings in this page. Fill in the following fields:
- Check alert
interactively: Enable this option if the alert is meant to be checked automatically
upon the events below.
- On Open: Enable this option if the alert is to be automatically checked when the document is opened.
- On Post Reload: Enable this option if the alert is to be automatically checked after a Reload of the document (script execution).
- On Post Reduce: Enable this option if the alert is to be automatically checked after a data reduction (Reduce data command) has taken place in the document.
- Batch alert: Enable this option if the alert is designed for triggering from external programs via the special Automation API for Batch triggers.
Click Next to continue.
Step 4 - Define Test Delay
In this step you may define a suspension period after the alert has been fired, in which the alert should not be checked. This makes it possible e.g. to make an alert fire only the first time you open a document each day. Fill in the following fields:
- Delay: The re-firing of automatically checked alerts may be suspended for a given time after that an alert has been fired. Enter a number of days in this box. Decimal numbers may be used to specify part of a day.
- Trigger Level: The firing of automatically checked alerts may also be suspended based
on data changes. In this drop-down you can choose between three levels
of reoccurrence.
- Always: The alert is fired every time the trigger event(s) occur and the alert condition is fulfilled.
- Message changes: The firing of the alert is suspended until the alert Message changes. This is of course only meaningful with dynamic message text. Note that the state of the alert condition does not necessarily have to change in order for the evaluated message to change.
- State changes: The firing of the alert is suspended until the alert state changes, i.e. the alert condition has been unfulfilled during at least one check and becomes fulfilled again during a later check. This is the strongest type of alert suspension.
Click Next to continue.
Step 5 - Define the Action(s) to Take when the Alert Fires
In this final step you decide what actions should be taken when the alert is fired. If your alert is for check by macros only, this step may not be necessary. Fill in the following fields:
- Message: Here you type the message to be displayed with the alert. In case of pop-up alerts this is what appears in the pop-up. In case of mail alerts this is the body text of the mail. The text may be defined as a QlikView expression for dynamic update. By clicking on the ... button the full Edit Expression dialog is opened for easier editing of long formulas.
- Show Pop-up: Enable this option if you want the alert message to be shown as a pop-up balloon when the alert is fired.
- Send mail: Enable this option to send mail as a result of the alert being fired. The body of the mail will be the alert message text.
- Mail Subject: Enter a text which will be used as mail subject in the sent mail(s). The subject may be defined as a QlikView expression.
- Mail recipients: Enter a semi-colon separated list of mail addresses. Each of these addresses will receive an e-mail message whenever the alert fires. The list may be defined as a QlikView expression.
Click Finish to complete the creation of the new alert.
