Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.2.0.7

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

Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 3.22.2.x is only compatible with other Oracle Health Insurance applications release version 3.22.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-2954	Include JVM GC metrics in Prometheus Metrics for GC monitoring have been added, controlled by a number of system properties: JVM metrics are enabled by ohi.instrumentation.gather.jvm (this used to be ohi.instrumentation.gather.jvmtelemetry) System metrics are enabled by ohi.instrumentation.gather.system (this used to be ohi.instrumentation.gather.jvmtelemetry) Garbage Collection metrics are enabled by ohi.instrumentation.gather.gc	3.22.1.0.12
POL-11479	Enhanced Policy Update Request With this enhancement an the Policy update request now supports Receiving File based update requests Enrollment File Counts

Summary

Patch

AUT-2954

Include JVM GC metrics in Prometheus

Metrics for GC monitoring have been added, controlled by a number of system properties:

JVM metrics are enabled by ohi.instrumentation.gather.jvm (this used to be ohi.instrumentation.gather.jvmtelemetry)

System metrics are enabled by ohi.instrumentation.gather.system (this used to be ohi.instrumentation.gather.jvmtelemetry)

Garbage Collection metrics are enabled by ohi.instrumentation.gather.gc

3.22.1.0.12

POL-11479

Enhanced Policy Update Request

With this enhancement an the Policy update request now supports

Receiving File based update requests
Enrollment File Counts

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
POL-11479	Added	writepolicyupdaterequests IP New IP to start long running operation to import policy update requests using data file processing
POL-11479	Added	importpolicyupdaterequests API API to retrieve long running operations for file based import of policy update requests
POL-11479	Modified	Policy Update Request Operation The enrollment File counts are updated when a policy update request is applied to the policy either through the long running process or apply operation

Ref

Action

Description

POL-11479

Added

writepolicyupdaterequests IP

New IP to start long running operation to import policy update requests using data file processing

POL-11479

Added

importpolicyupdaterequests API

API to retrieve long running operations for file based import of policy update requests

POL-11479

Modified

Policy Update Request Operation

The enrollment File counts are updated when a policy update request is applied to the policy either through the long running process or apply operation

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

Ref	Action	Description
POL-11479	Modified	Policy Update Request Page, Policies Attached Data Page Sorting criteria updated for Policy Update Request page, Policies Attached Data Page modified to include Disable Update From Queue? flag

Ref

Action

Description

POL-11479

Modified

Policy Update Request Page, Policies Attached Data Page

Sorting criteria updated for Policy Update Request page, Policies Attached Data Page modified to include Disable Update From Queue? flag

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
35353856		POL-12737	BP	OOM error when processing large volume of connector configuration activities
Description:	The application was auto-restarted after encountering an OOM error while processing a large volume of connector config activities.
Resolution:	The child activities of the connector configuration were made to run in groups, which will avoid over usage of resources thus preventing OOM.
35330421		POL-12704	BP	Performance issue with collecting existing premium results during premium calculation.
Description:	The selection to fetch existing calculation results for a policy was inefficient.
Resolution:	Selection is changed, so it is utilizing the optimal search path.
35361093	3-32933090951	POL-12749	BP	Unable to load FastStringService class during dynamic logic execution
Description:	Executions of few dynamic logics in ongoing OHI operation fail with "java.lang.RuntimeException: Unable to load FastStringService" exception which prevents successful execution of ongoing operation.
Resolution:	Implemented mechanism to load FastStringService class at the application startup time so that it will be available later in dynamic logic execution
35175227	3-32295832461	POL-12443	BP	Translatable attributes of flex codes are not migrated for all the installed languages using CMT
Description:	Translatable attributes of flex codes are not migrated for all the installed languages using CMT
Resolution:	Translatable attributes of flex codes for all the installed languages are now migrated using CMT
35039274	3-31861452961	POL-12093	BP	Additional Logging for failing OHI Connector tasks
Description:	The OHI Connector makes use of the task processing framework. When a task fails, it gets into an errored state and the functionality stops working. Failing tasks are not indicated in the log files.
Resolution:	Added error logging for the OHI Connector, in such a way that if a task fails, it will show up in the Application logs. Besides that, the documentation is extended with information on the task processing framework for the OHI Connector.
35340438	3-32862871471	POL-12722	BP	Application doesn’t start if there are compilation error in the Dynamic Logic
Description:	The application startup failed when there were compilation issues with DYLO. The system throws the error which weren’t handled.
Resolution:	Handled the DYLO compilation error during the application startup. The application will start logging warning if there are compilation issue with DYLO.
35281690		POL-12611	BP	Dynamic record as tab list is not showing flexcode data
Description:	Flexcodes configured in the tab list/tab table configurations does not show value.
Resolution:	Flexcodes configured in the tab list/tab table configurations shows the value.
35297232	3-32774965581	POL-12655	BP	Process policy activity remains in InProcess status if java.lang.verifyerror occurs when executing dynamic logic
Description:	During Policy processing dynamic Logic is executed, as part of the Policy Process steps. When a mistake in the dynamic logic is encountered, the PROCESS_POLICY activity should fail in TE (Technical Error) status and the policy should be reverted to Edit status. But, in case a specific mistake is encountered while executing the dynamic logic (for example a java.lang.VerifyError), the PROCESS_POLICY activity does not fail and policy remains InProcess status.
Resolution:	If any dynamic logic error occurs while processing policy, now PROCESS_POLICY activity fails with status TE and the respective policy is reverted to Edit status.
35178157	3-32094585611	POL-12578	BP	Output definition activity is failing with technical error
Description:	Generate Output activity when triggered with multiple approved versions of the policy, created child activities for all the approved versions. This led to optimistic locking during the execution of the child activities.
Resolution:	Generate Output activity now creates child activities for only the last approved version of the policy when there exists multiple approved versions. The optimistic locking is no longer seen.

BugDB

Internal

Summary

35353856

POL-12737

OOM error when processing large volume of connector configuration activities

Description:

The application was auto-restarted after encountering an OOM error while processing a large volume of connector config activities.

Resolution:

The child activities of the connector configuration were made to run in groups, which will avoid over usage of resources thus preventing OOM.

35330421

POL-12704

Performance issue with collecting existing premium results during premium calculation.

Description:

The selection to fetch existing calculation results for a policy was inefficient.

Resolution:

Selection is changed, so it is utilizing the optimal search path.

35361093

3-32933090951

POL-12749

Unable to load FastStringService class during dynamic logic execution

Description:

Executions of few dynamic logics in ongoing OHI operation fail with "java.lang.RuntimeException: Unable to load FastStringService" exception which prevents successful execution of ongoing operation.

Resolution:

Implemented mechanism to load FastStringService class at the application startup time so that it will be available later in dynamic logic execution

35175227

3-32295832461

POL-12443

Translatable attributes of flex codes are not migrated for all the installed languages using CMT

Description:

Translatable attributes of flex codes are not migrated for all the installed languages using CMT

Resolution:

Translatable attributes of flex codes for all the installed languages are now migrated using CMT

35039274

3-31861452961

POL-12093

Additional Logging for failing OHI Connector tasks

Description:

The OHI Connector makes use of the task processing framework. When a task fails, it gets into an errored state and the functionality stops working. Failing tasks are not indicated in the log files.

Resolution:

Added error logging for the OHI Connector, in such a way that if a task fails, it will show up in the Application logs. Besides that, the documentation is extended with information on the task processing framework for the OHI Connector.

35340438

3-32862871471

POL-12722

Application doesn’t start if there are compilation error in the Dynamic Logic

Description:

The application startup failed when there were compilation issues with DYLO. The system throws the error which weren’t handled.

Resolution:

Handled the DYLO compilation error during the application startup. The application will start logging warning if there are compilation issue with DYLO.

35281690

POL-12611

Dynamic record as tab list is not showing flexcode data

Description:

Flexcodes configured in the tab list/tab table configurations does not show value.

Resolution:

Flexcodes configured in the tab list/tab table configurations shows the value.

35297232

3-32774965581

POL-12655

Process policy activity remains in InProcess status if java.lang.verifyerror occurs when executing dynamic logic

Description:

During Policy processing dynamic Logic is executed, as part of the Policy Process steps. When a mistake in the dynamic logic is encountered, the PROCESS_POLICY activity should fail in TE (Technical Error) status and the policy should be reverted to Edit status. But, in case a specific mistake is encountered while executing the dynamic logic (for example a java.lang.VerifyError), the PROCESS_POLICY activity does not fail and policy remains InProcess status.

Resolution:

If any dynamic logic error occurs while processing policy, now PROCESS_POLICY activity fails with status TE and the respective policy is reverted to Edit status.

35178157

3-32094585611

POL-12578

Output definition activity is failing with technical error

Description:

Generate Output activity when triggered with multiple approved versions of the policy, created child activities for all the approved versions. This led to optimistic locking during the execution of the child activities.

Resolution:

Generate Output activity now creates child activities for only the last approved version of the policy when there exists multiple approved versions. The optimistic locking is no longer seen.

Issues that were backported in previous Release / Patch

No backports.