Alert console screens

This topic describes how to manage Alerts using the Alert Console.

Alerts are sent to predetermined queues within the Alert Console and can be assigned to a specific user within that queue. Queues are used to direct specific types of alerts to a specific group of users. Users who belong to a queue use the Alert Console to view and close alerts.

Queues can also be used to prioritize alerts. In the Alert Console, alerts in high priority queues appear at the top of the alert list. You can escalate an alert by assigning it to a queue of higher priority.

In the Alert Console, alerts are listed by identification ID, type, and the date the alerts were raised.

Some alerts are closed automatically when resolved. When the following alerts are resolved, they are automatically closed and removed from your queue:

• INCOMPLETE_PAYMENT_INFO - If an order's payment information is incomplete, the alert is automatically closed when payment information is received.
• BACKORDER_AT_CREATE - If an order is on backorder, the alert is automatically closed once the order is scheduled.
• FAILED_AUTH - If an order is not authorized, the alert is automatically closed once it is authorized.
• ON_FAILURE - If a credit card order fails, but is then cleared, the alert is automatically closed when it moves from failed charge to paid status.

Alert consolidation

You can consolidate alerts based on the day or the hour of occurrence.

When the Sterling™ Order Management System agent framework creates exceptions, they are consolidated by Date, ErrorCode, and so forth. The inbox references for such agent exceptions are these aggregation parameters. These alerts are different than the ones created by the raiseEvent API since one alert can correspond to more than one actual data record. In this case, a context reference such as order number is not applicable.