The way "Alerts" work in Openbravo is described below:
- Alert rules needs to be previously defined as SQL queries. SQL queries define the event that is going to be monitored.
Additional information about how to create an alert can be found here
- For instance, "Products without a defined price", "Products under stock" or "Bank account without accounting information"
- An alert rule can be applied to every Openbravo user or just to a set of them. Alert recipients are the Openbravo users for which a given event is going to be monitored.
- An Openbravo background process is permanently checking if the SQL query defined in each of the active rule alerts return any record.
- If that is the case Openbravo creates and returns a new alert instance which is saved in the "Alert Management" window in "New" status.
The number of alerts instances informing about events being monitored happening is shown in the "Top Navigation" menu:
Alerts instances can be visualized and managed in the Alert Management window which is opened by clicking on the "Alert" option of the Top Navigation menu.
Alerts can have 4 different status:
- New - new alerts instances which reflect the events monitored happening.
- Pending - acknowledge alert instances for which an end-user action is pending to be done to get them solved or fixed.
- Ignore - not applicable alert instances which must be ignored.
- Solved - alert instances solved as the event happening is fixed or solved.
The way to manage alerts instances is by manually selecting and moving them to the next or previous status once they are manually acknowledged, ignored or solved.