3.1 What’s New in Behavior Detection 8.1.2.10.0
New, changed, and deprecated features of Oracle Behavior Detection are described, with pointers to additional information.
Topics:
The following sections list the new features included in this release:
Anti Money Laundering
The following table describes AML-related new features and enhancements for OFS Behavior Detection Release 8.1.2.10.0:
Feature | Description |
---|---|
Ability to provide Merchant Category Code for Cash and MI Transactions | Now customers can provide merchant category code for Cash and MI transactions also. Earlier this was possible for Wire transactions only. |
Know Your Customer
The following table describes KYC-related new features and enhancements for OFS Behavior Detection Release 8.1.2.10.0:
Feature | Description |
---|---|
Enhancements for Comments Section for Watchlist Disposition in KYC Onboarding Case |
|
Enhancements in KYC Risk Assessment UI |
|
Enhancements for Risk Assessment for Customer without Accounts | For customer without accounts, risk assessment source is now displayed as “Customer without Account” (earlier it was incorrectly shown as “Deployment Initiation”). |
Enhancements for KYC Batch Case in ECM Application | If the KYC analyst overrides the system generated risk score as part of case investigation but later decides to close the case as “Accept System Risk Score”, then the “Risk Score” field under “Case Context” Screen is reverted to original system generated risk score along with required audit history details. |
Enhancements for KYC Model Simulation Feature | Enhancement for “Simulation aggregate and Simulation detailed report” to compare the “simulation risk assessment data against production data” so that it only compares against specific batch run in the simulation pipeline. |
Clean up of Pre-shipped Configuration Files |
|
Currency Transaction Reporting
The following table describes CTR-related new features and enhancements for OFS Behavior Detection Release 8.1.2.10.0:
Feature | Description |
---|---|
Enhancement for Configuring More Than 99 Accounts Per Person | Support for more than 99 accounts in the CTR e-File for an Involved Party: This allows institutions to submit all accounts linked to an involved party with over 99 accounts, ensuring accurate CTR generation and providing FINCEN with a complete view of the report. |
Enhancement for Monetary Instrument Transaction Log Locking Mechanism | We have implemented a locking mechanism for the Monetary Instrument (MI) log. When one user is accessing an MI log, other users will only be able to view it in read-only mode and will not be able to take any actions. |
Enhancement for Adding Expiry Date Field | We have introduced a new feature allowing analysts and supervisors to modify the Exemption Expiry Date directly within the Customer tab on the Exemption Details page. This enhancement enables expiry date updates through the user interface for improved efficiency. |
Other Noteworthy Changes
Note:
As of now, Behavior Detection 8.1.2.10.0 supports HTTPS 1.1 and does not support HTTPS 2.0.Scenario Wizard is decommissioned with the 8.1.2.6.0 release. In the Scenario Wizard folder of the 8129 Installer Package, the associated configuration files are deleted. Due to deletion constraints, the Scenario Wizard folder can still be seen at path <$FIC_HOME/ficweb>. This will be removed in next major installer release.
- Navigate to: #deployed_area/SMLiteWeb and delete SMLiteWeb.war
- Navigate to: #deployed_area/SMLiteWeb/WEB-INF/lib and delete all the jar files
- Navigate to: #deployed_area/SMLiteWeb/lib and delete all the jar files