Release Notes for Oracle Insurance Gateway Patch 4.25.1.0.4
This document contains the release notes for Oracle Insurance Gateway Patch 4.25.1.0.4.
| Version compatibility: Oracle Insurance Gateway Release 4.25.1.x is only compatible with other Oracle Health Insurance applications release version 4.25.1.x unless explicitly stated otherwise. |
| In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases. |
Enhancements
| ID | Summary | Patch | ||
|---|---|---|---|---|
CPN-3641 |
Enhanced PHI logs access using base views In SaaS deployments, PHI access logs are stored in the database for 60 days in the This enhancement improves the customer experience by enabling PHI access logs to be extracted directly through base view generation. The
|
|||
CPN-3799 |
Operational Reports and Data Transfer The following changes are made in Operational Reports and Data Transfer:
|
|||
NXT-32524 |
Table component improvements - Usability with editable row Introduced check (Apply) icon as a table row-level action in edit mode. Clicking the check icon returns the row from edit mode to view mode. Actions in other rows will be disabled until the user clicks on the check icon of the current row being edited. Editable row remains in edit mode and persists the data when the user clicks outside the table or switches to another browser tab. |
|||
NXT-32617 |
UI: Ability to exclude trailing wildcard with like search This enhancement allows excluding the automatic inclusion of the trailing wildcard for like search in quick search, advanced search, and lookups by setting the application property The system also auto-truncates the leading and trailing white space for searches. Documentation Links: |
|||
NXT-32621 |
UI: Additional Features Quick Search With this enhancement, the quick search component is extended, and it will be possible:
Documentation Links: |
|||
NXT-32629 |
UI: Expandable "more" section in tables With this enhancement, the overflow region for the table ("More" link) is now expandable to a two-column layout, allowing more information to be viewed at once. Documentation Links: |
Upgrade Steps for Installation
To perform the upgrade, perform the following steps:
-
Perform any pre-upgrade steps.
-
Stop all the managed nodes running the existing version of the application.
-
Perform any pre-undeploy steps.
-
Undeploy the existing version of the application.
-
Back up the database.
-
Perform any post-undeploy steps.
-
Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.
-
Change Installation Configuration: In
<OHI_ROOT>/util/install, make a copy ofohi_install.cfg.templateand name itohi_install.cfg. -
Edit
ohi_install.cfgto contain your specific database connection data and other configuration settings. The settings are explained in the file itself. -
Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)
-
Run the Upgrade script:
-
Open a command window and browse to
<OHI_ROOT>/util/install. -
Run the upgrade by executing
./ohi-update.sh .
-
-
Make the required changes to the ohi properties file
-
Perform any post-upgrade steps
-
Start WebLogic application server
-
Deploy the Application
-
Perform any post-deploy steps
Additional Upgrade Steps for Installation
|
The following phases are defined:
|
Post-Upgrade phase
-
A new MDC (Mapped Diagnostic Context) field,
user, has been introduced for security logs. To ensure this information appears in the security log file, update the log pattern for thesecurityAppender(which usesRollingFileAppender) to include theuserMDC field.Example updated pattern:
<appender name="securityAppender" class="ch.qos.logback.core.rolling.RollingFileAppender"> <encoder> <pattern>%d{ISO8601} [ %t ] %marker %c - %m [user:%X{user:-N/A}] %n</pattern> </encoder> ... </appender> -
Create a new
securityDBAppenderin SaaS deployments. This appender enables writing security logs to the database.Example Logback configuration:
<configuration debug="true" scan="true" scanPeriod="60 seconds"> ... <appender name="securityDBAppender" class="com.oracle.healthinsurance.loggingsupport.appender.impl.OhiSecurityLoggerAppender"> <connectionSource class="ch.qos.Logback.core.db.JNDIConnectionSource"> <jndiLocation>jdbc/policiesUserOhiApplicationDS</jndiLocation> </connectionSource> <logType>security</logType> <bufferDir>/writable/log/storage/buffer/security</bufferDir> </appender> ... <root level="error"> ... <appender-ref ref="securityDBAppender"/> </root> </configuration>
Configuration Properties
| Ref | Action | Description |
|---|---|---|
NXT-32617 |
Added |
ohi.ui.likesearch.wildcard.enabled This property enables or disables the trailing '%' sign from quick, advanced search, and lookup (LOV) with the query operators like and likeic. |
Web Services
| Ref | Action | Description |
|---|---|---|
CPN-3799 |
Modified |
Data Transfer IP
|
CPN-3799 |
Modified |
Operational Reporting IP Two new error messages are introduced in the Operational Reporting IP. The IP returns an HTTP 422 response with one of the following error messages:
|
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
38575973 |
OIG-4689 |
Zip and Unzip operations in Data File Sets IP return HTTP 405 in SaaS |
|
Description: |
The Zip and Unzip operations in Data File Sets IP return HTTP 405 (Method Not Allowed) in SaaS. Also, UploadToUCM step fails with database error ORA-06512 in SaaS. |
||
Resolution: |
Zip and Unzip operations are now supported in the Data File Sets IP in SaaS. Also, UploadToUCM step now runs successfully and no longer fails with database error in SaaS. |
||
38683690 |
OIG-4777 |
Data transfer export to Oracle directory has issues with CSV and JSON formats |
|
Description: |
Data transfer export has issues: CSV output is invalid when string columns with commas are not escaped, JSON export returns empty values for CLOB columns exceeding 20MB, and JSON exports show only one file even when more records exist in the database. |
||
Resolution: |
Data transfer export now generates valid CSV output with escaped special characters, supports CLOB data in JSON format, and correctly reports the number of exported files. For SaaS customers, exporting columns of type CLOB in CSV or JSON format is currently not supported due to a known issue in the DBMS_CLOUD package. This limitation is tracked under Oracle Bug 38183169. |
||
38761785 |
OIG-4830 |
Recovery of exchange failed or timed out on CheckDataTransferStatus step leads to out of memory scenario |
|
Description: |
When an exchange that failed or timed out on CheckDataTransferStatus step is recovered, the exchange gets stuck processing that step. This later leads to system running out of memory and errors are seen in application logs. |
||
Resolution: |
Recovering an exchange in the CheckDataTransferStatus step starts processing the exchange properly without getting stuck in that step or running out of memory. |
||
38669224 |
3-42706054381 |
OIG-4773 |
Recovery of failed or timed out ReceiveNotification step is unsuccessful if event store is used as error destination |
Description: |
If an OIG exchange fails or times out in the ReceiveNotification step and event store is used as error destination, an event is created by the error workflow. However, the location header present in exchange properties used for checking the external activity status gets overwritten with the URI of the created event. When the exchange is recovered, it is unsuccessful with a HTTP 401 Unauthorized error. |
||
Resolution: |
When an OIG exchange fails or times out in the ReceiveNotification step and event store is used as error destination, an event is created by the error workflow but it no longer overwrites the location header in exchange properties. As a result, recovery of exchange is successful, processing the exchange from the failed or timed out step. |
||
38655769 |
3-42551002131 |
OIG-4763 |
OHI Agent fails to read the property file |
Description: |
OHI Agent fails to read the properties file (application.properties) if the file is present in the same folder as OHI Agent. As a result, OHI Agent fails to start if the file is present in the same folder, also referred to as AGENT_HOME. |
||
Resolution: |
OHI Agent starts successfully after reading the properties file (application.properties) when the file is present in the same folder as OHI Agent. |
||