Release Notes for Oracle Health Insurance Product Definition Patch 4.25.1.0.10

This document contains the release notes for Oracle Health Insurance Product Definition Patch 4.25.1.0.10.

Version compatibility: Oracle Health Insurance Product Definition 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
PRD-3808	The Set Product Status integration point will allow user to change the status of multiple Products in a single operation This enhancement allows users to change the status of multiple products to Edit, Review, Test, or Approved in a single operation. In the Products list, users select the products and choose a target status from the Set Status menu. Documentation Links: Configuration Guide - Set Product Status integration point Configuration Guide - Set the status of multiple products in the Product UI

Summary

Patch

PRD-3808

The Set Product Status integration point will allow user to change the status of multiple Products in a single operation

This enhancement allows users to change the status of multiple products to Edit, Review, Test, or Approved in a single operation. In the Products list, users select the products and choose a target status from the Set Status menu.

Documentation Links:
Configuration Guide - Set Product Status integration point
Configuration Guide - Set the status of multiple products in the Product UI

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 of ohi_install.cfg.template and name it ohi_install.cfg.
Edit ohi_install.cfg to 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:
1. Open a command window and browse to <OHI_ROOT>/util/install.
2. 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

Configuration Properties

This section intentionally left blank.

Web Services

Ref	Action	Description
PRD-3808	Added	PR0067 New integration point allows users to set the status of multiple products in a single request.

Ref

Action

Description

PRD-3808

Added

PR0067

New integration point allows users to set the status of multiple products in a single request.

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

Ref	Action	Description
PRD-3808	Modified	PR0014 (Products search page) New Action button 'Set product status' added to do bulk status updates

Ref

Action

Description

PRD-3808

Modified

PR0014 (Products search page)

New Action button 'Set product status' added to do bulk status updates

Breaking Changes

This section intentionally left blank.

Access Restrictions

This section intentionally left blank.

Bug Fixes

BugDB	SR	Internal	Summary
39756685		PRD-5731	Enhance Extend UI download feature to include full search result set
Description:	API based download has been enabled for all the pages.
Resolution:	A descriptive message will be displayed to the end user, indicating the number of rows being downloaded. With this fix, all generic audit properties will be translated and displayed correctly. For list-based attributes, such as Ben Spec Location List and Ben Spec Specific Networks in generated products, the individual fields of the list will be downloaded in a single column. Documentation Links for more Details: Developer Guide - Integration - HTTP API - Download API
39658746		PRD-5635	addservicedefinition IP country region field needs to pass unique identifier
Description:	Country-region field uses code as a non-unique business attribute - multiple records can share the same code (e.g. two rows both coded CA, distinguished only by id, e.g. 1234 and 2345). addProductServiceDefinitions currently resolves these fields by code, so it always binds to the first matching row from country region table.
Resolution:	Updated Add Product Service Definitions IP to identify country regions using the combination of countryRegionCode and countryCode, instead of resolving by country region code alone. This ensures the correct country region is selected when multiple country regions share the same code.

BugDB

Internal

Summary

39756685

PRD-5731

Enhance Extend UI download feature to include full search result set

Description:

API based download has been enabled for all the pages.

Resolution:

A descriptive message will be displayed to the end user, indicating the number of rows being downloaded.
With this fix, all generic audit properties will be translated and displayed correctly.
For list-based attributes, such as Ben Spec Location List and Ben Spec Specific Networks in generated products, the individual fields of the list will be downloaded in a single column.

Documentation Links for more Details:

Developer Guide - Integration - HTTP API - Download API

39658746

PRD-5635

addservicedefinition IP country region field needs to pass unique identifier

Description:

Country-region field uses code as a non-unique business attribute - multiple records can share the same code (e.g. two rows both coded CA, distinguished only by id, e.g. 1234 and 2345). addProductServiceDefinitions currently resolves these fields by code, so it always binds to the first matching row from country region table.

Resolution:

Updated Add Product Service Definitions IP to identify country regions using the combination of countryRegionCode and countryCode, instead of resolving by country region code alone. This ensures the correct country region is selected when multiple country regions share the same code.

Issues that were backported in previous Release / Patch

No backports.