| A5T020 |
| SAS Compliance Solutions 7.1 |
| Issue(s) Addressed: | Introduced: |
| 58914 | The downloaded CSV data is inconsistent with the data displayed on the Alert Details page in SAS® Anti-Money Laundering |
A5T001 |
| 60039 | A hot fix for SAS® Anti-Money Laundering and SAS® Customer Due Diligence is available |
A5T001 |
| 60786 | Scenario information is not displayed on the Alert Details page when you do not have access to Scenario Administrator in SAS® Anti-Money Laundering |
A5T001 |
| 62274 | An incorrect reason for a suppression is shown in SAS® Anti-Money Laundering |
A5T001 |
| 63556 | Applying a hot fix for SAS® Anti-Money Laundering results in an error during the data definition language (DDL) application |
A5T001 |
| 64794 | Risk score levels do not display correctly on the Customer Details page when more than three risk score levels are in the FSK_LOV table |
A5T001 |
| 64831 | Incorrect values are displayed in the Law Enforcement Contact Date field on a case details or regulatory report page in SAS® Anti-Money Laundering |
A5T001 |
| 64832 | The Time Remaining counters for cases and reports might display incorrect values in SAS® Anti-Money Laundering |
A5T001 |
| 64852 | A newly created case displays an incorrect date in the Date Created field |
A5T001 |
| 64860 | A Suspicious Activity Report (SARX) is rejected by FinCEN because of extra blank spaces in certain report fields |
A5T001 |
| 64861 | A JointReportIndicator tag is not included in an efile report for SARX |
A5T001 |
| 64878 | An efile that is transmitted by Secured Data Transfer Method (SDTM) to the FinCEN is rejected |
A5T001 |
| 64882 | A SARX efile is accepted by the FinCEN although both "Initial report" and "Continuing Activity Report" flags are selected or set to "Y" |
A5T001 |
| 64884 | XML schema errors occur when there are blank fields or a "Not Applicable" selection for data about a financial institution where activity occurred |
A5T001 |
| 67226 | A bar in the bar chart that is displayed in the Analysis section of the Alert Details page disappears when your mouse moves above it |
A5T001 |
| 67257 | SAS® Anti-Money Laundering contains a broken access-control vulnerability |
A5T001 |
| 67258 | SAS® Anti-Money Laundering contains a broken access-control vulnerability |
A5T001 |
| 42491 | A WHERE clause containing the DATEPART() function might be incorrectly formed when passed to Teradata with SAS/ACCESS® Interface to Teradata |
A5T001 |
| 58905 | The fcf_rc_get_entity_score_info.sas macro in SAS® Anti-Money Laundering takes a long time to complete |
A5T001 |
| 58927 | Risk-factor-only alerts are not generated when you run the alert generation process in SAS® Anti-Money Laundering |
A5T001 |
| 59455 | %fcf_agp_codegen incorrectly applies user-specified scenario overrides and causes the alert generation process to fail in SAS® Anti-Money Laundering |
A5T001 |
| 64335 | The fcf_wl_wchk_transform.sas macro incorrectly processes date_of_birth information that is provided by World-Check |
A5T001 |
| 60973 | You cannot connect to your SAS® Anti-Money Laundering database schemas that are defined in metadata after you perform an upgrade |
A5T001 |
| 61033 | The Customer Risk Ranking score in SAS® Anti-Money Laundering is incorrect after you rescore an updated party |
A5T001 |
| 51230 | The "About SAS Anti-Money Laundering" button now returns the current release and latest applied hot fix or maintenance release |
A5T002 |
| 60219 | Deploying SAS® Compliance Solutions 7.1 with non-distributed and stand-alone SAS® LASR™ Analytic Server fails in the configuration process |
A5T002 |
| 60245 | Case status change is not reflected in audit events for cases in SAS® Anti-Money Laundering 7.1 and SAS® Customer Due Diligence 7.1 |
A5T002 |
| 60952 | You can still close an alert in SAS® Anti-Money Laundering even if you do not have that capability specified in SAS® Management Console |
A5T002 |
| 60954 | The alert-generation process fails and an error occurs after you create or update scenarios using the Scenario window in SAS® Anti-Money Laundering |
A5T002 |
| 60957 | SAS® Anti-Money Laundering Query Service REST API does not return a JSON response according to the order specified in the query column position |
A5T002 |
| 60958 | Graphics in the Analysis section of the customer Details window do not display the expected colors in SAS® Anti-Money Laundering 7.1 |
A5T002 |
| 60967 | A copied rule in the SAS® Anti-Money Laundering Customer Due Diligence Rule Administrator is not displayed in the rule list |
A5T002 |
| 60974 | The Suspicious Activity Report (SAR) in SAS® Anti-Money Laundering does not display the "Type of gaming institution" and "Other (specify)" fields |
A5T002 |
| 61008 | The CDD Review page incorrectly shows duplicate records for a rule after you edit the rule in SAS® Customer Due Diligence |
A5T002 |
| 61024 | Scenario Administrator in SAS® Anti-Money Laundering limits the number of replication days to 366 |
A5T002 |
| 61025 | Microsoft Internet Explorer renders only one half of the scoring graph in the Customer Due Diligence component of SAS® Anti-Money Laundering |
A5T002 |
| 61028 | External party details are not displayed on the SAS® Anti-Money Laundering transaction details page |
A5T002 |
| 61029 | The "Risk Factors" tab is missing from the SAS® Anti-Money Laundering "Alert Details" page |
A5T002 |
| 61031 | Users can route alerts, cases, and risk assessments in SAS® Anti-Money Laundering even though they are not configured to have the capability |
A5T002 |
| 61032 | Users can close alerts in SAS® Anti-Money Laundering even though the software is not configured for them to have that capability |
A5T002 |
| 61040 | The codes that you receive when you close an alert do not have a meaningful description in SAS® Anti-Money Laundering 7.1 |
A5T002 |
| 61041 | The account number on the SAS® Anti-Money Laundering transaction details page is an account key value instead of an account number value |
A5T002 |
| 61044 | The value for "Alert Age" in the list of entities on the SAS® Anti-Money Laundering alert triage page is incorrect |
A5T002 |
| 61045 | You can route cases that you do not own in SAS® Anti-Money Laundering |
A5T002 |
| 61046 | Users can access the "Risk Assessment" tab even though the software is not configured for them to have that capability |
A5T002 |
| 61050 | Disposition values are blank when you open a closed Customer Due Diligence (CDD) review |
A5T002 |
| 61082 | The labels that display account information of nodes in the Funds Tracker graph are not displayed correctly in SAS® Anti-Money Laundering |
A5T002 |
| 61090 | You cannot create a Suspicious Activity Report from a case when the subject does not have an associated account in SAS® Anti-Money Laundering |
A5T002 |
| 61092 | SAS® Anti-Money Laundering does not validate the user name that you enter in the "Route to user" field if that name is defined in SAS® metadata |
A5T002 |
| 61103 | Adding an entity to a case in SAS® Anti-Money Laundering results in a "Conflict when creating an object" message |
A5T002 |
| 61104 | When you click the Reports menu in the Anti-Money Laundering Regulatory Reports folder, you see "User is not authorized to access this page" |
A5T002 |
| 61106 | Users with "Route My Regulatory Reports for Anti-Money Laundering" capability in SAS® Management Console can route any regulatory report |
A5T002 |
| 61113 | A Customer Due Diligence Review cannot be saved or edited in SAS® Anti-Money Laundering |
A5T002 |
| 61114 | The SAS® Anti-Money Laundering Customer Due Diligence Reviews list contains duplicate information and the total count is incorrect |
A5T002 |
| 61122 | In SAS® Anti Money Laundering, you can route cases from the All Available Cases list even when you are not the owner of the case |
A5T002 |
| 61136 | The risk-classifier code value does not match the expected value in SAS® Anti-Money Laundering |
A5T002 |
| 61137 | The screen validation does not reflect the correct risk-classifier type in SAS® Anti-Money Laundering |
A5T002 |
| 61138 | Log files are not accessible in SAS® Anti-Money Laundering application when Transport Layer Security (TLS) is configured |
A5T002 |
| 61139 | The SAS® Anti-Money Laundering user interface does not notify you when the alert-generation process is running |
A5T002 |
| 61140 | Customer, Account, or Transaction names are not displayed in SAS® Anti-Money Laundering when they contain a dot character |
A5T002 |
| 61141 | An error occurs if you manually create a Customer Due Diligence (CDD) review that does not contain scoring data |
A5T002 |
| 61177 | The creation time for a report is truncated (missing) in the creation date in SAS® Anti-Money Laundering |
A5T002 |
| 61102 | Some entities with active alerts are not listed in the Entity Triage listing after you run the alert generation process in SAS® Anti-Money Laundering |
A5T002 |
| 59454 | The alert generation process in SAS® Anti-Money Laundering might perform slowly when copying transactions for alerts entities |
A5T002 |
| 60959 | The Suspicious Activity Report (SAR) form fails to validate in SAS® Anti-Money Laundering, even though the data is correct |
A5T002 |
| 60965 | The Suspicious Activity Report form fails to validate when the Taxpayer Identification Number type is unknown in SAS® Anti-Money Laundering |
A5T002 |
| 61085 | The value for "Form of Identification for Subject Unknown" in a Suspicious Activity Report is blank in the e-file report in SAS® Anti-Money Laundering |
A5T002 |
| 61097 | The customer risk ranking (CRR) program fails when SAS® Customer Due Diligence uses Microsoft SQL Server |
A5T002 |
| 62693 | The SAS® Compliance Solution alert-generation process fails in the FCF_REPLICATE_EXT_TRANSACTIONS.SAS macro after you apply Hot Fix A5T002 |
A5T003 |
| 61123 | All transactions are exported to a CSV file instead of only the transactions in the SAS® Anti-Money Laundering entity transactions list |
A5T004 |
| 61142 | The endpoint values for the Funds Tracker slider are misleading in SAS® Anti-Money Laundering |
A5T004 |
| 61530 | ALERT - "The maximum length of this input field has been exceeded" occurs when you enter text in "Step 5 - Narrative" in Suspicious Activity Reports |
A5T004 |
| 61532 | The transaction summary associated with an External Party alert shows an incorrect value on the Entity Details page in SAS® Anti-Money Laundering |
A5T004 |
| 61548 | Search by Case results are not sorted alphabetically in SAS® Anti-Money Laundering |
A5T004 |
| 61550 | In SAS® Anti-Money Laundering, when you validate a Suspicious Activity Report, an S419 error might occur |
A5T004 |
| 61552 | The "User is not authorized to perform this action" error occurs when you attempt to view an alert in SAS® Anti-Money Laundering |
A5T004 |
| 61556 | The "Route" action might be incorrectly disabled or enabled in SAS® Anti-Money Laundering 7.1 |
A5T004 |
| 61557 | Saving a scenario in SAS® Anti-Money Laundering results in "Scenario XXXXXX update failed" or "Other user may have changed this scenario..." errors |
A5T004 |
| 61569 | Users without permission to view cases can still see case information when using the Search by Cases functionality in SAS® Anti-Money Laundering |
A5T004 |
| 61571 | In SAS® Anti-Money Laundering, the contact information displayed in regulatory reports might be different from the information in the e-file |
A5T004 |
| 61574 | Saving a scenario in SAS® Anti-Money Laundering results in "Form Errors. Please correct..." or "Name must be populated and unique" errors |
A5T004 |
| 61575 | In the SAS® Anti-Money Laundering FinCEN Suspicious Activity Report user interface, the date range fields are populated with incorrect values |
A5T004 |
| 61579 | You cannot edit any reviews for Customer Due Diligence even if the correct capability is enabled in the SAS® Anti-Money Laundering metadata |
A5T004 |
| 61580 | The Money Laundering Risk Score column shows in the Search results even if you do not select the preference in SAS® Anti-Money Laundering |
A5T004 |
| 61581 | "ERROR: CLI describe error...SQLSTATE=42501" occurs when you add a new business unit in SAS® Anti-Money Laundering |
A5T004 |
| 61582 | SAS® Anti-Money Laundering contains cross-site scripting security vulnerabilities |
A5T004 |
| 61583 | SAS® Anti-Money Laundering does not support multiple institutions in the Suspicious Activity Report |
A5T004 |
| 61584 | Attempting to modify manual parties that are added to a SAS® Anti-Money Laundering report fails and returns "An unexpected server error has occurred" |
A5T004 |
| 61585 | You can edit some fields in a Suspicious Activity Report (SAR) that you do not own in SAS® Anti-Money Laundering |
A5T004 |
| 61586 | "Retail foreign exchange dealer" and "SRO Futures" in Suspicious Activity Reports are incorrectly mapped in SAS® Anti-Money Laundering |
A5T004 |
| 61591 | The alert run date in SAS® Anti-Money Laundering always shows that the time is midnight (00:00:00) |
A5T004 |
| 61108 | The "Could not open a connection to SQL Server..." error occurs during the compute tier post-configuration step in SAS® Anti-Money Laundering |
A5T005 |
| 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 |
A5T005 |
| 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 |
A5T005 |
| 61937 | The Visual Funds Tracker adds original Netflow values to entities each time you click Filter Transactions in SAS® Anti-Money Laundering |
A5T005 |
| 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 |
A5T005 |
| 62043 | The industry code field is blank in a SAS® Anti-Money Laundering Suspicious Activity Report (SAR) |
A5T005 |
| 62044 | An incorrect entity risk score is used for SAS® Anti-Money Laundering customer risk ranking (CRR) risk calculation |
A5T005 |
| 62145 | "ERROR: The macro CDD_MAIN_PROCESS will stop executing" occurs in SAS® Customer Due Diligence |
A5T005 |
| 62159 | The Add Entity to Case dialog box might not list all alerts to promote to a case in SAS® Anti-Money Laundering |
A5T005 |
| 62162 | Attribute scores might not be displayed in the Customer Risk Rating panel in SAS® Customer Due Diligence |
A5T005 |
| 62164 | The Solr index for Alert Status is not updated when a case is closed in SAS® Anti-Money Laundering |
A5T005 |
| 62165 | You can incorrectly create two CDD Reviews for the same customer if the CDD Review has a custom status |
A5T005 |
| 62166 | Branch data might be incorrect when you select a branch in SAS® Anti-Money Laundering |
A5T005 |
| 62168 | All notes do not appear when one note has a large number of attachments in SAS® Anti-Money Laundering |
A5T005 |
| 62180 | SAS® Enterprise Case Management displays an "unable to load" error when you set the value of the ECM.Policy.FinancialItemMigration property to false |
A5T005 |
| 62217 | The "Error checking in CDD Reviews" pop-up message is displayed in SAS® Customer Due Diligence |
A5T005 |
| 62219 | You receive the "User name is invalid" message when you try to route an entity to a user in SAS® Anti-Money Laundering |
A5T005 |
| 62220 | Graphics do not appear in the Analysis section of account pages in SAS® Anti-Money Laundering |
A5T005 |
| 62221 | You cannot claim an entity in SAS® Anti-Money Laundering |
A5T005 |
| 62227 | Entities on the Entity Triage page might show inconsistent information in SAS® Anti-Money Laundering |
A5T005 |
| 62228 | The "One and only one prep data set variable must be selected as 'By Variable'" message might occur when you attempt to synchronize a prep data set |
A5T005 |
| 62229 | An option to filter by a status of Closed is available on the CDD Reviews page, even though you cannot view a closed CDD Review |
A5T005 |
| 62230 | The "FCF_REPLICATE_TRANSACTIONS is being skipped" note might occur with newly generated alerts |
A5T005 |
| 62231 | You might see "WARNING: Apparent symbolic reference DT_AGP_ROUTE_ENTITY not resolved" in the alert generation process log |
A5T005 |
| 62232 | ALERT - SAS® Anti-Money Laundering contains a cross-site scripting vulnerability |
A5T005 |
| 62233 | The Transaction Details page might display the wrong date for a transaction |
A5T005 |
| 62833 | The transactions_prep.sas source code does not consider scenario duration parameters in the SAS10206, SAS10220, SAS10225, and SAS10230 scenarios |
A5T005 |
| 51185 | A macro exists in SAS Anti-Money Laundering that enables you to display the current release and the latest hot-fix that is applied |
A5T006 |
| 62712 | The "SAR Data Validation Error Report" in SAS® Anti-Money Laundering might not include data for the subject that is responsible for an error |
A5T006 |
| 62808 | A filter applied on the Alert Age column on the Entity Triage page in SAS® Anti-Money Laundering might not work |
A5T006 |
| 62901 | Text that is entered in the "Reason" field for suppressing an alert might truncate without warning if the text is more than 255 characters in length |
A5T006 |
| 62919 | Error messages are seen in SAS® Anti-Money Laundering after you open either a case or an entity that has 10 or more related cases |
A5T006 |
| 62920 | SAS® Visual Analytics Hub does not show an access link for SAS® Anti-Money Laundering even when the "View AML Hub Link" option is enabled |
A5T006 |
| 62936 | Transactions that are associated with alerts generated from Watch List Entities scenarios are not displayed in SAS® Anti-Money Laundering |
A5T006 |
| 62938 | The Apache Ant script that is called in SAS® Anti-Money Laundering Hot Fix A5T005 fails when it attempts to load the metadata package |
A5T006 |
| 62939 | The SAS® Customer Due Diligence customer risk ranking (CRR) process takes a long time to complete |
A5T006 |
| 62941 | The preference to hide the Money Laundering Score (MLS) in SAS® Anti-Money Laundering is not functioning properly |
A5T006 |
| 62954 | Your selected entries on the Entity Triage page in SAS® Anti-Money Laundering are deselected after you scroll up or down in a table |
A5T006 |
| 62961 | The "Netflow" value in the Visual Funds Tracker in SAS® Anti-Money Laundering is incorrect after double-clicking the "Refresh Transactions" button |
A5T006 |
| 62966 | An External Party page does not open in SAS® Anti-Money Laundering and you see a "Requested object not found" notice |
A5T006 |
| 63032 | Characters from various languages might not display as expected in the SAS® Anti-Money Laundering user interface |
A5T006 |
| 63034 | The party name is not displayed for parent entities on the left-hand side of the "Associated Entities" section in SAS® Anti-Money Laundering |
A5T006 |
| 63035 | "No localised resource strings . . ." or "Rest error for resources . . . " errors occur in the SAS® Anti-Money Laundering UI |
A5T006 |
| 63063 | Report data is corrupted if two reports are edited in SAS® Anti-Money Laundering in the same browser window |
A5T006 |
| 63066 | You might see unexpected date values on the Account Details or Customer Details pages in SAS® Anti-Money Laundering |
A5T006 |
| 63171 | Numeric values in data-grid columns align to the left when you use the Hebrew-language setting in a browser for SAS® Anti-Money Laundering |
A5T006 |
| 63173 | Data in list boxes and text boxes in SAS® Anti-Money Laundering can contain extra spaces when you use the Hebrew-language setting in a browser |
A5T006 |
| 63175 | The "Save as grid defaults" selection does not retain filters and sort orders that you apply to data-grid columns for lists related to reports |
A5T006 |
| 63176 | Owner assignments for alerted entities are incorrect after you apply Hot Fix A5T005 for SAS® Anti-Money Laundering |
A5T006 |
| 63223 | An incorrect value is in the "Entity Type" field in the "Summary" section on the CDD Reviews page of SAS® Anti-Money Laundering |
A5T006 |
| 63228 | The %fcf_add_to_sar90_cases compiled macro generates a warning message although there are no scenarios to activate SAR-90 cases |
A5T006 |
| 61077 | The Apache Solr delta-import command fails and generates errors in SAS® Anti-Money Laundering 7.1 |
A5T007 |
| 63080 | The "Validate Report" button does not validate a postal code as expected in SAS® Anti-Money Laundering |
A5T007 |
| 63081 | Clicking "Validate Report" results in an unexpected "HTTP Status 500" pop-up error message when the < or > characters are used in a SARX report |
A5T007 |
| 63082 | You receive an unexpected C10 Fatal error when you validate a SARX report in SAS® Anti-Money Laundering |
A5T007 |
| 63097 | You receive a transcoding error while restoring a table after you apply Hot Fix A5T006 in SAS® Anti-Money Laundering |
A5T007 |
| 63099 | You see a "CLI execute error . . ." regarding the FSK_RC_REPORT_ENTITY_BRIDGE table in SAS® Anti-Money Laundering after you apply Hot Fix A5T006 |
A5T007 |
| 63266 | You cannot route entities in SAS® Anti-Money Laundering when you have only the Route Any Entity capability |
A5T007 |
| 63267 | A blank value in field 94 "Filing institution contact phone number. . ." in a Suspicious Activity Report (SARX) causes an A4 Fatal FinCEN e-file error |
A5T007 |
| 63268 | You see a warning when you append a REPLICATION_DATES table to DB_KC.fsk_REPLICATION_DATES in a relational database management system (RDBMS) |
A5T007 |
| 63269 | The "Employee Indicator" field does not set to the default value for an entity when you want to add the entity to a case in SAS® Anti-Money Laundering |
A5T007 |
| 63270 | The "Date Closed" field does not update after a case is closed in SAS® Anti-Money Laundering |
A5T007 |
| 63271 | You click the "Activate" or "Deactivate" button for a scenario in SAS® Anti-Money Laundering, but the “LSTUPDATE_DATE” field does not update |
A5T007 |
| 63272 | The %FCF_RISK_RANKING macro routine might generate "WARNING: The variable acc_number in the DROP, KEEP, or RENAME list has never been referenced" |
A5T007 |
| 63273 | The extract, transform, load (ETL) code to process the OFAC watch list might not preserve information about the place of birth |
A5T007 |
| 63274 | A transaction reference number displays outside of the Transaction Type Information box in SAS® Anti-Money Laundering |
A5T007 |
| 63346 | SAS® Anti-Money Laundering is unresponsive when you try to remove or activate an alert in a case |
A5T007 |
| 63347 | You can create a case or add alerts to cases of an entity that you do not own in SAS® Anti-Money Laundering |
A5T007 |
| 63359 | You see warnings about differing field lengths for ACTUAL_VALUES_TEXT and PRIMARY_ENTITY_NUMBER variables after you run the alert generation process |
A5T007 |
| 63361 | The Edge Type Code column always contains an "Outbound Transaction" value on the Visual Funds Tracker page in SAS® Anti-Money Laundering |
A5T007 |
| 63364 | The SAS® Anti-Money Laundering alert generation process fails after the ctr_cico_ctc_header scenario header is used |
A5T007 |
| 63366 | SAS_Server81 does not start successfully after you deploy SAS® Anti-Money Laundering on multiple business units |
A5T007 |
| 63367 | Duplicate transactions appear in the SAS® Anti-Money Laundering Funds Tracker graph |
A5T007 |
| 63368 | Transaction times in the SAS® Anti-Money Laundering Funds Tracker transactions list are incorrect |
A5T007 |
| 63369 | Older transactions for the same account are missing from the Funds Tracker in SAS® Anti-Money Laundering |
A5T007 |
| 63393 | An "Unexpected next character . . ." error occurs when an "Additional details" data grid contains column names in Hebrew in SAS® Anti-Money Laundering |
A5T007 |
| 63456 | Some scenarios fail to run in SAS® Anti-Money Laundering 7.1.5 when segmentation is enabled |
A5T007 |
| 63528 | ALERT - The web application does not display anything other than errors or blank web pages in SAS® Anti-Money Laundering when Hot Fix A5T007 is not installed |
A5T007 |
| 63363 | The IdentificationPresentUnknownIndicator element name is not included in the XML Source window in SAS® Enterprise Case Management |
A5T008 |
| 64040 | You receive a "Bad Request" error message after you click "Additional details" on a details screen in SAS® Anti-Money Laundering |
A5T008 |
| 64245 | No error appears when you click Validate Report for the SARX, and "(none selected)" is in the "Type of filing" field in the Home section of the report |
A5T008 |
| 64292 | Adding a caseStatusClosed preference in SAS® Anti-Money Laundering does not close the case if it is used |
A5T008 |
| 64312 | A phone number and contact date for law enforcement (LE) are missing from the Suspicious Activity Report XML |
A5T008 |
| 63357 | An alert generation process fails after you execute custom scenario headers and you have installed SAS® Anti-Money Laundering 7.1 Hot Fix 5 (A5T006) |
A5T009 |
| 63481 | The alert generation process (AGP) fails at the FCF_UPDATE_ALERT_HISTORY step in SAS® Anti-Money Laundering |
A5T009 |
| 64419 | Clicking "Export" on the Scenarios tab in SAS® Anti-Money Laundering sets both segmentsEnabledInd and btlEnabledInd to null |
A5T009 |
| 64791 | Comments and changes in the Required Review Steps panel for a CDD review might not be saved |
A5T009 |
| 64792 | A report is not created after you select the "Report Required" check box in the "Edit Relationship" window for an external party |
A5T009 |
| 64793 | The "Close Date" field is missing a date in the result set for an alert search |
A5T009 |
| 64795 | Accepting a risk assessment in SAS® Anti-Money Laundering results in a key constraint error |
A5T009 |
| 64796 | The full file path for an attachment is shown in the REST response in SAS® Anti-Money Laundering 7.1 |
A5T009 |
| 64798 | The Alert Threshold messages associated with SAS10601 and SAS10604 are incorrect in SAS® Anti-Money Laundering |
A5T009 |
| 64799 | The date check for correspondent banking scenarios is incorrect and results in inaccurate alerts being created in SAS® Anti-Money Laundering |
A5T009 |
| 64830 | You are unable to save Suspicious Activity Report (SAR) subject information in SAS® Anti-Money Laundering if a subject ID number contains asterisks |
A5T009 |
| 64850 | The "Historical Transactions" selection for a transaction grid on a case details page is not working as expected |
A5T009 |
| 64863 | You are able to route entities, cases, or CDD reviews to a queue that was deleted |
A5T009 |
| 64883 | "Requested object not found" is displayed when you search for external entities with attachments in a global search in SAS® Anti-Money Laundering |
A5T009 |
| 65341 | The "Route to user" option generates a "User name is invalid" message when SAS® Anti-Money Laundering 7.1 is used in Microsoft Internet Explorer 11 |
A5T009 |
| 65722 | You cannot enter more than 35 characters in the "Description" field for a report |
A5T010 |
| 65198 | A SAS® Anti-Money Laundering upgrade fails with the HTTP error "...Application 'Compliance Solutions Mid' does not exist..." |
A5T010 |
| 65353 | A Netflow amount in the Visual Funds Tracker in SAS® Anti-Money Laundering 7.1 is incorrect after the account page is launched multiple times |
A5T010 |
| 65493 | You see an "AML: invalid argument" error in SAS® Anti-Money Laundering 7.1, even though the "Route to user" operation completes successfully |
A5T010 |
| 65608 | The SAS® Compliance Analytics process is removed from the SAS® Anti-Money Laundering solution |
A5T010 |
| 65713 | You can close cases in SAS® Anti-Money Laundering 7.1 even though you do not have the "Close My Cases" capability |
A5T010 |
| 65736 | A new feature to log user interactions in the user interface is added in SAS® Anti-Money Laundering 7.1 |
A5T010 |
| 65738 | The value in the "Value" field for a rule might be truncated in CDD Reviews |
A5T010 |
| 65749 | You cannot correct a regulatory report that was accepted in SAS® Anti-Money Laundering 7.1 after you install Hot Fix A5T009 |
A5T010 |
| 65750 | You encounter a DataAccessException error when you have more than 1,000 queues in SAS® Anti-Money Laundering |
A5T010 |
| 65752 | SAS® Anti-Money Laundering contains a privilege escalation vulnerability |
A5T010 |
| 66581 | The alert generation process in SAS® Anti-Money Laundering stops responding with "WARNING: Apparent symbolic reference SCN_NMn not resolved" |
A5T010 |
| 67225 | SAS® Anti-Money Laundering issues that are addressed in Hot Fix 11 (A5T014) |
A5T010 |
| 67231 | Some transactions that contributed to the generation of account or household alerts are not replicated as expected in SAS® Anti-Money Laundering |
A5T010 |
| 67233 | The Run Date and Create Date fields in the Targeted Search Results data grid do not contain the correct information |
A5T010 |
| 67256 | SAS® Anti-Money Laundering contains a cross-site scripting vulnerability |
A5T010 |
| 66099 | The message "An unexpected data access error has occurred" appears in the user interface when you try to view audit events for CDD Reviews |
A5T011 |
| 66112 | SAS® Anti-Money Laundering contains a vulnerability in a REST endpoint |
A5T011 |
| 66113 | A read-only case or report page might indicate that it had been modified after you click the "Notes" button in SAS® Anti-Money Laundering |
A5T011 |
| 66485 | SAS® Anti-Money Laundering 7.1 includes a vulnerable third-party library |
A5T012 |
| 66532 | The SAS® Anti-Money Laundering user interface becomes unresponsive after you click the "Notes" link |
A5T012 |
| 66583 | The alert generation process fails due to insufficient memory while the fcf_agp_codegen macro is running in SAS® Anti-Money Laundering |
A5T012 |
| 66586 | The Transmission ID is not populated for the CTR XML regulatory report when the rc_efile_fincen_sdtm.sas driver runs in SAS® Anti-Money Laundering |
A5T012 |
| 66592 | You can access regulatory reports even though you do not have sufficient assigned capabilities for them for your user account |
A5T012 |
| 66593 | You can route an object to a queue for a user who does not have the relevant privileges to work on the object in SAS® Anti-Money Laundering |
A5T012 |
| 66594 | The "Time Remaining" value that is displayed on a Case Details page continues to decrement for a closed case |
A5T012 |
| 66595 | The HTTP response from a REST call displays the full path for where an attachment object is stored |
A5T012 |
| 66597 | SAS® Anti-Money Laundering contains a broken access-control vulnerability |
A5T012 |
| 66602 | The default minimum values for the lock and unlock preference settings in SAS® Anti-Money Laundering might be too restrictive |
A5T012 |
| 67251 | The alert generation process fails when there are long scenario parameter values that have a length greater than 200 bytes |
A5T013 |
| 67344 | You are not able to route an entity, case, regulatory report, or CDD Review to a user in SAS® Anti-Money Laundering after applying Hot Fix 10 |
A5T015 |
| 67875 | Summary of issues that are addressed in Hot Fix 12 (A5T016) for SAS® Anti-Money Laundering 7.1 |
A5T016 |
| 68662 | A broken access-control vulnerability occurs with SAS® Anti-Money Laundering REST service endpoints |
A5T018 |
| 66403 | The prior report document control number is incorrectly set to read-only in a Designation of Exempt Person (DOEP) report |
A5T019 |
| 68815 | Opening a watchlist alert displays the error "Expression 'undefined' in attribute 'options' used with the directive 'amlGrid' is non-assignable!" |
A5T019 |
| 68891 | A Log4j version 1.2 vulnerability (when using JMSAppender) is identified in SAS® Anti-Money Laundering |
A5T019 |
| 69274 | You are unable to save a Suspicious Activity Report in SAS® Anti-Money Laundering and "The 'No known accounts involved' must be checked..." occurs |
A5T019 |
| 69275 | The Customer Risk Ranking Scoring History data grid contains scores and reviews that do not belong to the customer in SAS® Anti-Money Laundering |
A5T019 |
| 69280 | Corroborative statements to filer XML element tags are incorrectly included in the generated Suspicious Activity Report in SAS® Anti-Money Laundering |
A5T019 |
| 69287 | Birth date information for the External Party in the SAS® Anti-Money Laundering user interface is inconsistent with the value stored in the database |
A5T019 |
| 69288 | Posted Date information displayed on the SAS® Anti-Money Laundering Transaction Details page is inconsistent with the actual value in the database |
A5T019 |
| 69289 | The values in the Beneficiary columns in the Alerted Transactions and Historical Transactions data grids are incorrect in SAS® Anti-Money Laundering |
A5T019 |
| 69290 | The SAS® Anti-Money Laundering SARX form is updated to align with the latest FinCEN changes |
A5T019 |
| 69291 | The SARX form does not mark the page as "dirty" when populating "Attachment to efile" in SAS® Anti-Money Laundering |
A5T019 |
| 69292 | You encounter the "Expecting a ;" error message when processing Risk Ranking in the SAS® Anti-Money Laundering alert generation process |
A5T019 |
| 69293 | Attachments in the Notes section of regulatory reports are not listed in the "Attachments to E-file" drop-down list in SAS® Anti-Money Laundering |
A5T019 |
| 69295 | You are unable to correct inconsistent information in the SARX report after applying the SAS® Anti-Money Laundering Hot Fix A5T016 |
A5T019 |
| 69296 | The Time Remaining value in the Related Cases data grid on the Case Details page is 0 after applying SAS® Anti-Money Laundering Hot Fix 12 |
A5T019 |
| 69297 | You receive a B18 filing type error message when validating Suspicious Activity Reports (SARX) in SAS® Anti-Money Laundering |
A5T019 |
| 70327 | You are unable to view the list of cases associated with an entity in SAS® Anti-Money Laundering |
A5T020 |
| NOTE: AML 7.1 Hotfix 15 should ONLY be installed on SAS AML 7.1 on SAS 9.4M7. Please refer to the System Requirements for Anti-Money Laundering Middle-Tier requirements section for details on this requirement. |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
General Information about Hot Fixes