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

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

Version compatibility: Oracle Health Insurance Value-Based Payments Release 4.23.2.x is only compatible with other Oracle Health Insurance applications release version 4.23.2.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

AUT-2750

New metrics for Data Replication

This enhancement adds the following new data replication metrics to the Authorization, Policy, Claims, and Value based payments applications:

  • ohi.datareplication.sourceevents.created

  • ohi.datareplication.targetevents.created

  • ohi.datareplication.targetevents.processed

  • ohi.datareplication.sourceevents.lasttimestamp

  • ohi.datareplication.targetevents.lasttimestamp

  • ohi.datareplication.targetevents.processed.lasttimestamp

Documentation Links:
Administration Guide - Data Replication Metrics

AUT-3268

Metrics internal code optimization

This enhancement adds a metric set for every OHI metric category. The property "ohi.instrumentation.gather.applicationmetrics" controls all metrices and can be used to switch on/off all the OHI metrices. The property "ohi.instrumentation.gather.{0}" controls a single metric set or category of metrices The placeholder value is the code of the metric set such as "activityprocessing", "persistence", "springbatch", "datareplication".

The following properties have been removed:

  • ohi.instrumentation.gather.persistence

  • ohi.instrumentation.gather.activityprocessing

Documentation Links:
Installation Guide - Monitoring and Metrics

AUT-3376

Activity Groupmode processing enhancements

This enhancement slows down activity processing when memory runs short. It tries to prevent entering into the critical memory state. It is now monitored when and how often the group mode did not start or was terminated, with the help of two new metrices, ohi.activityprocessing.group.failed.errors and ohi.activityprocessing.group.failed.nomemory. Now, the activity groupmode processing starts only when memory state = normal and it is terminated when memory state is not normal.

Documentation Links:
Administration Guide - Activity Processing Metrics

AUT-3377

New metrics for Activity Grid Processing

This enhancement adds the following new activity grid processing metrics to the applications:

  • ohi.activityprocessing.threadpool.size - Monitors the number of background threads in the thread pool.

  • ohi.activityprocessing.grid.submission.tasks - Counts the number of submission tasks created.

  • ohi.activityprocessing.grid.submissions - Counts the number of activities successfully submitted into the grid.

  • ohi.activityprocessing.grid.started - Monitors the work distribution over the nodes in the grid.

  • ohi.activityprocessing.grid.executing - Monitors of work to be completed.

  • ohi.activityprocessing.grid.completed -Monitors the completed work.

Documentation Links:
Administration Guide - Activity Processing Metrics

AUT-3561

Remove environment identifier from healthcheck

As part of this enhancement, environment identifier has been removed from healthcheck.

CPN-2672

JET UI pages to configure Schedule Definitions, Languages, Default Time Period

With this enhancement, the application gives the capability to configure Schedule Definitions, Languages, and Default Time Periods using the JET user interface.

CPN-2673

This enhancement introduces a page for change event rule

A new Jet UI page is introduced for change event rule.

Documentation Links:
Configuration Guide

NXT-24398

Cache query (by code) results on configuration entities

This enhancement implements caching for all the configuration entities using code. This has been previously implemented only for a few entities.

NXT-25486

Multiscreen support in JET

This enhancement adds multiple screens with tabs feature to JET to allow users to switch between the screens easily.

NXT-26188

Update the field definition on a dynamic field usage

This enhancement introduces the ability to update field definitions on a dynamic field usage.

Documentation Links:
Configuration Guide - Example 1

NXT-26266

JET: Enhance View and Edit template to support different layouts for information presentation

This enhancement introduces a new component Form. Form component allows for multi sections - multi column configuration.

This enhancement also makes it possible to have a multi column configuration within the region component.

Documentation Links:
Developer Guide - Form Component
Developer Guide - Region Component

NXT-27054

Extend init condition evaluation for multivalued records in region/tab

Support Initialization conditions (initCondition) at region/tab level for multi-values records.

NXT-27369

Upgrade to Java 11 and WebLogic 14.1.1

This enhancement upgrades Java to version 11 and WebLogic to version 14.1.1. See "Additional Upgrade Steps for Installation" below and the installation guide for more details.

Documentation Links:
Installation Guide

NXT-27376

Migration of credentials from OPSS to ohistore

Weblogic 14.1.0.0 has removed support for OPSS; hence, existing secrets must be migrated to a new secret store.

Documentation Links:
Developer Guide - Credentials
Developer Guide - Keystores
Installation Guide - Migrate Credentials between Different Secret Stores

NXT-27927

UI: Download feature in Results Component

This enhancement introduces the ability to download data displayed within the results component in search pages and tabs in view and edit pages.

Documentation Links:
Developer Guide - Component - Results

NXT-28084

Medicare: address entity changes

This enhancement introduces the county and stateAndCountyCode attributes to the address entity.

NXT-28145

UI: Dynamic fields integer formatting

This enhancement introduces the ability to display numeric fields as 1) Number - with locale-driven formatting and 2) Integer - without formatting.

The system data type number can be overwritten by specifying 1) a number-format setting for dynamic fields (configurable at the usage) or 2) a format attribute within the floorplan.

Documentation Links:
Developer Guide - Setting format for numeric datatypes
Developer Guide - Setting format for dynamic field usages

NXT-28213

UI: Application to support Small and Large scales

This enhancement introduces the possibility for the user to choose an application scale 1) large or 2) small by setting the user preference attribute Large fonts? Large fonts, when set to false, apply small scale to the application.

POL-12478

Exclude reference resources for generic GET operation

This enhancement introduces a new resource representation parameter excludereferenceresources. When set to true, it excludes the list and reference resources from the generic GET response.

Additionally, for the search requests originating from UI, excludereferenceresources is set to true, that is, to retrieve only the required details.

Documentation Links:
Developer Guide - Exclude reference resources

POL-13552

JET: Default override for UI operations

For the API requests originating from the UI for create, update, and delete operations, the defaultoverride parameter is set to true to reduce the overall response payload.

Documentation Links:
Developer Guide - Defaultoverride

POL-13590

UI: Deeplinks to support full screen mode

This enhancement will make it possible to configure deep links to open in a 1) Drawer or 2) full screen in a new tab in the view mode.

Documentation Links:
Developer Guide - Setting deeplinkType

POL-14103

Ability to access PII in base views

By default, the base views exclude all columns and dynamic fields that contain Personally Identifiable Information (PII). This enhancement introduces a system property that overrides this behavior, so that PII data elements become available in base views. This feature enables customers to use base views to create reports that contain PII.

POL-14188

Check the validity of the concealment’s regular expression on the IdentifierType

This enhancement adds a check on the validity of the concealment’s regular expression of the Identifier Type.

Documentation Links:
Configuration Guide - Identifier Types
Security Guide - Identifier Type Access Restriction

POL-3449

UI: Keyboard shortcuts

This enhancement introduces configurable shortcut keys for header’s action buttons.

Documentation Links:
Administration Guide

Additional Upgrade Steps

This section describes the steps that a functional application manager will take during the upgrade. These steps to be performed as an application user who is authorized to access the IPs.

Pre-Upgrade Phase

  1. Export the keystore from OPSS/Vault

    Invoke the following "GET" request to export the keystore: http://[hostName]:[portNumber]/[api-context-root]/keystores/export. The response of this request can be saved anywhere on the file system as e.g. keystores.json.

  2. Export the credentials from OPSS/Vault

    Invoke the following "GET" request to export the credentials: http://[hostName]:[portNumber]/[api-context-root]/credentials/export. The response of this request can be saved anywhere on the file system as e.g. credentials.json.

Post-Deploy Phase

  1. Import the saved keystore

    Invoke the following "POST" request to import the keystore: http://[hostName]:[portNumber]/[api-context-root]/keystores/import. This request will take the previously saved file as the input (e.g. keystores.json). The parameter name is "keystore".

  2. Import the saved credentials

    Invoke the following "POST" request to import the keystore: http://[hostName]:[portNumber]/[api-context-root]/credentials/import. This request will take the previously saved file as the input (e.g. credentials.json). The parameter name is "credentials".

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 ohi-credential-store-install.sh to create credential store schema.

    3. 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 has run.

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

Pre-Upgrade phase

  1. Verify that version 4.23.1.0.1 or later is installed.

  2. Configure property "ohi.credential.migration.enabled" either in the database or property file and set the property value to "true". This property will allow the end user to access the endpoint to export/import the secrets i.e. keystore and credentialstore.

  3. Restart the application for the change to take effect.

  4. Have the Application User user export the keystore and credentials as described earlier in this document.

Post-Undeploy phase

  1. Upgrade to JDK 11 and WebLogic 14.1.1.0

    4.23.2.0.0 major release of OHI applications are certified to work with Java 11 and Weblogic 14.1.1.0. See the Installation Guide, section "Required Software", for an overview of the minimal patches that must be applied. Java and Weblogic software should be installed before the upgrade.

    1. Install the latest JDK 11 (11.0.3 or higher patch version)

    2. Install WebLogic 14.1.1.0.0. Make sure to use the "Generic Installer"

    3. Install the mandatory patches as mentioned in "Required Software" section of the Installation Guide

    4. Stop the managed servers, admin server and node manager in the existing WebLogic 12.2.1.4 domain

    5. Take a backup of the existing domain directory

    6. The existing domain that was created using Oracle Fusion Middleware 12.2.1.4 can not be upgraded to WebLogic 14.1.1.0.0. So, a new domain needs to be created:

      • Set JAVA_HOME to Java 11 before creating a new domain using configuration wizard

      • See the sections "Install and Configure Oracle WebLogic" and "Install Application" in the Installation Guide for more details

      • Copy the contents of set<Application>Env.sh (mentioned in "Install and Configure Oracle Fusion Middleware" section of the Installation Guide) from the existing domain to the new domain (review the contents before copying and make changes if necessary)

      • Review any additional configuration/JAVA_OPTIONS from the existing domain such as the changes made to startWebLogic.sh etc and make similar changes in the new domain

Post-Upgrade phase

Action: Applicable for SaaS deployments/AMS team: configure property "ohi.baseview.exclude.pii" in the property file and set the property value to "true". This property when set to false will allow the end user to access PII data in baseviews. In case SaaS customer wants to flip value of property then they need to raise ticket to AMS team.

Post-Deploy phase

  1. Have the Application User user import the keystore and credentials as described earlier in this document.

  2. Configure property "ohi.credential.migration.enabled" either in the database or property file and set the property value to "false". This property will disable end user access to the endpoint to export the secrets i.e. keystore and credentialstore.

  3. Restart the application for the change to take effect.

Configuration Properties

Ref Action Description

NXT-27376

Modified

NXT-27376

Allowed values for property "ohi.secure.secrets.store" are one of the following: "vault", "ohistore".

POL-14103

Added

ohi.baseview.exclude.pii

This new boolean property controls whether Personally Identifiable Information (PII) is included in base views. By default, PII is excluded from base views. SaaS customers can change the value of this property by submitting a service request.

Web Services

Ref Action Description

NXT-27376

Added

Export Keystores

Export existing keystores

NXT-27376

Added

Import Keystores

Import keystore

NXT-27376

Added

Import Credentials

Import credentials

NXT-27376

Added

Export Credentials

Export existing credentials

NXT-28084

Modified

addresses API

Added optional attributes: county and stateAndCountyCode

NXT-28084

Modified

persons IP/API

Added optional attributes county and stateAndCountyCode to Address

NXT-28084

Modified

organizations IP/API

Added optional attributes county and stateAndCountyCode to Address

Data Conversion

Ref Action Description

NXT-26266

Modified

All floorplans that support region

Region with set1, set2, set3 is converted to sets array

Dynamic Logic

This section intentionally left blank.

UI Changes

Ref Action Description

CPN-2672

Added

Schedule Definition

Schedule Definition Page is added

CPN-2672

Added

Languages

Languages Page is added

CPN-2672

Added

Time Periods

Time Periods Page is added

CPN-2673

Added

Change Event Rule(JET)(CP0016)

Page introduced to search and view Change Event Rules. In the view page, users with access can also select and update fields that need to be monitored under monitoring fields.

NXT-25486

Modified

All pages

Adds tabs feature to JET for easy switching between the pages/screens

NXT-26266

Modified

Claim, Claimlines, CTR claims, CTR claimlines

The floorplan for the mentioned pages is modified to support the form layout. Form layout is configurable for other View and Edit pages.

NXT-26266

Modified

Policy, Enrollment, Enrollment Product, Group client, Group account, and Product

The floorplan for the mentioned pages is modified to support the form layout. Form layout is configurable for other View and Edit pages.

NXT-27054

Added

Applicable to any page configured with init condition

InitCondition should support for Multi-value records when added in Region/Table.

NXT-27927

Modified

All Search pages and tabs results

Added capability to download results in a csv of search page and tabs for list configuration.

NXT-28145

Modified

Numeric Datatype Fields

For fields with number datatype, the formatting would be applied based on the field usage subtype. If the subtype is set to an integer, no number formatting is applied; otherwise, formatting is applied.

NXT-28145

Modified

Dynamic Field Usages

For dynamic field usages, the subtype would be picked up from the format’s value of property definition in the floorplan. If integer, no number formatting would be applied. Otherwise, number formatting would be applied.

NXT-28213

Added

Application Scaling/FontSize

JET applications support multiple Scales. 1. Large. 2. Small. Small is the default scale configured. Users can switch the scale value by using the checkbox present in the preference dialog.

POL-13590

Modified

Persons, Policies

Extended Deeplink Functionality to open the field PECOs and Policy Holder in a new tab on view.

POL-3449

Added

KeyboardShortcuts(CO0021)

Added keyboard shortcuts entry under user preferences dropdown. On clicking, a dialog opens up where user can view or update shortcut entries for page actions.Also added shortcuts enabled indicator under user preferences

Breaking Changes

Ref Action Description

AUT-3561

Removed

"environment" property

Now, as part of health response the above property is not there anymore.

NXT-27369

Modified

Timestamp

The default timestamp format in the error message argument has changed after the Java 11 upgrade. The format in use now is YYYY-MM-DDTHH:MM:SS.

Example: Error text before this release was, 'CLA-IP-LIMI-024: Start date-time "1/1/11 12:00 AM" cannot be greater than the end date-time "1/1/10 12:00 AM" of the transaction period'. This is now changed to 'CLA-IP-LIMI-024: Start date-time "2011-11-01T00:00:00" cannot be greater than the end date-time "2010-11-01T00:00:00" of the transaction period'.

NXT-27376

Modified

Replacement of OPSS/Vault

With the upgradation of Weblogic 14.1.0.0.x, the default secret store, which was earlier "OPSS," has been changed to "ohistore". The ohistore is a custom solution built within the product to provide similar functionality. If any secret has been stored in OPSS/Vault, then those are supposed to be migrated. See NXT-27376 for migration.

Bug Fixes

BugDB SR Internal Summary

35544858

3-33374204261

CPN-2612

Whenever there is a IP error response, errorCode, errorPath and errorDetails should be prefixed with 'o:' to follow the REST standards.

Description:

Few IP error responses are not inline with REST standards. 'o:' is missing.

Resolution:

Error response from IP is now inline with REST standards.

35794356

CPN-2789

Issue with diacritics search with special characters

Description:

While performing a diacritic search with a special character followed by a stoplist or stopword, the search ends with an unknown result set.

See E Oracle Text Supplied Stoplists for more information.

Resolution:

The issue is with the behavior of the Oracle text index with Stop list and Stop word functionality. When these stop list words are used along with special characters, then the same will not be indexed, and this leads to this issue; the same has been fixed by modifying the index metadata.

35794946

CPN-2791

Memory leakage with coherence processing pattern

Description:

DHL observed performance issues with activity processing; many activities got stuck during processing due to OOM.

Resolution:

Memory leakage was fixed in coherence.

36250730

CPN-3033

Length of OHI_ID_ARRAY database type is still 14 after upgrading to 4.23.1 release

Description:

Length of OHI_ID_ARRAY database type is still 14 after upgrading to 4.23.1 release

Resolution:

The length of OHI_ID_ARRAY database type is updated to 19

36244453

CPN-2757

Rate schedule lines table isn’t showing properly

Description:

Rate schedule lines table isn’t showing properly

Resolution:

Rate schedule line table issue fixed

35108741

CPN-2461

The order of dynamic records does not remain the same as what is configured on the Record Definition page

Description:

The dynamic record shows the fields in a different order than how it was configured.

Resolution:

The dynamic record shows the fields in the order in which they were configured. So, the fields are now displayed based on the sequence mentioned.

34962502

3-31180617981

CPN-2393

Edit mode is allowing multiple records for single value time valid record

Description:

Edit mode allows multiple records for Single Value Time Validity even after setting the “addNewRow”:”Never” in the floorplan. In individual providers, for create mode - Single Value Time validity, it’s not providing a new row when data is entered (which is expected). But for Edit mode - Single Value Time validity, it’s giving a new row when data is entered (which is NOT expected because “addNewRow”:”Never” is added in floorplan).

Resolution:

In edit mode AddNewRow functionality is working fine now if it is set to never

35548098

3-33515434791

CPN-2614

Improve log messages to point to log file when appropriate

Description:

Failure in parsing data file (XML type) in dynamic logic using fileReader binding wraps the original exception. Hence, the error reported in the dynamic logic execution does not contain detailed information to diagnose the failure.

Resolution:

A trace file is generated for unknown exceptions occurring in dynamic logic, and the error response message points to the trace file, which contains detailed information to diagnose the failure.

35867568

CPN-2828

Dynamic logic cache reloads every time on business cache invalidation, even if there is no dynamic logic update

Description:

Dynamic logic cache uses a business process cache, which is invalidated on any change in configuration entities (that implements ProcessCacheInvalidating) even though there is no change in dynamic logic itself. On invalidation of the cache, byte code is loaded again for all the dynamic logic, which is CPU intensive and can slow down other processes running in parallel during the class loading.

Resolution:

Now, the cache invalidation and reloading happen only on the changes in the dynamic logic entity.

Issues that were backported in previous Release / Patch

No backports.

Known Issues

BugDB SR Internal Summary

32477683

CPN-1431

No base view generated for reference sheet lines

Description:

Reference sheet line(s) use a different storage structure (JSON) for the dynamic fields. The base view generator does not support that yet. So, the reference sheet line columns can’t be queried using base views.

34401173

3-29621579461

CPN-2146

The CMT recovery process fails with a null pointer exception

Description:

During restart, the data set processes for CMT are cleaned up. As a result, the CMT recovery process fails with a null pointer exception.

34980215

3-31796002821

CPN-2418

Dynamic logic timeout property is ignored when compiling dynamic logic at startup time

Description:

The dynamic logic timeout property (ohi.dynamiclogic.timeout or ohi.dynamiclogic.timeout.{0}) is ignored when the dynamic logic is compiled at system startup time.

35031585

3-31969350441

CPN-2430

Query API cannot handle optional fields with flex code definition requesting combination with null

Description:

When you do a query search with a combination of a null, for instance (multicore.eq('Y').or.multicore.eq(null)). The result shows the records with value Y, not those with a null value.

35513644

CPN-2595

Person code generation dynamiclogic is not used to construct the person code, even after activating the dynamiclogic that has signature Person Code generation.

Description:

Person code generation dynamiclogic is not used to construct the person code, even after activating the dynamiclogic that has signature Person Code Generation.

36150413

CPN-2687

Individual providers - Unable to edit service address configured as deeplink in rendering address tab

Description:

It is not possible to edit resources which are configured as Deeplinks. For example in Individual providers, it is not possible to edit service address in rendering address tab. On click of edit button in service address drawer, its directly navigating back to individual providers page and not possible to edit/save

35686859

CPN-2724

Reset Query Statistics - in Monitor Dynamic Logic Querying

Description:

When we query something in the testunit dynamic logic and then invoke/test another dynamic logic in the same testunit dynamic logic, the value/count for all query parameters displays incorrect

35684770

CPN-2727

For certain special LOV properties configured in the floorplan with suffix 'JET' ,upon selecting a value, the focus moves out of the table row

Description:

On selecting a value from dropdown for special functional LOV properties in table pages, the focus moves out of the table row

36189836

CPN-2980

Execute datafile incident cleanup job (scavenging scheduler job) only on single node

Description:

The datafile set scavenging/cleanup job is scheduled to clean up application incidents (trace files) every day at midnight.

This Spring scheduling job is executed on all the nodes, which is an unwanted use of resources, it is it would be efficient to run this only once (eg: on the master/oldest node in the coherence cluster).

36194711

CPN-2991

Add new row is shown at last in table pages

Description:

Click Add new in table page. A new row is getting appended in the last visible row of the screen

36236317

CPN-2993

Incorrect result showing in Boilerplates Table.

Description:

The boilerplate table shows incorrect results after performing the 'ADD' and then 'CANCEL' actions simultaneously. This behavior is generic to other table-based pages.

36204113

3-34786906091

CPN-3007

Dynamic logic byte code is not loaded during server startup on non master nodes after invalidateall IP is invoked

Description:

Dynamic logic byte code was not loaded during server startup on non-master nodes after invalidateall IP was invoked. It was instead getting loaded at the actual dynamic logic execution time.

36220232

CPN-3021

Relation Links aren’t removed for a relation when empty list is given as payload

Description:

Unable to delete Relation Links by giving empty relation link list as payload for Persons IP.

36195745

CPN-3035

Download: All Records are not showing in downloaded file even after scrolling, only 10 records showing in table.

Description:

The download feature in the table is not working properly. When a user scrolls through a set of records and tries to download the data in the table, the downloaded file doesn’t show the correct result.

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

NXT-25662

3.22.2.0.0

The support to GET operations on Query API calls is deprecated.

Reference Document