Release Notes for Oracle Health Insurance Value-Based Payments Release 4.25.1.0.0

This document contains the release notes for Oracle Health Insurance Value-Based Payments Release 4.25.1.0.0.

Version compatibility: Oracle Health Insurance Value-Based Payments 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-2919

Operational Reports and Data Transfer

This release introduces two new features:

  • Operational Reports: To generate reports on operational data from reporting views.

  • Data Transfer: To export data from base views, including PHI data. This feature is designed to replace the existing Extract IP, offering improved performance and memory efficiency. The existing behavior of base views remains unchanged when using BI Publisher (PHI data is excluded by default, controlled by the system property ohi.baseview.exclude.pii). The Data Transfer feature supports data extraction in the following formats:

    1. CSV (Headers are not included in this release; they will be included in the upcoming patch release)

    2. JSON

    3. XML (available only for cloud customers)

    4. PARQUET (available only for cloud customers)

Documentation Links:
Administration Guide - Gathering Metrics
Developer Guide - Report Page
Developer Guide - Data Transfer Integration Point
Developer Guide - Operational Reporting Integration Point
Installation Guide - Concepts
Installation Guide - Configuring Data Transfer
Operations Guide - User Interface
Operations Guide - Operational Reports (UI)
Operations Guide - Data Model
Operations Guide - User Access
Operations Guide - Overview
Operations Guide - Operational Reporting Installation
Operations Guide - Reporting View Metadata

CPN-3076

Move PHI Logs to OCI Object Storage

With the introduction of the PHI logging feature in operational reporting and the new data transfer IP, a significant increase in PHI log volume is expected. To optimize database storage usage and improve overall performance, PHI logs are migrated from the database to lower-cost storage options. In cloud deployments, logs are stored in OCI Object Storage, while in on-premise environments, logs are stored in the file system. This change reduces database load, ensuring better efficiency and scalability as log volumes grow.

Following this enhancement, PHI logs are retained in the database for 60 days, allowing customers to retrieve recent logs via the existing logphievents Query API. Beyond this retention period, older logs are no longer retained in the database. For cloud customers, these logs are archived in Oracle-managed OCI Object Storage, and retrieval requires submitting a request to the AMS team. In on-premise deployments, logs remain accessible in the file system according to the customer’s retention policies.

This enhancement improves database performance by significantly reducing storage overhead while maintaining access to recent logs. If you are a cloud customer and if you have relied on long-term PHI log retention, review your internal processes and work with AMS as needed to ensure continued access to historical data. No changes are required for application integrations querying logs within the 60-day window, but if you are a cloud customer, plan for an alternative retrieval approach for older logs.

Documentation Links:
Administration Guide - Logging to a Central Database - How to Check Access to PHI Data
Administration Guide - Database - Move PHI Logs to Object Storage
Security Guide - User Access - Resource Auditing

CPN-3218

Groovy 4 upgrade

This release includes an upgrade from Groovy 3.x to Groovy 4.0.24. This upgrade introduces performance enhancements, new syntax options, and improved security. The upgrade also introduces breaking changes that may impact existing dynamic logic, as some APIs and packages are removed. For detailed information, please refer to the Groovy 4.0 Release Notes.

Groovy 3 provided duplicate versions of several classes in legacy packages to ease migration. With Groovy 4, these legacy classes are removed. For detailed information, please refer to the Groovy 3.0 Release Notes. For example, classes previously available in both groovy.util and groovy.xml packages (e.g., XmlSlurper, XmlParser) are only available in groovy.xml package in Groovy 4. Therefore, if you use classes from groovy.util package in the dynamic logic, update the dynamic logic to use groovy.xml package instead before upgrading to this release. See the section "Additional Upgrade Steps" for more details.

To enable compatibility with Groovy 4, the bytecode of existing dynamic logic is reset during the upgrade. This reset causes the application start-up time to be slightly longer on the first startup after the upgrade, as the dynamic logic are recompiled at startup time. Future application restarts do not recompile this bytecode, so subsequent startups are faster.

Documentation Links:
Developer Guide - Dynamic Logic - Introduction

CPN-3246

File type validation

This enhancement introduces a new validation check that ensures uploaded files (for example, via Data File Sets IP) conform to a predefined set of allowed file types. This feature prevents users from uploading files with unsupported formats, improving data integrity and system security.

Documentation Links:
Developer Guide - Data Set Operations
Developer Guide - Data File Sets

CPN-3247

Removed database details from error messages

Certain database error responses, such as ORA-12899 ("value too large for column") expose internal database details, such as table and column names. To prevent this information from being revealed in API/IP responses, these error messages are modified to replace direct references to table and column names with corresponding entity and attribute names.

CPN-3249

Cache control headers for sensitive data

This enhancement prevents sensitive information from being stored locally in a browser using the property ohi.httpapi.cache.control.enable. When unspecified or set to false , the Cache-Control header is set to no-store for API requests using cache settings PHI and REFERENCE. When set to true, the behavior remains unchanged.

Documentation Links:
Developer Guide - HTTP API Caching

CPN-3356

Antivirus Scanning for Uploaded Files in Cloud Deployments

This enhancement introduces Antivirus scan for files uploaded to OHI (for example, through Data File Sets IP or Exchanges IP in OIG application) in cloud deployments. Only files that pass the Antivirus scan are processed, ensuring that uploaded files do not pose a security risk.

Documentation Links:
Administration Guide - Database - Purging - Purging Data from Data File Sets
Developer Guide - System Administration - Data File Sets - Antivirus Scanning

CPN-3377

Document maximum number of dynamic fields on objects

This enhancement extends the generic tables API with information about the maximum number of single-value non-time-valid dynamic fields available on an entity.

Documentation Links:
Configuration Guide - Size Category

CPN-3456

Channel HTTP headers

This enhancement introduces two new custom HTTP headers:

  • X-OHI-CHANNEL-TYPE

  • X-OHI-CHANNEL-SOURCE

These headers enable tracking of API/IP request origins by identifying the type and context of the originating channel (e.g., JET UI, portals, etc.). This structured tracking provides reliable data for improved monitoring and analytics.

When making calls to OHI APIs from external systems, such as portals, customers are encouraged to set these headers. Doing so enhances the ability to monitor request origins, supporting better operational insights and tracking.

Documentation Links:
Administration Guide - Resource Metrics
Developer Guide - Metrics

NXT-24521

Optimized data file storage using OCI Object Storage in SaaS

Prior to this release, data files were stored in the database. To optimize storage cost and improve overall performance, data files are now stored in Oracle-managed OCI Object Storage for SaaS deployments.

The interfaces for uploading and downloading data files (via Data File Sets IP and Exchanges IP in OIG application) remain unchanged.

For on-premise deployments, data files continue to be stored in the database, so existing behavior is unaffected.

NXT-25384

GET search through query API isn’t supported

The GET method for searching entities via /generic/<entityName>?queryParams is no longer supported. Instead, you can use POST requests to /generic/<entityName>/search with the query parameters included in the request body.

NXT-28043

Extend the advanced search fields for the Usages page

This enhancement makes it possible to expand the advanced search fields on the Usages page.

NXT-28899

JET 17 upgrade

This enhancement upgrades the JET (JavaScript Extension Toolkit) core library to version 17, bringing the following changes:

  1. The date and time format is automatically determined by the default language and country set for users in the application. This ensures the date and time format follows the conventions of the user’s region and language, providing a more intuitive experience.

    The value is formatted based on the user’s locale, which is defined by the displayLanguageCode(language) and the default country setting in the application.

  2. The default background colour of drawer and popup in the Redwood theme has been changed to a slightly darker shade.

Documentation Links:
Developer Guide - Single-Value Properties

NXT-29151

Increased length on first name field

This enhancement increases the length of the person first name and middle name fields to 120 characters.

NXT-29279

Allow Iframe content in OHI applications

This enhancement enables customers to integrate Oracle Health Insurance Components with Oracle Guided Learning (OGL). This is meant for customers who have purchased OGL.

Documentation Links:
Installation Guide

NXT-29355

Improve performance of operational and search pages

This enhancement removes redundant fields from the POST request payload, such as fields configured in Quick Search, Advanced Search of Search and View and Edit Object List floorplans, as well as in the Search and Popup Tail sections of LOV floorplans. It replaces the use of expand: "all" in operational pages with specific expand values for parent and child resources as defined in the floorplan, reducing the overall response payload for API requests originating from the UI.

It further reduces duplicate API calls made during application login and improves the performance of View and Edit Object – Recursive pages by deferring API calls used to construct the property model for dynamic data under the Tab Table More section until the Download action is triggered. Collectively, these changes reduce API calls and API response payload sizes for a faster UI experience.

NXT-29605

Support for deeplink is available for static/dynamic fields of string type

This enhancement supports deeplink for static/dynamic fields of string type

Documentation Links:
Developer Guide - Properties

NXT-29732

Improved performance of user interface searches

This enhancement removes all the non-operational links from the response at header level and the child lists level unless specified in the post request body. Changes are done to remove links for dynamic fields and records as well. The 'excludelinks' parameter is set to true to reduce the overall response payload for the API requests originating from the UI

Documentation Links:
Developer Guide

NXT-30352

Exclude links from dynamic fields for generic API POST search operation

New parameter "excludelinks" have been added for removing the non-operational links of child and reference resources (as per search result) until the user explicitly mention the field link in fields section. For Dynamic fields and dynamic records in response a new attribute "linkId" will be returned containing the value as id of the link.

Documentation Links:
Developer Guide - Influence Resource Representation - Exclude Links

NXT-30614

Additional dynamic fields on the relation entity

This enhancement increases the number of single-value non-time-valid dynamic fields that can be stored on the Relation entity.

NXT-30620

Reference Sheet Lines: As-of Date & Search Filtering for Time-Based Records

This enhancement enhances the search functionality for time valid reference sheet lines by enabling users to filter data between a start and end date, as well as specify an "asOfDate" within that range. This will improve both the accuracy and convenience of retrieving time-sensitive data.

NXT-30624

View Technical Errors, System Event Logs, and Queue Information Page.

This enhancement improves operational efficiency and simplifies troubleshooting by giving users more control over error management. It includes an enhanced View Technical Errors page for a better user experience, a new System Event Logs page for easy access to system events, and a new View Queue Information page (for Claims only) to help users manage and monitor queue-related data more effectively.

NXT-30781

Additional financial message attributes on invoice and invoice lines

This enhancement extends the number of available attributes on invoice and invoice lines in the financial message by additional sixty bringing the total number of available attributes to ninety.

NXT-31159

Update in LogBack Configuration

In this release, the logback-core library is upgraded. As a result, the component previously named SizeAndTimeBasedFNATP is renamed to SizeAndTimeBasedFileNamingAndTriggeringPolicy.

Please update your logback.xml configuration file to reflect this change.

POL-14428

New OHI specific HTTP library to make HTTP calls from dynamic logic

The initCallOut and webTarget functions used in dynamic logic for making HTTP calls depend on Javax WS RS API libraries and expose third-party classes such as WebTarget, Client, InvocationBuilder, and Response within dynamic logic. This release introduces an OHI-specific HTTP library, this new library provides a more intuitive, and maintainable alternative for constructing HTTP calls, reducing reliance on external dependencies and improving compatibility with future OHI updates and enhancements.

While this release continues to support both initCallOut/webTarget and the new HTTP library, the initCallOut and webTarget functions will be removed in a future release. Customers are strongly encouraged to use the new HTTP library in the dynamic logic. The user guide provides detailed migration instructions and examples to facilitate this transition.

Documentation Links:
Developer Guide - OHI Http Library
Developer Guide - OHI Http Library - Conversion Examples

POL-15792

Memory optimization in extract activity

Improved memory efficiency when loading dynamic fields with single, non-time-valid values in extract activity.

Additional Upgrade Steps

Pre-Upgrade Phase

1) Groovy 4 upgrade

Migration Details for groovy.util Classes

The following classes are removed from groovy.util package in Groovy 4. Update the dynamic logic to import the classes from groovy.xml package instead:

  • groovy.util.XmlNodePrinter

  • groovy.util.XmlParser

  • groovy.util.XmlSlurper

  • groovy.util.XmlUtil

  • groovy.util.slurpersupport.Attribute

  • groovy.util.slurpersupport.Attributes

  • groovy.util.slurpersupport.FilteredAttributes

  • groovy.util.slurpersupport.FilteredNodeChildren

  • groovy.util.slurpersupport.GPathResult

  • groovy.util.slurpersupport.NamespaceAwareHashMap

  • groovy.util.slurpersupport.NoChildren

In Groovy 3, classes from groovy.util package are automatically imported. With Groovy 4, these classes in groovy.xml package require explicit import statements.

To identify dynamic logic scripts that require modification, use the following POST request to api/generic/dynamiclogic/search:

{
    "resource": {
        "q": "logic.like('%XmlNodePrinter%').or.logic.like('%XmlParser%').or.logic.like('%XmlSlurper%').or.logic.like('%XmlUtil%').or.logic.like('%groovy.util.slurpersupport%')"
    }
}

Make these changes before upgrading to this release. The minimum required OHI version to apply these changes is 4.23.1. So, perform these changes if you are currently on version 4.23.1, 4.23.2, or 4.24.1.

Code Migration Examples
Example 1: Using XmlSlurper Without Import

Current dynamic logic: Uses XmlSlurper without an explicit import (implicitly relying on groovy.util):

def result = new XmlSlurper().parseText(response)

Updated dynamic logic: Add an explicit import for groovy.xml.XmlSlurper:

import groovy.xml.XmlSlurper

def result = new XmlSlurper().parseText(response)

Or use the fully qualified name:

def result = new groovy.xml.XmlSlurper().parseText(response)
Example 2: Explicitly Importing groovy.util.XmlSlurper

Current dynamic logic: Imports groovy.util.XmlSlurper explicitly:

import groovy.util.XmlSlurper

def result = new XmlSlurper().parseText(response)

Updated dynamic logic: Update the import to groovy.xml.XmlSlurper:

import groovy.xml.XmlSlurper

def result = new XmlSlurper().parseText(response)
Example 3: Correct Use of groovy.xml.XmlSlurper

Current dynamic logic: Already imports groovy.xml.XmlSlurper, so no changes are needed:

import groovy.xml.XmlSlurper

def result = new XmlSlurper().parseText(response)

Post-Deploy Phase

1) New OHI specific HTTP library for dynamic logic

Migration details
Identify the existing dynamic logic

To identify dynamic logic that require modification, use the following POST request to api/generic/dynamiclogic/search:

{
    "resource": {
        "q": "logic.like('%.path(%').or.logic.like('%.request(%').or.logic.like('%.invoke(%')"
    }
}

If the number of dynamic logic is large, use the (new) Data Transfer IP to query and export all the impacted dynamic logic.

Conversion of impacted dynamic logic to new format

Follow the Developer User Guide and Conversion Examples provided in the product documentation to update the identified dynamic logic.

Thoroughly review, validate, and test the dynamic logic changes before deployment.

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

  1. Perform any pre-upgrade steps.

  2. Stop all the managed nodes running the existing version of the application.

  3. Perform any pre-undeploy steps.

  4. Undeploy the existing version of the application.

  5. Back up the database.

  6. Perform any post-undeploy steps.

  7. Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.

  8. Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.

  9. Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.

  10. Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)

  11. Run the Upgrade script:

    1. Open a command window and browse to <OHI_ROOT>/util/install.

    2. Run the upgrade by executing ./ohi-update.sh .

  12. Make the required changes to the ohi properties file

  13. Perform any post-upgrade steps

  14. Start WebLogic application server

  15. Deploy the Application

  16. Perform any post-deploy steps

Additional Upgrade Steps for Installation

The following phases are defined:

  1. pre-upgrade: Application is still running.

  2. pre-undeploy: Application is stopped, but not undeployed.

  3. post-undeploy: Application is undeployed. Database is backed up.

  4. post-upgrade: Released upgrade script run is complete.

  5. post-deploy: New application is deployed, and is up and running.

Post-Undeploy Phase

1) Create a new database user ohi_capitation_rpt_user

As an admin user, create a new user ohi_capitation_rpt_user, which is used to run operational report queries.

create user ohi_capitation_rpt_user identified by <password>;
grant create session to ohi_capitation_rpt_user;
grant create synonym to ohi_capitation_rpt_user;

2) Create a data source ohi-operational-reporting-datasource

Configure a new data source named ohi-operational-reporting-datasource in the WebLogic Server to connect to ohi_capitation_rpt_user. For detailed steps, refer to the Installation Guide.

3) Configure Data Transfer

  1. On-premise deployments:

    1. Follow the steps mentioned in Configure Database Directories and Properties

    2. Install DBMS_CLOUD package in on-premise deployments. Refer to My Oracle Support Doc ID 2748362.1 for details.

  2. SaaS deployments:

    1. Follow the steps mentioned in Configure Object Storage Buckets and Properties

    2. As an admin user, grant the following permission to ohi_capitation_owner in SaaS deployments only.

grant select on v$pdbs to ohi_capitation_owner;

4) Apply WLS PATCH SET UPDATE and Coherence 14.1.1 Feature Pack 22.06 Cumulative Patch

Refer Required Software for details.

Post-Upgrade Phase

1) Configure Antivirus scanning property

On-premise deployments

Set the property ohi.antivirus.scan.enabled to false in the properties file.

SaaS deployments

Set the property ohi.antivirus.scan.enabled to true in the properties file.

2) Update logback configuration file

In this release, the logback-core library is upgraded. As a result, the component previously named SizeAndTimeBasedFNATP is renamed to SizeAndTimeBasedFileNamingAndTriggeringPolicy.

Please update your logback.xml configuration file to reflect this change.

3) Configure Data Transfer

  1. On-premise deployments: Follow the steps mentioned in Configure Database Scheduler Job

  2. SaaS deployments: Follow the steps mentioned in Configure Object Storage Use Cases and Database Scheduler Job

Configuration Properties

Ref Action Description

CPN-2919

Added

ohi.phi.logs.data.transfer.target.db.directory.name

Name of the database directory where the PHI logs will be stored. Applicable only for on-premise deployments.

CPN-2919

Added

ohi.views.metrics

Timer metrics to indicate time taken to execute the query.

CPN-2919

Added

ohi.data.transfer.target.db.directory.name

Name of the database directory where the files generated for data transfer operation will be stored. Applicable only for on-premise deployments.

CPN-2919

Added

ohi.reporting.fetched.rows.count.per.view

Counter metrics which indicate the number of rows fetched per view.

CPN-3356

Added

ohi.antivirus.scan.enabled

Added a new mandatory property to enable/disable Antivirus scanning for data file uploads. Set the value of this property (in properties file, not using properties API) to true in cloud deployments and false in on-premise deployments.

NXT-24521

Added

ohi.datafile.object.storage.enabled

Enables storing data file content in OCI Object Storage. By default, data files are in the database. This property is applicable only in SaaS deployments.

NXT-24521

Added

ohi.datafile.object.storage.part.size

Size of each data file part in bytes when data file is uploaded to OCI Object Storage using multipart upload. Big data file is split in multiple parts of mentioned size. Default size is 10000000 bytes (10 MB). This property is applicable only in SaaS deployments.

NXT-24521

Added

ohi.datafile.object.storage.bucket.folder.structure

Folder structure in OCI Object Storage bucket where data files are stored. Folder structure must end with '/'. Example - CLAIMS/DATAFILES/. Default value is {appName}/DATAFILES/. This property is applicable only in SaaS deployments.

NXT-25384

Removed

ohi.service.queryapi.get.support

Removed deprecated property.

NXT-29279

Added

ohi.ui.iframe.allowlist.url

This property contains list of URLs to be allowed to load inside iFrame in OHI application.

Web Services

Ref Action Description

CPN-2919

Added

operationalreporting IP

Added a new IP to query the reporting views.

CPN-2919

Added

datatransfer IP

Added a new IP to export data from base views (including PHI data).

CPN-2919

Added

datatransferlogs API

Read-only API to query data transfer logs.

CPN-2919

Added

objectstoragecredentials API

Added a new API to configure credentials to connect to the OCI Object Storage. Applicable only for SaaS deployments.

CPN-2919

Added

objectstorageapikeyusecases API

Added a new API to configure credentials to connect to the OCI Object Storage using API keys authentication method. Use objectstoragecredentials API to configure the credentials prior to creating data using this API. Applicable only for SaaS deployments.

CPN-2919

Added

objectstorageconfigurationfileusecases API

Added a new API to configure credentials to connect to the OCI Object Storage using OCI configuration file. Applicable only for SaaS deployments.

CPN-2919

Added

reportingviews metadata IP

Added a new IP to query reporting views columns metadata.

CPN-2919

Added

viewfloorplans API

Added a new API to configure floorplan for operational reporting.

CPN-2919

Added

userviewpreferences API

Added a new API to configure search preferences for operational reporting.

CPN-2919

Added

reportingviews API

Read-only API to query reporting views metadata.

CPN-2919

Added

reportingviews IP

Added a new IP reportingviews to generate reporting views.

CPN-2919

Added

objectstorageresourceprincipalusecases API

Added a new API to configure credentials to connect to the OCI Object Storage using resource principal authentication method. Applicable only for SaaS deployments.

CPN-3076

Modified

autopurgemetadata API

The option to configure the retention period for PHI logs is removed.

CPN-3076

Modified

logphievents API

PHI logs are retained in the database for 60 days, allowing customers to retrieve recent logs via the existing logphievents Query API. Beyond this retention period, older logs are no longer retained in the database. For cloud customers, these logs are archived in Oracle-managed OCI Object Storage, and retrieval requires submitting a request to the AMS team. In on-premise deployments, logs remain accessible in the file system according to the customer’s retention policies.

CPN-3249

Modified

All APIs

When ohi.httpapi.cache.control.enable is set to false (or is not set), the Cache-Control header is set to no-store for API requests using cache settings PHI and REFERENCE.

CPN-3356

Modified

Data File Sets IP

  • Added 2 new optional attributes status and extraInfo.

  • The operation to download data file is enabled only if the status is null or Ready or Skipped.

CPN-3356

Modified

datafiles API

Added 2 new optional attributes status and extraInfo.

CPN-3356

Modified

datafilesets API

Added 2 new optional attributes status and extraInfo.

CPN-3377

Modified

tables API

Added a new attribute sizeCategory to tables API.

CPN-3456

Modified

All APIs/IPs

Two new custom optional headers are introduced: X-OHI-CHANNEL-TYPE and X-OHI-CHANNEL-SOURCE.

NXT-30624

Added

systemeventlogs API

Added a new API to view and update System Event Logs.

NXT-30624

Modified

taskprocessing IP

Added a new operation to restart a list of errored task in the system.

Data Conversion

Ref Action Description

NXT-24521

Added

DataFile Storage Type

The storage type of the existing data files is set to 'DB' in dat_data_files table.

Dynamic Logic

Ref Action Description

CPN-3218

Modified

Groovy 4 upgrade

Upgraded Groovy from 3.x to 4.0.24.

POL-14428

Added

New HTTP Library

Introduced new OHI-specific HTTP library to make HTTP calls from dynamic logic.

POL-14428

Deprecated

initCallOut

initCallOut method is deprecated.

POL-14428

Deprecated

webTarget

webTarget method is deprecated.

UI Changes

Ref Action Description

CPN-2919

Added

Search Reports

Added page to search for reports.

CPN-2919

Added

Operational Reports

Added page to view operational reports.

CPN-2919

Added

View Floorplans

Added page to view, add, update floorplans for reporting views.

NXT-28043

Modified

Usages Page

The advance search in the Usage page is extended with more attributes

NXT-29605

Added

Episodes page

Deeplink added to Claim code (applicable only to the Claims application)

NXT-29605

Added

Claims page

Deeplink added to Authorization code and Reservation code at claimline tab (applicable only to the Claims application)

NXT-30620

Modified

Reference Sheet page

Added "asOfDate" field in quick search to filter data between a start and end date

NXT-30624

Added

System Event Logs page

New page added to view System Event Logs

NXT-30624

Added

Queue Information page (Claims)

New page added to view Queue Information

NXT-30624

Modified

View Technical Errors page

Page is enhanced to provide efficiency and simplifies troubleshooting

Breaking Changes

Ref Action Description

CPN-3076

Modified

autopurgemetadata API

The option to configure the retention period for PHI logs is removed.

CPN-3076

Modified

logphievents API

PHI logs are retained in the database for 60 days, allowing customers to retrieve recent logs via the existing logphievents Query API. Beyond this retention period, older logs are no longer retained in the database. For cloud customers, these logs are archived in Oracle-managed OCI Object Storage, and retrieval requires submitting a request to the AMS team. In on-premise deployments, logs remain accessible in the file system according to the customer’s retention policies.

CPN-3218

Modified

Groovy 4 upgrade

Upgraded Groovy from 3.x to 4.0.24.

CPN-3767

Modified

Date format in APIs/IPs

The APIs/IPs accept value for date fields in ISO 8601 format (YYYY-MM-DD), for example 2025-01-01. Any other formats result in an error.

NXT-30624

Modified

Error Messages

The following error messages have been modified as follows,

  1. OHI-TASK-IP-001 to OHI-IP-TASK-001

  2. OHI-TASK-IP-002 to OHI-IP-TASK-002

  3. OHI-TASK-IP-003 to OHI-IP-TASK-003

Note: These message codes are used in Oracle Health Insurance Claims Adjudication.

Bug Fixes

BugDB SR Internal Summary

32477683

CPN-1431

Base views for reference sheet lines are not created

Description:

Base views for reference sheet lines are not created using base views generator.

Resolution:

Base views generator is updated to generate base views for reference sheet lines.

33430852

CPN-1811

Dynamic fields in multiple floorplan sets are displaying incorrectly

Description:

When a usage is added to floorplan to display the same dynamic field in multiple sets of the entity page, the respective fields are not rendering the values as expected.

Resolution:

When a usage is added to the floorplan to display an existing dynamic field in a different section of the entity page, it detects any prior usage of that field and updates it with the latest configuration. As a result, there are no longer multiple occurrences of the same dynamic field

36977368

CPN-3415

Copy action shown on display-only global activity details page

Description:

The Copy action is incorrectly shown on display-only details pages.

Resolution:

Copy action is removed from view only details pages

36993281

3-37715853681

CPN-3426

API response contains empty ID for single value flex codes

Description:

The API response contains an ID attribute for single value flex codes. The value of this attribute is always null.

Resolution:

The API no longer returns the ID attribute for single value flex codes.

37082990

CPN-3463

Unable to update widget descriptions

Description:

Unable to update the description for system specific widget entry.

Resolution:

The restriction to update the widget description is removed.

37480109

CPN-3602

The end date column is missing on the Flex Code Group Details page

Description:

The end date column is missing on the Flex Code Group Details Page.

Resolution:

The end date column is added to Flex Code Group Details Page

37654291

CPN-3666

Conflicting keyboard shortcuts

Description:

Users can set up set a custom shortcuts using an existing key combination. This creates a conflict when the key combination is used.

Resolution:

A new business rule is introduced to ensure that all custom shortcuts have unique key combinations.

37147234

CPN-3485

Activity page searches take too long

Description:

Page searches take too long on the following pages: Financial Transaction Set, Contract (Activities), Global Activities pages.

Resolution:

The search features on these pages now require a minimum of search conditions to ensure that the resulting query has an optimal performance.

37248337

CPN-3512

The referencesheetlines Query API returns incorrect results for gte and lte operations

Description:

The referencesheetlines Query API returns incorrect results for gte and lte operations

Resolution:

The query logic for gte and lte operations is updated to return the correct the results in the referencesheetlines Query API.

37886824

CPN-3780

Base View generation fails for an entity which has an apostrophy character in the display name

Description:

For entities which have dynamic attributes, base view generation adds column remark using display name. If display name has apostrophy character ('), it fails with following exception: java.sql.SQLSyntaxErrorException: ORA-00933: SQL command not properly ended

Resolution:

No SQL exception is thrown when a display name has apostrophy character (')

37056633

CPN-3443

Action items missing on inbound and outbound exhange pages

Description:

Action items such as 'build', 'message', and 'download' are missing on the activity pages

Resolution:

The missing action items have been added to the inbound and outbound exchange pages

37837884

CPN-3767

Number and Date incorrectly converted based on locale in API/IP requests

Description:

Dates are incorrectly converted based on the locale value in API/IP requests.

Resolution:

The date conversion no longer considers the locale value.

Issues that were backported in previous Release / Patch

No backports.

Known Issues

BugDB SR Internal Summary

35031585

3-31969350441

CPN-2430

Query API ignores conditions on empty attributes

Description:

Queries that accepts results where attribute A either has a specific value OR is empty do not work as per the specifications. For example, the query condition (multicore.eq('Y').or.multicore.eq(null)) only returns records with attribute multicore set to value Y, not including records where multicore is empty.

35686859

CPN-2724

Dynamic logic statistics IP returns incorrect statistics for test unit dynamic logic

Description:

Dynamic logic statistics IP returns incorrect statistics when a test unit dynamic logic is used to test one dynamic logic and then modified to test another dynamic logic.

36967832

CPN-3407

Activities remain in QD status after OutOfMemoryProtector is triggered

Description:

After exceeding the critical memory threshold and having recovered the application memory, the queued activities are not dequeued and remain in QD status.

36970168

3-37743857111

CPN-3410

Property ohi.ws.client.readtimeout does not work as intended

Description:

The system property ohi.ws.client.readtimeout is intended to control the time (in milliseconds) that the client will wait for a response from the server after sending a request. However, it is currently being incorrectly applied to set the timeout for the entire request/response conversation, rather than just the response wait time.

36991723

3-37582942001

CPN-3423

Application logs are not persisted in the database in rare scenarios

Description:

Application logs are internally queued before writing to the database. In rare cases, these logs are not successfully written, causing the internal queue to grow significantly in size - several GBs in some instances. This led to a loop in the log persistence mechanism, impacting system performance.

37257823

3-38637505211

CPN-3515

Query API does not return correct results when the search criteria contains an apostrophe

Description:

Query API does not return correct results when the search criteria contains an apostrophe.

37334534

CPN-3566

Additional field values when emptied are not retained after save

Description:

Additional field value (dynamic fields of a dynamic record) nullification does not work and original value gets retained. When a payload to update a dynamic field in a dynamic record is sent via api, such that only the fields that are nullified are present and any non-null field is not present, then those updates are not being handled properly and the nullification for the fields present in the payload does not happen. If any non-null field is also included with the payload along with nullified fields then the persistence happens properly and the respective values get nullified also.

37785812

CPN-3707

Contract adjustment page does not display schedule dimensions

Description:

Contract adjustment page does not display schedule dimensions

37793706

CPN-3733

Boilerplate texts are not displayed for dimensions in adjustments page

Description:

Labels (Boilerplate texts) are not displayed for Schedule dimensions in contract adjustments page. Boilerplate code is displayed instead

37882208

CPN-3778

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.

37924882

CPN-3793

Data File Sets IP does not return the message text in the response for error codes DAT-IP-DAFI-013 and DAT-IP-DAFI-014

Description:

Data File Sets IP does not return the message text in the response for error codes DAT-IP-DAFI-013 and DAT-IP-DAFI-014

Deprecated Items

These features will be removed in a future release. Customers are advised to review the documentation and take timely action.

JIRA Key Announced Release Announced Summary

NXT-25000

3.22.2.0.0

The use of parameters that influence the resource representation in the 'Accept' header of an HTTP request is deprecated.

Reference Document

CPN-3249

4.25.1.0.0

HTTP API Caching override feature is deprecated in this release and will be removed in a future release.

Reference Document

POL-14428

4.25.1.0.0

The webTarget and initCallOut functions, which are used to make HTTP calls from dynamic logic, have been deprecated.

Reference Document