Oracle Financial Services Behavior Detection Application Pack v8.1.2.5.0

 
 

Oracle Financial Services (OFS) Behavior Detection Application Pack is a separately licensed product.

            Description

OFS BD Application Pack v8.1.2.0.0 Minor Release #5 8.1.2.5.0 (ID 35189486).

This OFS BD Application Pack release is cumulative of all enhancements and bug fixes since the v8.1.2.0.0 release.

              Prerequisites

Refer to the below pre-requisites:

•         Before applying OFS BD 8.1.2.5.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 Guide 8.1.2.0.0. 

•         Apply patch for Bug 35013409 - OFSAA 8.1.2.0.0 AAI ML Release #3 (8.1.2.3.0)

•         Apply patch for Bug 35307360 - Consolidated fixes for issues found on OFSAAI 8.1.2.3.0

•         For additional prerequisites, refer OFS BD Application Pack Installation Guide 8.1.2.5.0. 

 

            How to Apply This Patch?

For detailed instructions on installing this OFS BD release, see OFS Behavior Detection Installation Guide 8.1.2.5.0.

            About This Release

            This section describes the new features, bugs addressed, and known issues in this release of OFS Behavior Detection.       

            Topics:

·         New Features

·         Bugs Addressed

·         Known Issues

            New Features

The following is the list of new features included in this release:

AML

•         The scenarios listed below have been modified to support Functional Currency

o  High Risk Transactions: High Risk Geography – Account focus

o  High Risk Transactions: High Risk Geography – Customer focus

•         The scenarios listed below have been modified to support Cash transactions:

o  High Risk Transactions: High Risk Geography – Account focus

o  High Risk Transactions: High Risk Geography – Customer focus

•         The scenarios listed below have been modified to support Wire transactions:

o  Structuring: Avoidance of Reporting Thresholds - Account Focus

o  Structuring: Avoidance of Reporting Thresholds - Customer Focus

•         The following scenarios were redesigned from Sequence algorithms to Rule algorithms for better performance:

o  Structuring: Avoidance of Reporting Thresholds - Account Focus

o  Structuring: Avoidance of Reporting Thresholds - Customer Focus

Table 1: Sequence Algorithms to Rule Algorithms

Old Scenario

New Scenario

ML-StructuringAvoidReportThreshold.116000062.xml – AC focus

ML-StructuringAvoidReportThreshold.118860029.xml – AC focus

ML-StructuringAvoidReportThreshold.116000046.xml – CU focus

ML-StructuringAvoidReportThreshold.118860028.xml – CU focus

Note: The old scenario file has been replaced by the new one listed above, for scenario technical performance optimization purposes. There is no change in alert generation, filters, data streams of interest, parameters, scenario configuration, building blocks, highlights, Frequency, and lookback period.

•         Alert Management Configuration pages have been migrated to OJET – our latest Forms Frameworks - and offered with a new wave design for enhanced UI/UX experience. The following pages have been redesigned:

o    Alert Assigner Editor

o    Alert Creator Editor

o    Alert Scoring Editor

o    Threshold Editor

o    Review Test Scenario Results

RTF

•         Two new roles have been introduced in the security mapping:

o  Auditor role: a “view only” role intended for users that want to audit the system

o Senior Supervisor role: a role for senior supervisors or managers that give them extended possibilities like assigning or re-assigning alerts manually or taking actions in bulk.

•         To optimize workflow, a configurable UI locking system has been introduced. It ensures that only one user can take action on an alert at a given time.

•         For in-site customization, a step-by-step guide is provided to assist installers in extending the Data model to fit their coverage requirements.

•         Transaction Data can now be archived on a configurable frequency, leading to overall performance improvement.

•         Additional Documentation is provided, coming with new details to facilitate integration: field detailed description and corresponding samples.

KYC

•         Language Pack support for Thai and Vietnamese languages for KYC admin and risk assessment-related screens.

•         Manual promoted case (MPTC) for KYC Batch is populated with a due date for better monitoring and SLA adherence.

Bugs Addressed

The following bugs have been fixed in OFS Behavior Detection Release 8.1.2.5.0.

Table 2: List of Resolved Issues

Component

Bug ID

Resolution

KYC (Risk Assessment UI)

35134790

Display watchlist for related customers in the UI for KYC batch assessments.

BD

35456482

HRG (CU) Focus Scenario (118860022)- highlights to be aligned with the TSD.

BD

35423290

Functional Currency hardcoded to Base Currency in the scenario- Early Payoff/Paydown of a Credit Product.

BD

35394968

AML Audit History does not display multiple comments.

BD

35231466

Structuring (AC) Trusted Pair transactions check to be included in the scenario.

BD

35130565

Remove the TC and BC sections from Threshold Analyzer/Scenario Tuning (OBIEE Report).

BD

35078124

Add Cash Transaction and Functional Currency to scenario ML-HRTRANSHRGEOGRAPHY- CU FOCUS.

BD

35071287

Add Cash Transaction to scenario ML-HRTRANSHRGEOGRAPHY- AC FOCUS.

BD

34989454

Converting scenario ML-STRUCTURINGAVOIDTHRESHOLD- AC FROM SEQ PATTERN TO RULE PATTERN.

BD

34934258

Converting scenario ML-STRUCTURINGAVOIDTHRESHOLD- CU FROM SEQ PATTERN TO RULE PATTERN.

            Known Issues

              The known issues/limitations in OFS Behavior Detection Release 8.1.2.5.0. are as follows

Table 3: List of Known Issues

Component

Bug Number

Description

CTR

35443990

When a user logs into CTR using https://URL and navigates to the CTR Search and List page, a blank pop-up appears, preventing the user from taking any further activities. 

Workaround: Log out and then log back in.

CTR

35514277

When uploading the Acknowledgment file, after entering in the BSA ID and selecting save, the user receives an error saying that mandatory information is missing.

Workaround: This issue is intermittent and will be fixed in a later patch.

CTR

35443983

When sorting by CTR ID in the CTR Search and List the first and last pages are not being sorted properly.

CTR

35423191

The Sub-Type options for the Financial Institution edit pop-up are always enabled.

Workaround: Select Casino/Card Club as FI type.

CTR

35482609

In the CTR Search and List, the Owner drop-down displays a list of all BD users, not just the CTR users.

Workaround: Select the CTR User option.

CTR

35482609

In the CTR Search and List, if the user selects multiple values in the Location field no records will be returned in the search result.

Workaround: Select only one Location at a time.

CTR

35448473

When the Action button is selected, the modal window, by default, scrolls to the end rather than displaying the first field.

Workaround: Scroll back to the top of the modal window.

AML

35494062

The Find option is not working in:

·         Narrative tab editor window

·         History pop up window in Narrative tab.

Workaround: Narrative window find will work in Chrome browser.

 

Oracle Financial Services Software Confidential and Restricted   |   Copyright © 2023, 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