How users view alerts


The information in this topic is applicable only for on-premises deployments.

Users do not interact directly with the Alert Events form. Instead, users view their alerts by opening a form that contains an alert list field in a browser.

Best practice
We recommend that you make sure that each group can access only one alert list form. By doing so, you can create forms with different workflows and different fields for different groups.

 
The alert list field type is a special type of table field that automatically retrieves records from the Alert Events form for the current user. Any form can contain an alert list field. The Alert List form installed with AR System contains only an alert list field and is the default form for displaying alerts.

Review the following points to understand how alert list fields work in AR System:

  • Alert list fields display the user's records from the Alert Events form.
  • If the form that triggered the alert contains a results list table field, clicking on an alert in the list opens the source request in the form that generated the alert.
  • In alert list table fields, each column represents a field from the Alert Events form, and each row represents a request. The columns themselves are fields, and you can specify their properties.
  • The alert list displays alerts from multiple servers. For web clients, the alert list queries the servers configured in Mid Tier. For more information, see Using-the-alert-list-in-a-browser.
  • If a web user has access to multiple forms with alert list fields, AR System uses the first form it finds that contains an alert list. Therefore, if users have access to multiple forms, you cannot predict which form
  • AR System will pick.

Delete unread alerts

The information in this topic is applicable only for on-premises deployments.

The CleanupAlertEvents escalation is automatically created with the Alert Events form. If enabled, this escalation deletes all unread alerts older than 30 days.

By default, the CleanupAlertEvents escalation is disabled. You can enable it and customize it according to your needs.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*