Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

When the SARLINK property in the applications configuration (SASAML.CONFIG) file is set to the default value ("enable"), selection of the link on the My Alerts window or the Alert Details window calls the AlertSARsAction module to extract the relevant data and to populate the Alert Regulatory Report screen.

If the SARLINK property is set to "custom", AlertSARsAction forwards to a second module, CustomAlertSARsAction, which builds the window instead.

Currently the code tests for the Property value and forwards that value to CustomAlertSARsAction, which appears at the end of the AlertSARsAction module. As a result, when a Suspicious Activity Report (SAR) link is selected, AlertSARsAction extracts the data and populates the resulting session attributes BEFORE forwarding that data to CustomAlertSARsAction.

Subsequently, CustomAlertSARsAction repeats the process before the .JSP program is called and before the window is built. This double looping occurs every time the Alert Regulatory Report window is called, including refreshes that occur after every modification to the displayed list. Modifications include such tasks as creating a new SAR, returning to the Alert Regulatory Report window from an edited SAR, deleting a SAR, or changing the status from Open to Filed.

Select the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

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