For some foreign locales, the date filter might not work in the My Alerts and Available Alerts windows.

The following locales might exhibit this behavior:

For example, for a Danish locale, a date value entered in a filter dialog box results in the following exception in the web server log:

2010-11-22 10:15:31,175 ERROR [STDERR] java.text.ParseException: Unparseable
date: "26/10/2010"
2010-11-22 10:15:31,175 ERROR [STDERR]  at
java.text.DateFormat.parse(DateFormat.java:335)
2010-11-22 10:15:31,175 ERROR [STDERR]  at
com.sas.aml.struts.action.NavigateAlerts.setFilters(NavigateAlerts.java:295)
2010-11-22 10:15:31,175 ERROR [STDERR]  at
com.sas.aml.struts.action.NavigateAlerts.execute(NavigateAlerts.java:196)
2010-11-22 10:15:31,175 ERROR [STDERR]  at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.
java:425)
2010-11-22 10:15:31,175 ERROR [STDERR]  at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:228)
2010-11-22 10:15:31,175 ERROR [STDERR]  at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
2010-11-22 10:15:31,175 ERROR [STDERR]  at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:462)

The exception occurs because the Java DateFormat class is being asked to parse a value formatted according to the ICU-derived date format for Denmark; the Danish short-form date format from ICU is dd/mm/yyyy, whereas Java understands the short date format for Denmark as dd-mm-yyyy.

The resulting exception causes the filter not to be applied to the alert list.

Operating System and Release Information

A fix for this issue for SAS Anti-Money Laundering 4.2 is available at:

A fix for this issue for SAS Anti-Money Laundering 5.1_M1 is available at:

A fix for this issue for SAS Anti-Money Laundering 5.1 is available at: