|
Oracle Financial Services
(OFS) Enterprise Case Management (ECM) Pack is a separately licensed product.
Description
Release ID 35197649 – OFS ECM v8.1.2.0.0 Minor Release #5
(8.1.2.5.0).
The Oracle Financial Services Enterprise Case Management
(OFS ECM) version 8.1.2.5.0 ML is cumulative of all bug fixes &
enhancements done since the 8.1.2.0.0 release, and it can be directly applied
to the ECM 8.1.2.0.0 version.
Prerequisites
·
Before applying OFS ECM
v8.1.2.5.0, it is required to install OFS ECM v8.1.2.0.0. For detailed
instructions on installing this OFSECM Release, see OFS ECM Application Pack
Installation Guide 8.1.2.0.0.
·
Configure the Server Time Zone
as:
For ECM standalone installation:
o The SERVER_TIMEZONE parameter
must be configured in the CONFIGURATION table in CONFIG schema with the correct
time zone name.
§
The Date/Timestamps
are displayed according to the user's browser time zone.
§
Once the user time
zone is saved, the browser date is converted to the Server time zone date and
saved in the database.
For Pack-on-Pack
installation:
o Update the SERVER_TIMEZONE
parameter in the CONFIGURATION table in CONFIG schema with the following query:
§ UPDATE CONFIGURATION SET PARAMVALUE='', DESCRIPTION='DB
Server Timezone' WHERE PARAMNAME='SERVER_TIMEZONE';
·
The SYS DB user must provide the
following grant to the ATOMIC DB user:
GRANT execute on ctx_ddl to <ATOMIC_USER>;
·
Apply Bug
35189486 - BD8125:BEHAVIOR DETECTION VERSION 8.1.2. ML RELEASE #5 (8.1.2.5.0).
·
Apply Bug
35013409 - OFSAA 8.1.2.0.0 AAI ML
RELEASE #3 (8.1.2.3.0) (OFSAAI).
·
Apply Bug
35307360 - Consolidated fixes for issues found on OFSAAI V8123.
How to Apply This Patch?
For detailed instructions on installing the OFS ECM 8.1.2.5.0 release, see OFS ECM ML Installation Guide.
About This Release
This
section describes the new features and known issues in this release of OFS
ECM.
Topics:
New Features/Enhancements
The following is the list of new features and enhancements
included in this release:
·
Manual
Entry of Transactions: For the new
transaction tab, which was released in 8.1.2.4, users can now define manual
transactions and add them to the case.
·
Configure
the max number of cases returned in search: A system parameter has been created to define the total number of cases
returned per page when searching. 100 is
the default value, and 300 is the maximum value.
·
Automated
Due Date Setting of New Cases: A new
procedure has been created to automatically update the due date of a case when
the case is created. This batch job is configurable per case type.
·
Standard
Comments Per Case Type, Action, and User Role: Standard comments can now be defined per Case Type, User Role, and
Status.
·
Case
Archiving: These scripts allow for
cases older than a defined period to be segmented into a separate storage area
to improve performance. This is beneficial for customers who have large amounts
of historical data which is still within the retention period. Users can still query the data and retrieve
it as needed.
·
Audit
History Printing for Events: In Event
Viewer, a user can now print the audit history of the event.
·
Additional
Permissions for Restricted Use License: The following permissions have been added to the CM Level 1 Analyst and
CM Level 1 Supervisor roles: Create New Manual Event, Send Email, Event Search
and Create Event
·
Formatting
the display of long text in event binding JSON: If large amounts of data are provided in the generic event JSON, the
data is now displayed left justified and centered to improve the display.
·
Case
Sensitive Searching: All case
sensitivity has been removed from Case Search
·
Case
Merge to include transaction labels: For customers using the new Transaction tab, labels are now merged to
the parent case when the cases are merged.
·
Manual CAR Cases: The ability to select the AML CAR case type when manually
creating a case has been removed.
The following bugs have been fixed in OFS Enterprise
Case Management Release 8.1.2.5.0.
Table:1 List
of Fixed Issues
Bug Number |
Description |
35144927 |
When the acknowledgment of the SAR is received, the amount and
suspicious activity date are not being populated on the Previous Report
Information tab in the resulting CAR case. Therefore, this information is not
provided to the SAR report if it is determined a SAR should be filed on the
CAR case. These values will need to be manually entered in the SAR report
before submitting to FinCEN. |
35040535 |
Duplicate case attributes are getting displayed in Case Designer. |
35015350 |
The AML_CA case type is showing when the user tries to create a
manual case. |
35113376 |
Refresh issue in Case Designer where the previously selected case
type is showing when viewing a separate case type. |
35136296 |
Due to performance concerns, we restrict the loading of Case Type
Attributes’ drop-down values in the Attributes section of Case designer
screen. However, the Case Designer displays all types of fields |
The following
table provides the list of known issues in this release.
Table:2
List of Known Issues
Description |
|
35526597 |
Even if a user selects a status other than Closed from the Status
drop-down in Advanced Search, only closed cases will be returned in the
search results. Workaround: Use only closed
status for search. |
34789808 |
In Case Advanced Search,
users are able to enter strings in date fields. This should not be allowed. Workaround: Only enter the date
values or select the date from the Calendar option. |
35140989 |
As part of the CAR process,
when CRR sends the narrative of the prior SAR for display in the CAR case,
any carriage return formatting in the narrative is lost. If the narrative was
paragraph text with no carriage returns, there are no issues. Workaround: If the narrative was
paragraph text with no carriage returns, there are no issues. |
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