�Description
OFS BD Application Pack v8.1.2.0.0 Minor Release #2 8.1.2.2.0 (ID 34332109)
This release of OFS BD Application Pack is cumulative of all enhancements and bug fixes done since the v8.1.2.0.0 release.
�Prerequisites
Refer to the below pre-requisites:
� Before applying OFSBD 8.1.2.2.0, it is required to install OFSBD 8.1.2.0.0. For detailed instructions on installing this OFS BD Release, see OFS BD Application Pack Installation and Configuration Guide 8.1.2.2.0.
� Apply the patch for Bug 33865657. This is the OFSAAI 8.1.2.1.0 RELEASE #1 (8.1.2.1.0)
� Apply the patch for Bug 34278179. This is the consolidated fixes of all issues identified in AAI on 8121 ML.
�How to Apply This Patch?
For detailed instructions on installing this OFS BD release, see OFS Behavior Detection Installation Guide 8.1.2.2.0.
�
�About This Release
�This section describes the new features, bugs addressed, and known issues in this release of OFS Behavior Detection.
�Topics:
For detailed information on how to use this release, see the various OFS BD Application Pack User Guides.
For detailed information on how to install, configure, and use this release, see Oracle Financial Services Behavior Detection Applications Pack Installation Guide from the OHC Documentation Library.
For more information on the OFS AAI requirements, see OFS Advanced Analytical Applications Infrastructure Application Pack in the OHC Documentation Library.
The 8.1.2.2.0 release provides the following new features and enhancements:
� The following existing scenarios have been modified in 8.1.2.2.0 to implement Functional Currency.
o Anomalies in ATM, Bank Card: Foreign Transactions �Customer Focus
o Structuring: Avoidance of reporting thresholds �Account Focus
o Rapid Movement of Funds - All Activity �Account Focus
o High-Risk Transactions: High-Risk Geography �Account Focus
For more details refer to the OFSBD 8.1.2.2.0 Technical Scenario Description Guides.
� Behavior Detection Data Model updated as per ISO20022 to consume the granular payment information new standard offers. For more details, see the OFSBD 8.1.2.2.0 Data Model Guides.
� OFS Real-Time Fraud has been updated in the following ways. For more information, see the 8.1.2.2.0 Real Time Fraud Guides.
o Support for card transactions has been added to OFS Real-Time Fraud. The update provides data model support and a redesigned User Interface, allowing users visibility into card transactions, accounts, and relationships.
o New user groups have been added to OFS Real-Time Fraud, allowing users to be assigned as analysts, senior supervisors, and administrators, providing enhanced access control.
o Support for access control and alert allocation by jurisdiction and domain has been added to OFS Real-Time Fraud.
o A new scenario, Sudden Surge in Credit Utilization has been added to OFS Real-Time Fraud, allowing users to detect unusual changes in card account balances.
o The Analyst workflow for OFS Real-Time Fraud has been improved, including get next work allocation for faster disposition of alerts.
� OFS Know Your Customer (KYC) has been updated in the following ways. For more information, see the 8.1.2.2.0 KYC Guides.
o New Parameters added from the KYC UI will now be present in the respective history table. Also, values added or edited in the Rule Based Risk Assessment UI are now captured in the Audit history table.
o Next Periodic Review Date in the KYC Case Details Section will be populated post-case closure.
o The Risk Score Expiration Date field has been removed from the KYC Case Details Section.
o The KYC UI has been updated to add a new Risk Score for Parameter / Rule value screen. To add metadata to the kdd_code_set_trnln table, upload the data using the Excel Upload utility.
o KYC is integrated with Compliance Studio to offer the ability to perform accelerated Re-review using the Customer Segmentation & Anomaly detection model.
o KYC Assessments Page and CTR have been migrated to OJET and offered with a new wave design for enhanced UI/UX experience.
o Stage Party Party-related data movement to ECM is provided as part of manual KYC case promotion.
o PEP_FL field population enabled in ECM during manual KYC case promotion.
The following bugs have been fixed in OFS Behavior Detection Release 8.1.2.2.0.
Table 1: List of Resolved Issues
|
Component |
Bug ID |
Resolution |
|
BD |
34142575 |
BDF 8.1.1.x partytopartyrelationship mappings updated. |
|
BD |
34262235 |
BDF 8.1.1.x customer identification document mappings updated. |
|
BD |
34287109 |
func_crncy_cd attribute included in wire_trxn_wrp |
|
BD |
34478121 |
BDF 8.1.2 task failure to load the table cust_acct due to missing customeraccountrole has been resolved. |
|
BD |
34506944 |
In OFSBD 8.0.7.1.25 - external entity monthly summary table was not being updated correctly This has been updated to only consider the current month data and update for current month instead of calculating for previous months as well. |
|
BD |
34608160 |
A max of 70 characters should be fed to prevent data from source getting truncated while inserting derived address. |
|
ECM-UI |
34151184 |
Duplicate record creation in interested party grid of KYC case in ECM has been removed. |
|
KYC-UI |
34156298 |
History table shows updated value after updating risk score. |
|
KYC-UI |
34190043 |
Changing active flag on multiple rules does not generate duplicate history entries |
|
RTF |
34302294 |
In RTF 8.0.8.0.104 UI when user applies filter "held" it displays transactions with "held" status only, |
|
RTF |
34364833 |
In the RTF UI, when user applies filter "held" it displays transactions only with "held" status. |
|
RTF |
34531910 |
RTF filter removal after click assign has been resolved. |
�The known issues/limitations in OFS Behavior Detection Release 8.1.2.2.0. are as follows.
Table 2: List of Known Issues
|
Component |
Bug ID |
Description |
|
CTR |
34618750 |
Locking functionality for mi screen is not working as expected. |
|
CTR |
34608417 |
Location displayed instead of location id in persons involved tab transaction. |
|
CTR |
34593842 |
Saving CTR person involved and financial institutions, without mandatory save, does not work. |
|
CTR |
34593823 |
Exemption id is missing in the pop up when exemptions created in ojet. |
|
CTR |
34562161 |
Bus domain is displayed in ojet instead of business domain under exemptions. |
|
CTR |
34556287 |
Icons are missing for change transaction fi , edit. |
|
CTR |
34556156 |
Add, edit, remove icons are missing in persons involved tab in ojet |
|
CTR |
34532651 |
Icons for advanced search, action and email is missing under exemptions ->search and list in ojet framework |
|
CTR |
34268698 |
Expand and collapse functionality should be on lhs for doep context page. |
|
CTR |
34258268 |
Unable to export e-files when user selects an option from views drop down and takes 'export to excel' action. |
|
CTR |
34136183 |
E-files for submission is not selected by default in view [ojet doep e-file list]. |
|
CTR |
34095062 |
No alert shown to restrict user for edit and add option if more than one mit is selected. |
|
AML |
33410918 |
Previously, the Threshold Editor (Admin Tools UI) could not run the Sequence Matcher scenario with custom threshold for TEST run. This issue has been fixed. Now, users can run the Sequence Matcher scenario with custom threshold for TEST run. Existing issues are as follows: � The fix does not work for an existing custom threshold set of Sequence Matcher scenarios. In this case, the user would have to create new set of custom thresholds post patch application. � Pattern name for Sequence Matcher scenario appears as 'null' in 'Scenario Test Execution' window. � Pattern name appears as '-' in Review Test Scenario Results window for Sequence Matcher scenarios. |
|
AML |
33410918 |
Existing issues in Review Test Scenario Result Screen (Admin Tools UI) are as follows: � Match information icon (downloadable Excel) should be in grey color and disabled till the job is in Running Batch status. However, this icon is enabled irrespective of Batch status. Do not download an excel report for jobs having Batch status other than Finished. � The Threshold values pop-up window for job entries in Running Batch Status is blank. � The Review Test Scenario Result page may incorrectly display for some scenarios when multiple jobs are assigned to a single template ID. One job will be completed with 'Finished' status and will display the count of matches. Other jobs will be in 'Running' Status and the count displayed will be '0'. When executed with a single job mapped with the template group ID, the result will display correctly. |
Oracle Financial Services Software Confidential and Restricted | Copyright �2022, Oracle and/or its affiliates. All rights reserved. | Phone: +1.650.506.7000 | Fax: +1.650.506.7200 | www.oracle.com/industries/financial-services/index.html