Release Notes for Oracle Insurance Gateway Release 3.21.3.0.0

This document contains the release notes for Oracle Insurance Gateway Release 3.21.3.0.0.

Version compatibility: Oracle Insurance Gateway Release 3.21.3.x is only compatible with other Oracle Health Insurance applications release version 3.21.3.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

NXT-21641

JET UI Feature - Ability to specifiy default values for reference fields

With this enhancement, support is added to specify a default value for referenced fields.

NXT-21834

Introduce retry mechanism for dynamic logic import in configuration migration tool

Dynamic logic can refer to another dynamic logic and if the dynamic logic are not imported in the correct order using configuration migration tool, the dynamic logic import fails. This enhancement introduces automatic retry mechanism of dynamic logic.

NXT-21907

Upgrade to groovy 3

As of major release 3.21.3.0.0 OHI applications (are certified to) work with Groovy 3

NXT-22775

JET:Refactor Sort component

There are client side sorting issues like default sort not working at tab level for certain fields and the sort criteria query has issues around 'nulls first' clause. These improvements for sort component are done in this enhancement

NXT-22779

Reduced Page Loading Time

Generic boilerplates are queried & cached in local storage during login and page specific ones are queried and cached when the page is accessed first time. The timestamp of the query is stored in local storage based on local browser timezone

The lastUpdatedDate of the boilerplate returned from the DB server may be on a different timezone.

So the boilerplate query which is based on comparison of lastUpdatedDate and localStorage timestamp may return wrong results

NXT-23323

Data Exchange/CMT Export/Import notifications should be in common notification structure

Introduced common notification structure which has fixed number of attributes and can be sent in any format (JSON, XML etc.) Introduced new property "ohi.datasetoperations.notification.common.structure" to support both, old as well as new notification structure. It accepts boolean value as "true" or "false". "true" indicates notification should be sent in new notification structure. If property has a value as "false" or has not been set, old notification structure is used always.

OIG-1447

Generate Audit Trail in CMT

This enhancement enables creation of an audit log of what changes happened in a CMT import. This helps the customers to ascertain, if the changes are inline with what was expected, and to also determine the affected usecases for testing. It is switched off by default.

OIG-2040

Specific to Australia: added support for handling on-line hospital claims

See the Australian Country Pack documentation for details

3.21.2.0.4

POL-5637

User Interface Embedded Links

It is now possible to configure external links at page level and at the property level. In addition it is now possible to create configure deep links on the referenced property. Through this deep link feature, a referenced property can be viewed, created, or edited from the page where it is referenced. For example, using the deep link feature create/view and edit member page can be accessed from the policy page.

POL-5895

Bookmarks

It is now possible to bookmark a page within the JET application. Bookmarks are accessible in the primary navigation menu.

POL-7089

Improved Application Menu

The application menu is now accessible from the hamburger icon next to the application name. The menu can now be pinned to the left-hand side of the screen for the entire duration of the user session. In addition the application menu is now also made searchable. A menu item can be searched by using the menu name or the function code.

POL-8031

Third column in the region component

It is now possible to add a third column within the regions component by configuring set3. This support is added to view and edit - recursive template and in the overflow area within the table component

3.21.2.0.2

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

  1. Perform any pre-upgrade steps.

  2. Stop all the managed nodes running the .existing version of the application.

  3. Perform any pre-undeploy steps.

  4. Undeploy the existing version of the application.

  5. Back up the database.

  6. Perform any post-undeploy steps.

  7. Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.

  8. Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.

  9. Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.

  10. Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)

  11. 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 .

  12. Make the required changes to the ohi properties file

  13. Perform any post-upgrade steps

  14. Start WebLogic application server

  15. Deploy the Application

  16. Perform any post-deploy steps

Additional Upgrade Steps for Installation

The following phases are defined:

  1. pre-upgrade: Application is still running

  2. pre-undeploy: Application is stopped, but not undeployed.

  3. post-undeploy: Application is undeployed. Database is backed up

  4. post-upgrade: Released upgrade script has run.

  5. post-deploy: New application is deployed and is up and running.

Stage: post-undeploy

Please execute the SQL statement with the user: OHI_OIG_OWNER. This SQL is to fix the known issue of custom floorplans getting overridden by OHI floorplans with same ID.

begin
    execute immediate 'alter table ohi_floor_plans_tl disable constraint ohi_floor_plan_tl_fk1';
    for rec in (
        select
            id
        from
            ohi_floor_plans_b
        where
            id in ( 15121 )
            and ind_system = 'N'
    ) loop
        update ohi_floor_plans_b
        set
            id = ohi_floor_plan_s1.nextval
        where
            id = rec.id;

        update ohi_floor_plans_tl
        set
            base_table_id = ohi_floor_plan_s1.currval
        where
            base_table_id = rec.id;

    end loop;

    execute immediate 'alter table ohi_floor_plans_tl enable constraint ohi_floor_plan_tl_fk1';
    commit;
end;
/

Configuration Properties

Ref Action Subject Description

NXT-21834

Added

ohi.cm.dynamiclogic.import.maxRetryCount

Dynamic logic can refer to another dynamic logic and if the dynamic logic are not imported in the correct order, the compilation will fail. If it happens, CMT process retries the failed dynamiclogic. This property determines how many times the dynamic logic import is retried before marking it as 'errored' Suggested is a value between 1 and 9. Default value is 3

NXT-21834

Added

ohi.cm.dynamiclogic.retry.import.batch.size

Defines the batch size that should be read for the failure log table at a time. Default value is 100

NXT-23323

Added

ohi.datasetoperations.notification.common.structure

Can be set as "true" or "false". "true" indicates notification should be sent in new structure otherwise in old structure

Web Services

Ref Action Subject Description

NXT-22779

Modified

User Information Integration Point

New attribute lastLoginTimestamp is added

OIG-1447

Added

audittraildetails API

New API

OIG-1447

Added

audittrails API

New API

OIG-1447

Modified

datasetprocesses API

The link to the change log is made available through the response on a GET operation

OIG-1447

Modified

Data Set Operations Integration Point

New attribute enableAuditTrail is added to "Import From File" and "Import From Environment" operations

POL-5895

Added

bookmarks API

Added new resource for bookmarks

POL-5895

Modified

userpreferences API

Added bookmarks as child list

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

Ref Action Subject Description

NXT-21641

Modified

All JET pages

LOV (reference field) now supports default values

POL-5637

Added

Page level links

Added ability to configure page level external links.

POL-5637

Added

Deep links on referenced property

Added ability to support deep links on referenced properties. Through this deep link feature, a referenced property can be viewed, created, or edited from the page where it is referenced.

POL-5637

Added

Property level links

Added ability to configure property level external links.

POL-5637

Removed

HTTP Links page

HTTP Links page is removed from JET applications.

POL-5895

Added

bookmarks icon

Added bookmarks icon in the header bar on clicking of which a page can be bookmarked and its possible to set alias and remarks and edit and remove them.

POL-5895

Added

bookmarks

Added bookmarks in navigation bar. Under bookmarks, alias and remarks are displayed and clicking on alias navigates to the corresponding bookmarked page.

POL-7089

Added

JET pages

Added side navigation drawer and searchable menu in application header.

POL-8031

Added

All JET pages

User can now customize floorplan to get third column.

Deprecated items (to be removed in future release)

Ref Action Subject Description

NXT-23323

Modified

Data Set Operations Integration Point

From this release, the notification can be sent in the new or common format. If property "ohi.datasetoperations.notification.common.structure" is not set or set to false, old format is always used. If property "ohi.datasetoperations.notification.common.structure" is set to true, new or common format is used. This property will be removed in a future release and from that release onwards, the data set operations notification will be sent only in the new or common format.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal BP Summary

32950841

OIG-1914

Add basic access grants needed for JET UI user login with setup access role.

Description:

Add basic access grants needed for JET UI user login with setup access role.

Resolution:

The user with the setup access role can login to the JET UI application without any issue and is able to access the access roles page successfully.

32921621

3-25847761621

OIG-2003

OIG exchange fails with org.eclipse.persistence.exceptions.databaseexception

Description:

OIG Exchange failed with org.eclipse.persistence.exceptions.databaseexception when multiple activity steps were present in an activity step and the first activity step completes almost instantly.

Resolution:

OIG Exchange will complete all the steps even if multiple activity steps are present and the first activity step completes almost instantly.

32933892

OIG-2011

Extension to dynamic logic functionality - inactive extended dylo unit is getting invoked.

Description:

An extended dynamic logic with active as off, was still extending the base dynamic logic.

Resolution:

An extended dynamic logic with active as off, will no longer extend the base dynamic logic.

32987139

OIG-2051

Sometimes JET UI pages with large number of fields might cause a bad request error due to a large request header.

Description:

Sometimes JET UI pages with large number of fields might cause a bad request error due to a large request header like - "Request Header Or Cookie Too Large" thereby not rendering the page. In such a case the floorplan might need to be modified to reduce the number of fields and thereby reducing the accept header size. There is an enhancement planned in 3.21.3.0.0 to reduce the accept header size.

Resolution:

Aliases have been applied to reference fields and child lists. In addition, all dynamic fields and child lists are expanded and not individually included in the fields parameter, thereby reducing the overall accept header length.

33025147

3-25847761621

OIG-2067

Commit fail error after receiving notification

Description:

Sometimes a commit fail exception is raised when multiple activity steps are present.

Resolution:

The rare commit fail exception won’t be raised when multiple activity steps are present.

33125473

3-26456481851

OIG-2104

Exchange REST client operations sometimes failed with a JAVAX.CRYPTO.BADPADDINGEXCEPTION.

Description:

Sometimes the exchange REST client operations failed with JAVAX.CRYPTO.BADPADDINGEXCEPTION. This is caused by a bug in the JVM (https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8191002) that is only fixed in Java 9 onwards. WebLogic is certified to work with Java 8 in which this is not fixed.

Resolution:

The system no longer calls the Java method that suffers from the bug.

33164399

OIG-2124

Add caching for static files

Description:

Stale copy of the static files were being served by the application

Resolution:

Introduced ETag in the response headers to application’s static resources. This will ensure that the fresh copy of the resource is fetched whenever the resource is changed.

If you are upgrading from a version lower than 3.21.2.0.3, make sure to clear the browser cache before accessing the application. If you are upgrading from 3.21.2.0.3 or above, clearing of browser cache is not needed.

33208065

OIG-2144

Change AS2805 response if Health Fund system is not available

Description:

If OIG to OHI communication is not happening due to system issues or due to error(e.g. use of wrong credentials for the destination), the AS2805_A and AS2805_B response code was set as 00 Approved.

Resolution:

If OIG to OHI communication is not happening, due to system issues or due to error, the AS2805_A and AS2805_B response code will be 91 Health Fund Down and 93 System problem respectively.

33247456

3-26683349041

OIG-2152

Data collection custom and subflow type of dynamic logics are not included cmt data set export

Description:

Data collection custom and subflow type of dynamic logic were not included in a selective CMT export.

Resolution:

Data collection custom and subflow type of dynamic logic will now be included in selective CMT export.

33248137

OIG-2154

NullPointerException should be replaced with an user friendly error message in ConfigMigrationItemReader

Description:

Nullpointer received when an entity name in the import file doesn’t exist in the application

Resolution:

GEN-MIGR-016 will be shown with the missing entity name in the application

Issues that were backported in previous Release / Patch

BugDB Internal Summary Backport BugDB SR

32950841

OIG-1914

Add basic access grants needed for JET UI user login with setup access role.

3.21.2.0.2

33012858

32921621

OIG-2003

OIG exchange fails with org.eclipse.persistence.exceptions.databaseexception

3.21.2.0.2

33025048

3-25847761621

33025147

OIG-2067

Commit fail error after receiving notification

3.21.2.0.2

33025156

3-25847761621

33125473

OIG-2104

Exchange REST client operations sometimes failed with a JAVAX.CRYPTO.BADPADDINGEXCEPTION.

3.21.2.0.3

33125485

33247456

OIG-2152

Data collection custom and subflow type of dynamic logics are not included cmt data set export

3.21.2.0.5

33252550

3-26683349041

Known Issues

BugDB SR Internal Summary

31523984

OIG-1284

Search Exchanges: pagination is not working properly

Description:

Search Exchanges: pagination is not working properly.

  1. When filtered the search results based on certain conditions.

  2. When changed the search results count from the default(10 rows), it is displaying as the text area.

  3. After applying the filter conditions, pagination is not displayed.

33427486

OIG-2233

Unsaved Changes Popup Handler Inconsistency

Description:

Unsaved Changes Popup Handler Inconsistency is coming across custom pages.

33432110

OIG-2234

Change logs generated by importing different updated subtypes of an entity in the same payload are incomplete

Description:

When a CMT import with audit trail enabled is done and below conditions are true , then the generated audit trail change log is incomplete

  1. There are different subtypes exists for an entity. For example - IntegrationSteps can have TransformStep and ActivityStep.

  2. They are mapped to the same table.

  3. In the CMT import payload, there are updates on more than one subtype for the same entity. For example - TransformStep is removed and ActivityStep is added.