Release Notes for Oracle Health Insurance Product Definition Patch 4.24.1.0.1
This document contains the release notes for Oracle Health Insurance Product Definition Patch 4.24.1.0.1.
| Version compatibility: Oracle Health Insurance Product Definition Release 4.24.1.x is only compatible with other Oracle Health Insurance applications release version 4.24.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. |
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.templateand name itohi_install.cfg. -
Edit
ohi_install.cfgto 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
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
36989267 |
PRD-4580 |
SaaS: Default service options and services are not getting added while creating a new product. |
|
Description: |
When 'productIncludeDefaultJET' has a value set to true, this should allow the users to add default services and service options to the Product. Currently, this is not happening in SAAS environments. |
||
Resolution: |
Changed logic to ensure that it accepts the header value case-insensitively and adds default service options and services to the product. |
||
36993408 |
PRD-4588 |
Products: "+Add" button missing in adjudication stop limit and adjudication continue limit in create mode |
|
Description: |
"+Add" button missing in adjudication stop limit and adjudication continue limit in create mode until check icon is selected |
||
Resolution: |
'+Add' button is now visible in create mode as well. |
||
36977454 |
PRD-4576 |
Remove Copy from Global activities details page |
|
Description: |
Copy action should not be shown for view only details pages |
||
Resolution: |
Copy action is removed from view only details pages |
||
37057752 |
PRD-4609 |
Products: Parameters are shown in product cost sharing even if it is present in mandate cost sharing(Amount) |
|
Description: |
It is possible to save value in product cost share for the same parameter and currency combination even if it is present in mandate cost share |
||
Resolution: |
Only valid parameters are shown in LOV in Product cost sharing section. |
||
37374738 |
PRD-4742 |
Boilerplates are shown in bookmarks dialog |
|
Description: |
Click on bookmark icon, verify the dialog. Bookmark is shown for alias and remark field |
||
Resolution: |
Boilerplates are not shown in bookmarks dialog |
||
37293741 |
PRD-4722 |
Service Definition : Unable to save a record when user removes non mandatory field(Specialties Usage and Specialties) from copied row |
|
Description: |
Go to Service Definition page. Copy a row with Specialties Usage and Specialties. Now remove the values from Specialties Usage and Specialties fields and save the record. Unable to save the record and mandatory error message should be displayed in UI |
||
Resolution: |
It is now possible to save a record when user removes non mandatory field(Specialties Usage and Specialties) from a copied row |
||
37480321 |
PRD-4783 |
Flex Code Group Details Page - End date is missing in the table |
|
Description: |
Navigate to object navigation: "Flex Code Group Details" of Flex Code group page. In the table, only 2 fields - Start Date and Flex Code is displayed, end date is missing |
||
Resolution: |
End date field is added to Flex Code Group Details Page |
||
37924705 |
PRD-4966 |
Unable to delete a product with product limit |
|
Description: |
When user tries to delete a product which has product limit in product service definition, there is an error. |
||
Resolution: |
A product with product limit can now be deleted without any business error |
||
37923356 |
PRD-4964 |
Global activity page does not load messages |
|
Description: |
In the ADF UI, it is possible to troubleshoot why an activity fails with technical errors. The dynamiclogic error on the child activity is shown. User does not see this in the JET UI, making troubleshooting difficult. |
||
Resolution: |
All the messages are getting displayed properly in the activity messages tab on Global Activities page. |
||
37248294 |
PRD-4683 |
Referencesheet Query API works erroneously in some cases |
|
Description: |
Referencesheet Query API did not return correct result set when a comparison operation like gte (greater than or equal to) or lte(less than or equal to) was used because the passed value was being interpreted as a string instead of a number |
||
Resolution: |
The query logic for gte (greater than or equal to) and lte(less than or equal to) operations is updated to return the correct the results in the referencesheetlines Query API |
||
38194088 |
3-41483288351 |
PRD-5038 |
While configuring a product, the maximum limit of parameter alias allowed is 200 |
Description: |
After adding 200 parameter alias for the limits (configured as accumulation options) in the product, when user tries to access cost sharing details, the page freezes and does not load once 201st parameter alias is added |
||
Resolution: |
The cost sharing tab loads all the parameter values successfully when more than 200 parameteraliases are configured for a product |
||