Projects:Instrusive Alerts/Technical Specifications

Intrusive Alerts - Technical Specifications

Implementation

Intrusive Alerts Infrastructure

The changes needed to Application dictionary in order to be able to support intrusive alerts are:

• AD_AlertRule.Message: Add a message field to the alert rule table, this message will be used in case the alert does not use SQL clause.
• Intrusive type: Add a new type for intrusive alerts.
• AD_AlertRule.allRecipients: A new column that allows not to define the recipients the alert is applicable to, when this column is checked the alert will be generated for every one.
• AD_AlertRule.instancePerUser: When this column is checked an alert will be created per user.
• AD_Alert.AD_User_ID: In case the AD_AlertRule.instancePerUser is checked, this column will contain the user the alert is assigned to.
• AD_Alert.PostPone: This is a date/time column that is used when the user sets the remind in x minutes.

Intrusive Alerts management

org.openbravo.erpCommon.ad_background.PeriodicAlert class is in charge of managing alerts. This class now must be able to mange Intrusive Alerts, to do so it must take into account all the elements defined in the previous section.

The process that checks for alerts and displays the counter in the menu, now must check if there are intrusive alerts, and in this case call the intrusive alert pup-up.

User interface

A pup-up window will be opened with ok and cancel buttons and a remind in x minutes.

Time scheduler

Depending on the definition of background process project.

This will add the ability of creating alert instances regardless any SQL clause, just in a scheduled time.