Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.21.3.0.6

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

Enhancements

ID	Summary	Description	Included in Patch
NXT-21416	Use Vault as alternative secrets store with WebLogic deployments	Next to Fusion Middleware / WebLogic Oracle Platform Security Services (OPSS), OHI applications also support HashiCorp Vault as alternative secrets store. See the Installation Guide for details.
POL-9643	IETF RFC2882 Email Format Support	This enhancement enables the use of email addresses according to the IETF RFC2882 standard in Relations and Providers

Summary

Description

Included in Patch

NXT-21416

Use Vault as alternative secrets store with WebLogic deployments

Next to Fusion Middleware / WebLogic Oracle Platform Security Services (OPSS), OHI applications also support HashiCorp Vault as alternative secrets store. See the Installation Guide for details.

POL-9643

IETF RFC2882 Email Format Support

This enhancement enables the use of email addresses according to the IETF RFC2882 standard in Relations and Providers

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

Ref	Action	Subject	Description
NXT-21416	Added	ohi.vault.clientpem.url	Resource URL to Vault Client pem
NXT-21416	Added	ohi.vault.clientkeypem.url	Resource URL to Vault Client Key pem
NXT-21416	Added	ohi.vault.address	Vault address. Must use HTTPS
NXT-21416	Added	ohi.vault.environment.identifier	To distinguish secrets on a per OHI application instance basis
NXT-21416	Added	ohi.secure.secrets.store	The type of store the OHI application uses for secrets
NXT-21416	Added	ohi.vault.kv.secrets.engine	By default, OHI applications assume that Vault’s Key-Value secrets engine is enabled at root path "secret"
NXT-21416	Added	ohi.vault.namespace	OHI specific Vault namespace section, under the path determined by properties ohi.vault.kv.secrets.engine/ohi.vault.namespace to look for secrets
NXT-21416	Added	ohi.vault.token	Vault token
NXT-21416	Added	ohi.vault.pem.url	Resource URL to Vault pem

Ref

Action

Subject

Description

NXT-21416

Added

ohi.vault.clientpem.url

Resource URL to Vault Client pem

NXT-21416

Added

ohi.vault.clientkeypem.url

Resource URL to Vault Client Key pem

NXT-21416

Added

ohi.vault.address

Vault address. Must use HTTPS

NXT-21416

Added

ohi.vault.environment.identifier

To distinguish secrets on a per OHI application instance basis

NXT-21416

Added

ohi.secure.secrets.store

The type of store the OHI application uses for secrets

NXT-21416

Added

ohi.vault.kv.secrets.engine

By default, OHI applications assume that Vault’s Key-Value secrets engine is enabled at root path "secret"

NXT-21416

Added

ohi.vault.namespace

OHI specific Vault namespace section, under the path determined by properties ohi.vault.kv.secrets.engine/ohi.vault.namespace to look for secrets

NXT-21416

Added

ohi.vault.token

Vault token

NXT-21416

Added

ohi.vault.pem.url

Resource URL to Vault pem

Web Services

This section intentionally left blank.

Data Conversion

This section intentionally left blank.

Dynamic Logic

Ref	Action	Subject	Description
POL-9541	Modified	Bulk Update Definition	Fixed GEN-TMVL-008 error when using copyAndEndDateEnrollmentProduct on a Policy Enrollment with time valid Parameter Values

Ref

Action

Subject

Description

POL-9541

Modified

Bulk Update Definition

Fixed GEN-TMVL-008 error when using copyAndEndDateEnrollmentProduct on a Policy Enrollment with time valid Parameter Values

UI Changes

Ref	Action	Subject	Description
POL-9438	Modified	amount field	The amount value should be restricted by the min or max range as specified by the metadata with maximum precision set to 4 decimal places. If metadata has decimal limit 1- 4 then use the same in UI else if it is more than 4 in metadata then truncate the decimal length to 4.

Ref

Action

Subject

Description

POL-9438

Modified

amount field

The amount value should be restricted by the min or max range as specified by the metadata with maximum precision set to 4 decimal places. If metadata has decimal limit 1- 4 then use the same in UI else if it is more than 4 in metadata then truncate the decimal length to 4.

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB	SR	Internal	BP	Summary
33564097		POL-9527	BP	User is not able to create a new insurable entity type as person from JET UI
Description:	Entering a new Insurable Entity Type is not possible in the JET UI (PERSON). It throws an error that the access restriction already exists
Resolution:	User is able to create a new insurable entity type as person from JET UI
33569064	3-27358614881	POL-9542	BP	Bulk Update fails when using copyAndEndDateEnrollmentProduct on a Policy Enrollment with a time valid Parameter Value
Description:	GEN-TMVL-008 error (for parameter value) is raised when copyAndEndDateEnrollmentProduct pre-defined method is used in bulk update definition dynamic logic on an approved Policy which has Policy Enrollment Product Parameter Values with start date later than the newStartDate parameter passed in to the pre-defined method copyAndEndDateEnrollmentProduct.
Resolution:	The Parameter Values causing the GEN-TMVL-008 error are properly removed.
33668873	3-27944936671	POL-9710	BP	Matching on policyholder and policy enrollment goes wrong when relation identifier is used in payload in Policy In Integration Point
Description:	The match on policyholder and policy enrollment (in case it is a person) is false always for requests where relation identifier is used to identify the person. This leads to always delete and remove of policyholder and policy enrollment, hence creating unnecessary policy events and triggering of several processes like premium calculation.
Resolution:	The policyholder(s) and policy enrollment(s) are now properly matched.
33669669	3-27896665871	POL-9713	BP	CMT import stops when a Dynamic Logic contains regexp character(s) fails
Description:	When import of dynamic logic containing regexp character(s) fails (for example if the dynamic logic referenced in that dynamic logic could not be found), then CMT stops importing any other entities and the result is shown as success.
Resolution:	CMT import is shown as failure when import of dynamic logic with regexp character(s) fails. And all the other entities are imported.
33677698		POL-9736		ADF UI Isse - Picklist does not work
Description:	When a picklist is chosen in a Record field of Dynamic Record definition, the LOV for that particular field does not work fine. Blank Search in the LOV and the OK, Cancel buttons do not work fine.
Resolution:	When a picklist is chosen in a Record field of Dynamic Record definition, the LOV for that particular field now works fine. Blank Search, Ok, Cancel buttons work as expected.
33678810	3-27874164671	POL-9742	BP	Bp - 3.21.3 - OHI.ENVIRONMENT.IDENTIFIER IS Set But SHOWS AS UNDEFINED IN THE PAGE.
Description:	OHI.ENVIRONMENT.IDENTIFIER IS SET BUT SHOWS AS UNDEFINED IN THE PAGE
Resolution:	Added the environment details to session , which is common for different login gateways
33679574	3-27942896191	POL-9743	BP	Boilerplate text created for links is not replaced, unless it is referred to in lowercase
Description:	When the user creates a boilerplate text for links and mentions it in links in uppercase, it is not replaced unless it is referred to in lowercase.
Resolution:	Any boilerplates given for links will be replaced in UI irrespective of the casing of letters.
33710928		POL-9768	BP	Correct floorplan is not getting picked from Create Policy tile when custom floorplans are available
Description:	When custom floorplan is enabled and clicked on create policy tile, even if selected system specific floorplan, the policy page is loaded with custom floorplan.
Resolution:	User will be able to choose which floorplan to render when creating a policy.
33750543		POL-9821	BP	The amount value precision is set to 4 decimal places, it should ideally be 2 decimal places
Description:	The amount value should be restricted by the min or max range as specified by the metadata with maximum precision set to 4 decimal places. If metadata has decimal limit 1- 4 then use the same in UI else if it is more than 4 in metadata then truncate the decimal length to 4.
Resolution:	The amount value is restricted by the min or max range as specified by the metadata by using max and min precision to set decimal places by taking decimal length from metadata for moneyFieldValidator. decimal limit is set to 4 as specified in metadata, if it exceeds 4 then will be truncated using roundingMode as FLOOR.
33750589		POL-9822	BP	Flex code definition page: have to click twice on the save button when editing an existing record
Description:	After clicking Edit and then Save Button, on Flex code definition page, the page remains in Edit mode. Clicking on Save Button again will only save data and the page will be in View mode.
Resolution:	Page will be in View mode after Edit and Save action.
33708543		POL-9767	BP	Review stage of adding usage to floorplan, shows "In tab add as : list with detail page, even if table is selected
Description:	On Usages Page, the Review Stage of Add to Floorplan actions shows "In tab add as" field shows value as "list with detail page" even if the table is selected.
Resolution:	Proper options are shown for HRR & table templates in Usages page when the user is in Review Station of Add to Floorplan action

BugDB

Internal

Summary

33564097

POL-9527

User is not able to create a new insurable entity type as person from JET UI

Description:

Entering a new Insurable Entity Type is not possible in the JET UI (PERSON). It throws an error that the access restriction already exists

Resolution:

User is able to create a new insurable entity type as person from JET UI

33569064

3-27358614881

POL-9542

Bulk Update fails when using copyAndEndDateEnrollmentProduct on a Policy Enrollment with a time valid Parameter Value

Description:

GEN-TMVL-008 error (for parameter value) is raised when copyAndEndDateEnrollmentProduct pre-defined method is used in bulk update definition dynamic logic on an approved Policy which has Policy Enrollment Product Parameter Values with start date later than the newStartDate parameter passed in to the pre-defined method copyAndEndDateEnrollmentProduct.

Resolution:

The Parameter Values causing the GEN-TMVL-008 error are properly removed.

33668873

3-27944936671

POL-9710

Matching on policyholder and policy enrollment goes wrong when relation identifier is used in payload in Policy In Integration Point

Description:

The match on policyholder and policy enrollment (in case it is a person) is false always for requests where relation identifier is used to identify the person. This leads to always delete and remove of policyholder and policy enrollment, hence creating unnecessary policy events and triggering of several processes like premium calculation.

Resolution:

The policyholder(s) and policy enrollment(s) are now properly matched.

33669669

3-27896665871

POL-9713

CMT import stops when a Dynamic Logic contains regexp character(s) fails

Description:

When import of dynamic logic containing regexp character(s) fails (for example if the dynamic logic referenced in that dynamic logic could not be found), then CMT stops importing any other entities and the result is shown as success.

Resolution:

CMT import is shown as failure when import of dynamic logic with regexp character(s) fails. And all the other entities are imported.

33677698

POL-9736

ADF UI Isse - Picklist does not work

Description:

When a picklist is chosen in a Record field of Dynamic Record definition, the LOV for that particular field does not work fine. Blank Search in the LOV and the OK, Cancel buttons do not work fine.

Resolution:

When a picklist is chosen in a Record field of Dynamic Record definition, the LOV for that particular field now works fine. Blank Search, Ok, Cancel buttons work as expected.

33678810

3-27874164671

POL-9742

Bp - 3.21.3 - OHI.ENVIRONMENT.IDENTIFIER IS Set But SHOWS AS UNDEFINED IN THE PAGE.

Description:

OHI.ENVIRONMENT.IDENTIFIER IS SET BUT SHOWS AS UNDEFINED IN THE PAGE

Resolution:

Added the environment details to session , which is common for different login gateways

33679574

3-27942896191

POL-9743

Boilerplate text created for links is not replaced, unless it is referred to in lowercase

Description:

When the user creates a boilerplate text for links and mentions it in links in uppercase, it is not replaced unless it is referred to in lowercase.

Resolution:

Any boilerplates given for links will be replaced in UI irrespective of the casing of letters.

33710928

POL-9768

Correct floorplan is not getting picked from Create Policy tile when custom floorplans are available

Description:

When custom floorplan is enabled and clicked on create policy tile, even if selected system specific floorplan, the policy page is loaded with custom floorplan.

Resolution:

User will be able to choose which floorplan to render when creating a policy.

33750543

POL-9821

The amount value precision is set to 4 decimal places, it should ideally be 2 decimal places

Description:

Resolution:

The amount value is restricted by the min or max range as specified by the metadata by using max and min precision to set decimal places by taking decimal length from metadata for moneyFieldValidator. decimal limit is set to 4 as specified in metadata, if it exceeds 4 then will be truncated using roundingMode as FLOOR.

33750589

POL-9822

Flex code definition page: have to click twice on the save button when editing an existing record

Description:

After clicking Edit and then Save Button, on Flex code definition page, the page remains in Edit mode. Clicking on Save Button again will only save data and the page will be in View mode.

Resolution:

Page will be in View mode after Edit and Save action.

33708543

POL-9767

Review stage of adding usage to floorplan, shows "In tab add as : list with detail page, even if table is selected

Description:

On Usages Page, the Review Stage of Add to Floorplan actions shows "In tab add as" field shows value as "list with detail page" even if the table is selected.

Resolution:

Proper options are shown for HRR & table templates in Usages page when the user is in Review Station of Add to Floorplan action

Issues that were backported in previous Release / Patch

No backports.