This topic lists the changes to the Alerts feature.
Table 1. Changes to Alerts.
| 9.3 fix pack wsc.alert.AlertNotificationDetails
wsc.alert.ManageAlertNotificationDetails
|
9.4 release wsc.components.alerts.AlertDetails
wsc.components.alerts.AlertNotificationDetails
wsc.components.alerts.AlertTypeList
wsc.components.alerts.AlertTypePanel
wsc.components.alerts.ManageAlertNotificationDetails
|
- Alerts displayed are not grouped by exception types.
- Alerts are fetched by calling
getExceptionListForUser API
for (YCD_HOT_PICK and YCD_NEAR_SLA)
exception types. "Pick" is displayed as an action for alerts of these
extension types. Otherwise, "Resolve" is displayed.
|
- Alerts are listed in a tree structure and are grouped by exception
types. Each individual category of alerts is expandable and collapsible.
When a category is expanded, a paginated view of the alerts for that
category is displayed, only when the user is subscribed to the queues
to which the alerts belong.
- Alerts are fetched by calling
getExceptionList API
and it supports all exception types. The "Pick", "Pack", or "Resolve"
actions are displayed for all alerts.
|
How it affects you
As a store associate,
you can see alerts of any type and perform multiple actions such as
Pick, Pack, and Resolve, on each alert.
As a store implementer,
you must re-customize the Alerts UI appropriately to incorporate the
extensions to alerts in the previous installation.