You might experience slow performance when you click the All Available transaction tab within the Alert Details window. The SQL queries that are used to return the transactional data to the user interface are causing the problem.

The following changes have been made to improve performance:

1. Transactions are listed in descending order by date. If the list is limited by "max rows", the most recent, and therefore likely relevant, transactions are listed.
2. There is a configurable age limit to transactions that are listed on the All Available tab, based on the current date. As the alert ages, the overlap between the alert period and the All Available transactions list range is diminished. Provided the alert is investigated in a timely fashion, this is presumably not an issue. The query is changed to CORE only, and it tries to keep to a fixed date range.
3. KC transactions are not included in the All Available queries. Provided that the age limit is within the data range in CORE, all KC transactions that would be within the date range are also in CORE. So, the inclusion of KC transactions in the query is unnecessary.
4. The date range that is applied to the All Available transactions list is displayed.
5. Party alerts list only transactions on the All Available tab for accounts where the party is a primary owner.
6. There are separate maximum row limits per tab. On the All Available tab, the maximum row limit is combined with the date range constraint.

Performance should be improved generally on the Alert Details page, regardless of which transaction tab is displayed, but most noticeably when the All Transactions tab is displayed.

Transactions are listed in date descending order.

A transaction age limit is applied to the All Available transactions tab. The applicable date range is displayed when that tab is selected.

The transaction list in the attachment for an alert e-mail shows a transaction count. The missing transaction count indicates that the listed transactions might not be a full list of those matching the applicable criteria.

Operating System and Release Information

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: