Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.21.3.0.10
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 3.21.3.0.10.
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
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
34095629 |
3-29113598351 |
NXT-24598 |
BP |
Reduce the number of database calls to fetch user details in claimstransactionout integration point |
Description: |
Reduce the number of database calls to fetch user details in claimstransactionout integration point to improve performance . |
|||
Resolution: |
User details are now cached in business process cache . So ,the number of database calls are reduced now . |
|||
34619814 |
3-30674988421 |
NXT-25437 |
BP |
Performance degradation due to multiple xstream object creation |
Description: |
During claim/reservation processing, multiple XStream object are getting created during XML marshalling/unmarshalling. Such object creation involves loading of multiple classes internally which puts pressure on class loader which ultimately leads to slowness. |
|||
Resolution: |
Reused same XStream object across instead of creating multiple instances |
|||
34648915 |
3-30676382761 |
NXT-25487 |
BP |
Descriptor not shown in the list of values after making changes in flex code field |
Description: |
Descriptor not shown in the list of values after making changes in flex code field usages. |
|||
Resolution: |
Descriptor is now shown in the list of values. 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. |