Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.1.0.4
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.1.0.4.
Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 3.22.1.x is only compatible with other Oracle Health Insurance applications release version 3.22.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 | Description | Included in Patch |
---|---|---|---|
POL-11121 |
Prevent leading or trailing spaces in user name |
This enhancement prevents the use of leading or trailing spaces in the user’s login name. The provisioning integration point raises a fatal message when leading or trailing spaces are used in the login name. The enhancement supports a conversion script for existing login names with trailing spaces. |
|
POL-11288 |
Improvements in calculate premium activity |
The number of queries on premium schedules, schedule definitions and insurable persons objects are reduced. The performance of querying reference sheet lines from "Reusable Code" dynamic logic (using SearchBuilder) is optimized by caching the query results (controlled by a system property). |
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 ofohi_install.cfg.template
and name itohi_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:
-
Open a command window and browse to
<OHI_ROOT>/util/install
. -
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
Additional Upgrade Steps for Installation
The following phases are defined:
|
Stage: pre-upgrade
1) Action: Run the following SQL update statement, to replace leading and trailing spaces in login_name with 'X' for all users with trailing spaces.
update ohi_users -- replace leading spaces
set login_name = lpad(ltrim(login_name), length(login_name), 'X')
, last_updated_date = current_timestamp
, last_updated_by = -1
, object_version_number = object_version_number + 1
where login_name != ltrim(login_name);
update ohi_users -- replace trailing spaces
set login_name = rpad(rtrim(login_name), length(login_name), 'X')
, last_updated_date = current_timestamp
, last_updated_by = -1
, object_version_number = object_version_number + 1
where login_name != rtrim(login_name);
commit;
If you run into the "ORA-00001: unique constraint violated" error, this means that there is already a user with the same login_name after replacing spaces with X. In this case, identify the offending login_names with the following query:
select u1.login_name
from ohi_users u1, ohi_users u2
where u1.login_name != rpad(rtrim(u1.login_name), length(u1.login_name), 'X') -- u1: users whose login_name are renamed
and u2.login_name = rpad(rtrim(u1.login_name), length(u1.login_name), 'X'); -- u2: users whose login name equals the renamed name
And similarly where rpad(rtrim(…
has been replaced with lpad(ltrim(…
for errors in login_names with leading spaces.
Manually replace these login_names with extra X’s to avoid the unique key violation, e.g. if user "login_with_space "
was found with the previous query, copy it (including the space) and update it with the following statement:
update ohi_users
set login_name = 'login_with_spaceXX' -- add an extra X
, last_updated_date = current_timestamp
, last_updated_by = -1
, object_version_number = object_version_number + 1
where login_name = 'login_with_space ' -- the offending login_name
commit;
After this, run the first update statement again.
Dynamic Logic
Ref | Action | Subject | Description |
---|---|---|---|
POL-11288 |
Modified |
All |
The dynamic logic will be re-compiled when the application starts up the first time after upgrading to this release. So, application startup could take more time than usual. This is an one time operation, so the dynamic logic are not re-compiled in the subsequent startup. |
UI Changes
Ref | Action | Subject | Description |
---|---|---|---|
POL-11303 |
Modified |
Tables page |
The description of Tables configuration page is not getting saved, Spinner keeps on spinning(Processing request). And resolved by updating floorplan by removing edit action |
POL-11387 |
Modified |
Deeplink Dialogue |
Changes made to pass proper request url in POST Search after clicking Save in Deeplink Dialog |
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
34180502 |
3-30460115351 |
POL-10617 |
BP |
Policy Process Flows Policy Rule Step Records are showing blank for any rule type |
Description: |
Policy Rule Step Records are showing blank for any rule type in Policy Process Flows Page. On trying to add a validation rule under Policy Rule Step in the Policy Process Flow, no Validation Rule List is found. A blank Validation Rule is added on the Policy Process Flow page under Policy Rule Step section on Attach |
|||
Resolution: |
Validation Rule List appears in the Policy Rule Step page so that the user can choose one they want to add. |
|||
34537820 |
3-30280303703 |
POL-11241 |
BP |
Policies are not getting approved because overlapping Person Covered Services are generated |
Description: |
Some policies are not getting into approved status during policy processing because of time validity errors during Person Covered Service generation. This happened when a person is enrolled on a specific product on multiple policies at the same time. The following two scenarios caused the GEN-TMVL-011 error to be thrown: - When multiple enrollments have the same start date and product, but a different end date - When multiple enrollments have the same product but different parameter values and the reference date is taken somewhere in the middle of the enrolments instead of the beginning of all the enrollments |
|||
Resolution: |
The GEN-TMVL-011 error will not be thrown in the described scenarios. |
|||
34568840 |
POL-11303 |
BP |
User is unable to edit the description in the "tables" page |
|
Description: |
The description of Tables configuration page is not getting saved, Spinner keeps on spinning(Processing request) and Getting "405 Method Not Allowed" from backend. |
|||
Resolution: |
Removing Edit action button from Tables page from floorplan |
|||
34568549 |
POL-11299 |
BP |
In Tab Table, if multiple records are created by enabling deeplink on any column, save button freezes |
|
Description: |
In tab table, enabling deeplink and adding multiple records will not let the user to save the page and no error is thrown either. |
|||
Resolution: |
The user is allowed to save tab table records with deeplink enabled in the properties, even when multiple rows added at a time |
|||
34592424 |
3-29584669481 |
POL-11336 |
BP |
Add more logging in the target and in the source of data replication. |
Description: |
Add more logging in the target and in the source of the data replication. |
|||
Resolution: |
Added logging in the source and in the target of the data replication. |
|||
34612152 |
POL-11387 |
BP |
Deeplinks are not working as expected |
|
Description: |
While adding a new person getting error: GEN-ORA-01400: "LANG_ID" column is mandatory for table "REL_RELATIONS". However, a person is created and able to search it on Persons page |
|||
Resolution: |
Person is being created without any error in the deeplink dialogue. |
|||
34518206 |
3-30037365971 |
POL-11193 |
BP |
Adf only shows the last group account available product |
Description: |
System was displaying only the latest Available Product in Availability tab of Group Accounts. |
|||
Resolution: |
Availability tab of Group Accounts is showing all the related Group Account Available Products as expected. |
|||
34618912 |
3-28742140171 |
POL-11398 |
BP |
Adding descriptor field is not possible when values exist for a FlexCodeDefinition. |
Description: |
Adding descriptor field is not possible when values exist for a FlexCodeDefinition definition. |
|||
Resolution: |
If the values exist for a FlexCodeDefinition and if no FieldUsage is a descriptor, a non-descriptor FieldUsage is allowed to be marked as descriptor. But if values exist and there is FieldUsage marked as descriptor, then it cannot be unmarked as a descriptor. |