Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.24.1.0.10

This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.24.1.0.10.

Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 4.24.1.x is only compatible with other Oracle Health Insurance applications release version 4.24.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

No enhancements.

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

Configuration Properties

This section intentionally left blank.

Web Services

This section intentionally left blank.

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal Summary

37833675

3-40355957991

POL-16970

API access restriction parameterdomain missing when a role has PO0012 Enrollment page access

Description:

When a user with a specific access role that includes the PO0012 Enrollment Products JET access restriction tries to view a parameter domain value, an error message stating "Not Authorized on this resource" is displayed.

Resolution:

Added missing API access restrictions for page access and floorplan resource updated from parameterdomain to enrollmentproductparameterdomain to resolve the issue. The same modification should be applied to custom floorplans, if configured.

37872667

POL-17065

Accounting details are not assembled correctly in financial message when signature 'Create accounting detail with dual for financial transaction' is used.

Description:

When the signature 'Create accounting detail with dual for financial transaction' is used to create and generate non-invoiced accounting details, the same accounting detail is showed twice (so either the dual or non-dual one) in the financial message, while it should be one entry for non-dual and one for dual accounting detail.

Resolution:

The non-accounting details show both the dual and non-dual accounting details.

37633510

3-40449586751

POL-16697

Prefilter criteria is retained when multiple custom floorplans are configured in Payment Registrations page

Description:

In Payment Registrations page, when multiple custom floor plans are configured with at least one floorplan with prefilter option, prefilter criteria is retained and not cleared while switching between the floorplans

Resolution:

Pre-filter criteria is cleared while switching between the floorplans

37907444

3-40346571471

POL-17099

Not able to retrieve parent context values in view mode of the page in a tab

Description:

For a use case when a user wants to filter out a field in the tab, based on the type of the claim, the following condition works correctly in create mode : "condition": "context.claim.type === 'R'". It does not work when the page is opened in view mode

Resolution:

For tab details pages conditional evaluation issue fixed for both create and edit mode

37908290

3-38056877861

POL-17104

Labels for regular flex code fields are not working while configuring it in search page

Description:

Labels are not getting displayed in search page, it works fine in hierarchical recursive page

Resolution:

Labels for flex code fields are working as expected when configured in search page

37944423

3-40662938551

POL-17162

user information is not available to use in floorplans using userJET property

Description:

the userJET property in the floorplan does not support setting default values or filtering data based on the current user.

Resolution:

id and displayName fields of userJET property can be used in the floorplan for setting default values or filtering data based on the current user.

37908945

3-39962052161

POL-17107

Number format Type is not working in JET for number fields

Description:

Number format type is not working (Integer/Number/Formatted integer) except for Amount. It is not possible to show a numeric field in integer format without comas

Resolution:

It is possible to show a numeric field in integer format without comas and formatting works fine in JET

37888926

3-40493278681

POL-17078

Setting flex codes on registrations in dynamic logic of policy validation signature is not allowed.

Description:

Setting dynamic field on Registration entity in Policy Validation Rule dynamic logic throws UnsupportedOperationDynamicLogicException error.

Resolution:

All types of dynamic fields can be set on registrations in dynamic logic of policy validation signature.

37908013

3-40316102201

POL-17101

Expand/Collapse is shown even when there is no tab

Description:

When tab is not configured expand / collapse should be not visible

Resolution:

Expand / Collapse link is visible only if tab is configured, if tab is not there in floorplan then it will be hidden

37925950

3-40617866901

POL-17146

Regenerate of a baseviews throws 405 response

Description:

POST http://{hostname}/<context>/baseviews/<baseViewName>/regenerate gives a 405 Method not allowed error.

Resolution:

The regenerate operation now generates a GET link using /generic/baseviews/{baseViewId}

Issues that were backported in previous Release / Patch

No backports.