Creating new alerts
- Juan Tomás Alonso Nieto (Deactivated)
What permissions do I need?
In order to define new alerts, you need to have a role with management permissions on Alert configuration and also in My Alerts or any of the subcategories (Administration → Roles → Permissions/Alerts tabs).
Where can I create new alerts?
Alerts are tasks that continually monitor active queries to look for and report on specific events or conditions. Therefore, alerts are created from within the Data Search area where queries are made.
Open the required data table and perform the operations and filters necessary to identify the alert condition. Then, select New Alert Definition on the toolbar and fill in the required information as instructed in the section below. Click Create to save the alert.
The new alert is automatically associated with the default sending policy. If you want to choose a different one, go to Administration → Alert Configuration. Check the Manage defined alerts article to know how to do it.
You can also click on the Configure Alerts button on the message that appears right after creating the alert.
Once you have some alerts created, you can create an alert based on them. For more information, see Create an alert based on triggered alerts.
Â
New Alert Definition window
These are the mandatory fields to complete in this form:
Summary | A short message used to identify the alert condition. This text is displayed in the Alerts History, found in the Summary column. You can include in the alert Summary the field values associated with the alert using the case-sensitive variable$columnName.Take into account that only those fields strictly related to the alert are valid and they depend on the trigger method used. See each Alert trigger method to know the accepted fields. |
|---|---|
Description | The full description of the alert condition. When distributed by e-mail, this text will appear in the e-mail body. In the Alerts History, this is the information displayed when you use the drop-down control to expand the Summary. You can include in the alert Description the field values associated with the alert using the case-sensitive variable $columnName. Take into account that only those fields strictly related to the alert are valid and they depend on the trigger method used. See each Alert trigger method to know the accepted fields. |
Subcategory | Alerts created by Devo users are always created under the My Alerts category. This is the subcategory you will use to group this alert. |
Alert name | This should be a descriptive title for this alert. It will appear in the Alerts History in the Alert name column. When a triggered alert is distributed by e-mail, this text is included in the e-mail subject. |
Priority | Indicates the priority assigned to this type of alert. Choose from five levels: Very Low, Low, Medium, High, and Very high. |
Trigger methods | In the lower part of the window, you will see those methods you can use according to the transformations you applied in the query: |
Can I create alerts with all queries?
You can create alerts with a variety of queries and tables, however, there are some restrictions.
Blocked queries
You cannot create an alert on a query that has been blocked or added to your aliased finder. The New Alert Definition button will not appear in the toolbar and you will see the Incognito Mode button. Click it and select to clone the query in order to be able to create the alert.
Injected tables
You cannot create an alert on a table that has been injected with data from another table (my.app tables). The New Alert Definition button will not appear in the toolbar when you access this type of table.
Â
Related articles: