A new update is available for SAS Compliance Solutions , version 7.1 :
SAS Note 61108 | The \"Could not open a connection to SQL Server...\" error occurs during the compute tier post-configuration step in SAS® Anti-Money Laundering |
SAS Note 61660 | In SAS® Anti-Money Laundering, when you route an unsaved case, you lose either the changes that you made or the new case owner |
SAS Note 61661 | In SAS® Anti-Money Laundering, when you set the case status to \"Case Review,\" all the fields in the Case Details window are no longer editable |
SAS Note 61937 | The Visual Funds Tracker adds original Netflow values to entities each time you click Filter Transactions in SAS® Anti-Money Laundering |
SAS Note 62029 | \"ERROR: Variable EXECUTING_EXT_PARTY_KEY is not on file MST_PREP.CTR_EXECUTING_PTY_TRANS\" occurs if you test a scenario in SAS® Anti-Money Laundering |
SAS Note 62043 | The industry code field is blank in a SAS® Anti-Money Laundering Suspicious Activity Report (SAR) |
SAS Note 62044 | An incorrect entity risk score is used for SAS® Anti-Money Laundering customer risk ranking (CRR) risk calculation |
SAS Note 62145 | \"ERROR: The macro CDD_MAIN_PROCESS will stop executing\" occurs in SAS® Customer Due Diligence |
SAS Note 62159 | The \"Add Entity to Case\" dialog box might not list all alerts to promote to a case in SAS® Anti-Money Laundering |
SAS Note 62162 | Attribute scores might not be displayed in the Customer Risk Rating panel in SAS® Customer Due Diligence |
This list of notes might be incomplete. For a complete list of issues addressed by this hot fix, visit the hot fix page for A5T005 |
Note: A comprehensive list of all SAS hot fixes is available from support.sas.com. You can use the SAS Hot Fix Analysis, Download, and Deployment (SASHFADD) tool to manage your SAS hot fixes.