A new update is available for SAS Fraud Management , version 6.2 :
| KB0044712 | Production rules are not displayed when you open the Production folder on the "Rules" tab |
| KB0044713 | The automation interface in SAS® Fraud Management allows you to check out and assess a closed alert whose contact value is not set |
| KB0044714 | SAS® OnDemand Decision Engine does not start if you change the original column order of a lookup list when uploading list data |
| KB0044715 | A "DB2 SQL Error: SQLCODE=-304, SQLSTATE=22003" error occurs when you try to update an alert on IBM DB2 systems |
| KB0044717 | The "EXPIRATION_TIMESTAMP" field for an alert is set to an invalid value for transactions where the "RQO_TRAN_DATE_CLIENT" field is empty |
| KB0044718 | The database update scripts for SAS® Fraud Management do not hide the characters that you enter in the password prompt |
| KB0044719 | You can promote and deploy an alerting rule to production without configuring the alert type and queue |
| KB0044720 | The search feature on the "Rules" tab does not find rules that contain the word "state |
| This list of notes might be incomplete. For a complete list of issues addressed by this hot fix, visit the hot fix page for M9S008 | |
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.
Nearly 200 sessions are now available on demand in the Innovate Hub.
Watch Now →