Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.20.3.0.2
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.20.3.0.2.
Enhancements
ID | Summary | Description | Included in Patch |
---|---|---|---|
OIG-1434 |
Dynamic Logic Framework should allow to use package statement in the logic |
Currently our dynamic logic framework, assumes all scripts to be written in a default package ohi.dynamiclogic. This is done to apply the security restrictions and to allow for logging only in scripts defined in the aforementioned package. This causes problems with reusability, as every logic that requires to use the reusable code, needs to append ohi.dynamiclogic before importing it. This makes it difficult to manage and tests these groovy logic in isolation. On top of that, dynamic logic framework does not play well, if the package statement is explicitly included as ohi.dynamiclogic, as it appends another ohi.dynamiclogic in front of it. With this enhancement, it should be possible to declare packages in the script and the framework should work with the package defined. It is however important, that the packages defined should start with ohi.dynamiclogic, else security restrictions will be enforced. |
|
POL-6797 |
Dynamic Logic Framework should allow for reusable groovy classes to be created and used |
With this enhancement, dynamic logic framework allows for coding reusable classes to be reused as structures in other groovy scripts. This enhancement also introduces a new signature name for coding such reusable classes/scripts. The name of the signature is REUSABLE CODE and does not have any specific bindings. |
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
32018001 |
POL-6469 |
BP |
All tab data is getting cleared off on invalid data |
|
Description: |
On entering one/more rows of data with an invalid entry all tab data is cleared off instead of showing error and highlighting the invalid feel as expected. |
|||
Resolution: |
Now even on adding multiple rows in a given tab page, the field with error is highlighted and error is shown without the tabs being removed. |
|||
32029520 |
POL-6482 |
BP |
Remove option on dynamic record should delete the latest created dynamic record |
|
Description: |
Remove option on dynamic record is not deleting the first row instead of the newly created dynamic record in group client page. |
|||
Resolution: |
Now the dynamic record on the Group Client page which was created last is removed instead the first one on selection of remove option. |
|||
32043259 |
POL-6497 |
BP |
Not able to save data for dynamic records if it have mandatory fields. |
|
Description: |
User is not able to save the page after filling the mandatory record, when an empty row is added on tab out of the multi-value dynamic records. |
|||
Resolution: |
Now user is able to save the page successfully after filling the mandatory record when an empty row is added on tab out of the Multivalue dynamic records. |
|||
32113625 |
3-24068646251 |
POL-6637 |
BP |
Business validation error not handled correctly in UI leading to unexpected exception |
Description: |
When business validation added to the corresponding UI data row, exception throws and it was not handled in UI. So it navigates to the standard error page. |
|||
Resolution: |
Handled the error where save logic is written. Now it will be shown in the corresponding page as the expected error. Message 'The server is unable to respond' does not show anymore when saving in the application. |
|||
32142921 |
3-24377974061 |
POL-6724 |
BP |
Group Account "CALCULATE_PRODUCE_INVOICE" activity , should contain links to Data file in the activity notification. |
Description: |
Group Account "CALCULATE_PRODUCE_INVOICE" activity , do not have the links for data file in activity notification. |
|||
Resolution: |
Data file links are now available in "Run Calculation and Produce Invoice for a Group Account" activity notification when the activity is completed. |
|||
32150219 |
3-24500949741 |
POL-6744 |
BP |
Exception occurred when user selects value to the column level multivalue flex code. |
Description: |
When the user selects a value from the LOV for a multivalued flex code column, null pointer exception was thrown and error page was displayed. |
|||
Resolution: |
A value can now be selected from the LOV for a multivalued flex code column. |
|||
32164935 |
3-24491372481 |
POL-6767 |
BP |
CALCULATE_PRODUCE_INVOICE activity completes successfully, but the notification received on premium/commission end point has status as "Failure" |
Description: |
Even though the "Run Calculation and Produce Invoice for a Group Account" activity completes successfully, the notification received on premium/commission end point has "Failure" status. |
|||
Resolution: |
In the following use cases, the status in the data file notification now correctly reflects the status of the activity:
With this bug fix, the order of the links in the data file notification has changed. |
|||
32170121 |
3-24498375181 |
POL-6774 |
BP |
THE CHILD ACTIVITY GENERATE_FIN_MSG_XML OF "RUN CALCULATION AND PRODUCE INVOICE FOR A GROUP ACCOUNT" ACTIVITY SHOWS BOTH PREMIUM AND COMMISSION DATA FILE SET CODES IN UI. |
Description: |
In "Run Calculation and Produce Invoice for a Group Account" activity, two different financial transaction sets are created (one for premium and one for commission). So, two different child activities GENERATE_FIN_MSG_XML are created. The child activity for premium adds an activity message (ACT-FL-DAFI-001) with the code the data file set containing financial messages of premium and the child activity for commission adds an activity message (ACT-FL-DAFI-001) with the code the data file set containing financial messages of commission. However, in the ADF UI, both the child activities (GENERATE_FIN_MSG_XML) show both the messages. |
|||
Resolution: |
now the generate financial message activity (premium) will show message related to data file for premium and generate financial message activity (commission) will show message related to data file for commission. |
|||
32250908 |
POL-6933 |
BP |
Group Hierarchy tree view is not rendered, when we have group client and group account having similar IDs |
|
Description: |
There is chance of having group clients and group accounts with similar IDs in the application, as ID is unique only to that particular entity. Since we were using ID as the keyAttribute for nodes in tree view, it will fail to render if there is group clients and group accounts with similar IDs. |
|||
Resolution: |
User will now be able to view and access group hierarchy tree view in all possible scenarios. |
|||
32257783 |
POL-6951 |
BP |
GENERATE_FIN_MSG_FLAT_FILE activity doesn’t send data file notification |
|
Description: |
After the bug 32164979 is fixed, the GENERATE_FIN_MSG_FLAT_FILE activity does not send data file notification any more. |
|||
Resolution: |
The activity "Generate Financial Message (Flat File)" now correctly sends data file notification. |
|||
32014536 |
POL-6464 |
AU: Run calculation and produce invoice for a group account - process registration is executed for all policies |
||
Description: |
This activity selects all applicable policies instead of processing the policies belonging to the group account this activity is started for. |
|||
Resolution: |
The activity Run Calculation and Produce Invoice for a Group Account (AU) was picking up new, applicable, registrations of all policies: this has now been changed to: 1) only pick up registrations that belong policies to that group account (i.e. do not end before the look back date parameter). 2) uncorrelated new registrations are not picked up any more. This will only be verified when the process registrations activity is run. Also, in that activity, only uncorrelated new registrations of type PAYMENT are checked and new registrations without correlation id will be included. |
|||
32019680 |
POL-6474 |
Formatted name is not showing up in list of values for persons LOV |
||
Description: |
Persons lov is not showing up the formatted name code in policies page. |
|||
Resolution: |
Now user can configure and able to access the persons lov along with formatted name in application. |