Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.2.0.5

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

Version compatibility: Oracle Health Insurance Enterprise Policy Administration 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

NXT-24066

WebLogic authentication implemented compliant with the Java Authorization and Authentication Service (JAAS) specification

This enhancement introduces support for the SAML 2.0 authentication mechanism in the Oracle Health Insurance. Additionally, a new JAR file named "CustomIdentityAsserter" has been created to accommodate the Basic Auth configuration.

Refer installation guide for further detail.

Documentation Links:
Installation Guide - Users and Authentication

3.22.2.0.26, 4.23.1.0.6

POL-13500

Tracking processed policy mutations

This enhancement introduces an ability to back up the processed policy mutations. This helps fix the premium calculation result after a configuration error and identifies the policies to recalculate.

POL-14287

UI: Premium and sample run results auto-expaned (default)

This enhancement allows the user to view the premium results expanded at a detailed level by default; to view an overview of the premium, click the collapse button.

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

Ref Action Description

POL-13500

Added

processedpolicymutation API

New API to retrieve (un)processed policy mutations

POL-13500

Modified

Cancel Policy

Store (un)processed policy mutations

POL-13500

Modified

Premium Calculation

Store processed policy mutations

POL-13500

Modified

Purge Policy

Purge processed policy mutations

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

Ref Action Description

POL-14287

Modified

Policies(PO0001)

Added a expand/collapse button to Example Calculation Dialog and View Premium Page. When the page opens the results are auto-expanded.

Breaking Changes

Ref Action Description

NXT-24066

Modified

Installation Configuration

Customers using the Basic Authentication mechanism must follow the installation guide to install the newly built JAR file, "CustomIdentityAsserter.jar," and configure the WebLogic security provider accordingly.

Bug Fixes

BugDB SR Internal Summary

36752302

3-37045628421

POL-15340

The page keeps loading while trying to add fields under usage

Description:

Go to 'Usages'. Select any usage, click on add then select field. We should be able to add a field/record under usage

Resolution:

It is possible to add a field/record under Usage and page opens without any issues

36809661

3-36452370811

POL-15456

Advanced search lov’s for dynamic fields are not loading in referencesheetlines

Description:

Not able to search using the LOV’s in the reference sheet lines page. When clicking in the LOV field an error occurs on the api/generic/flexcodes/search.

Resolution:

Proper results are displayed in the LOV for flexcodes based on diagnosis, procedures and providers, displays.

36744401

POL-15330

Unable to apply update trigger on resource 'attachedpolicydata' in Change Event Rules page

Description:

The user is unable to apply Update Trigger on resource 'attachedpolicydata' in changeEventRules page.

Resolution:

The user can now update monitoring fields for the entity 'attachedpolicydata' provided they have the correct access grants.

36270211

POL-14354

Incorrect result shown 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.

Resolution:

Correct results are shown after performing the 'ADD' and then 'CANCEL' actions simultaneously in table-based pages

36813394

3-37120352731

POL-15462

Select Financial Transaction into Set activity failing with GEN-PROC-ERR

Description:

When Financial Transaction into Set activity is ran with financailTransactionType 'PRE', activity is failing with technical error.

Resolution:

Extra spaces was introduced in dynamic sql query generation which fixed the issue allowing the activity to get successfully completed.

36194691

POL-14347

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

Resolution:

Table component is modified with the below changes: 1) On click of Add button, a new row will be added to the top of the available rows. It is a sticky row to the table 2) Two new icons are added to a new row. Check icon would add the new row to the table and clicking on Cross icon would discard the new row. 3) User will have to click on Check icon and Save to persist the newly added data

36833476

3-36864108701,3-37393890291

POL-15489

Issue with display of flexcodes in piechart for widget

Description:

Create a piechart widget with grouping criteria set on flex codes. Piechart doesn’t show flexcode names instead shows FlexCodeDomain(..)

Resolution:

PieChart widgets shows flexcode names properly when set as grouping criteria

36195780

POL-14359

All records are not shown in downloaded file, only 10 records are shown even after scrolling in table page

Description:

When a user scrolls through a set of records and clicks on download action in the table, the downloaded file doesn’t show the correct result.

Resolution:

All the records viewed in the table page is downloaded to the file when clicked on download action

36823254

POL-15476

Integer field values are shown with separator (12,345 instead of 12345)

Description:

Enter '12345' in integer fields like "house number" or state and country code" in Persons page, it is getting displayed as 12,345

Resolution:

Integer field values are shown without separators now

Issues that were backported in previous Release / Patch

No backports.