Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.14
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.14.
| Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 4.25.1.x is only compatible with other Oracle Health Insurance applications release version 4.25.1.x unless explicitly stated otherwise. |
| As per the Service Description, you are obligated to request a service upgrade within 90 days of this release being generally available (GA). In line with the Oracle Cloud Services Pillar document, Section 4.2.2 End of Life, this release will be EOL in 12 months. |
Web Services
| Ref | Action | Description |
|---|---|---|
POL-18278 |
Modified |
policies/quote/{calculationInputDate} Validation rules with 'Exclude from Validation?' true are excluded during execution of validation rules. |
POL-18278 |
Modified |
policies/{policyId}/examplecalculation/{calculationInputDate} Validation rules with 'Exclude from Validation?' true are excluded during execution of validation rules. |
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
38691204 |
3-42957456931 |
POL-18083 |
Flex Code Base Views are both removed and updated at the same time |
Description: |
During Base View Generation, the generation of Flex Code Base View is unstable: (1) Concurrent update/remove operations occasionally targeted the same view, raising the Oracle error 'table or view does not exist'. This happened intermittently. (2) The generator skipped creating some Flex Code Base Views whenever the Flex Code System code contained lowercase characters. |
||
Resolution: |
The update/removal operations are serialized to prevent errors like 'table or view does not exist', also, Flex Code Base Views are generated for Flex Code Systems with a code containing lowercase characters. |
||
38872430 |
4-0001814443 |
POL-18271 |
Boilerplate codes visible instead of the values on parameter values of a policy enrollment product |
Description: |
In Parameters tab, Percentage, Number and Service days boiler plate texts are displayed instead of actual values when we open it the first time |
||
Resolution: |
Translations are applied properly now and actual values are displayed instead of boilerplate texts |
||
38973182 |
POL-18359 |
Query API returns incorrect totalResults when groupBy is used |
|
Description: |
When the Query API is invoked with the |
||
Resolution: |
The Query API now returns the correct |
||
38856807 |
4-0001793793 |
POL-18254 |
Missing secrets for OAuth clients while ohistore is used as keystore |
Description: |
Sometime OAuth clients shows clientSecretRegistered as false even through secret is already set in the database. |
||
Resolution: |
OAuth client credential keys are now correctly fetched. |
||
39107446 |
POL-18481 |
Implicit deletion of Group Client Events creates a Policy Event |
|
Description: |
When deleting a Group Client, all related Group Client Events are also implicitly deleted (cascade delete). It is possible to configure a Change Event Rule on deletion of a Group Client Event, in which case a Policy Event is created with a reference to the corresponding Group Client. However, if a Group Client Event is deleted as a consequence of deleting the Group Client, the Group Client reference is no longer available. This leads to an error when transforming the resulting Policy Event into an Aggregate Event. |
||
Resolution: |
When a Group Client Event is removed implicitly due to cascade deletion of its associated Group Client, no Policy Event is created to represent the deletion of that Group Client Event. |
||
38877862 |
4-0001712606 |
POL-18278 |
Validation rules marked as "exclude from validation" are executed during example calculation and quote IP. |
Description: |
When "Exclude from Validation?" is set to true on a policy validation rule, this rule should not be executed during Example Calculation and Quote IP. |
||
Resolution: |
Validation rules with "Exclude from Validation?" true are excluded during execution of validation rules in Example calculation and Quote IP. Next to that, for Example calculation and Quote IP: before calculation of premium, the data changed in the validation rules are temporarily persisted to make sure that premium calculation picks up these changes. |
||
39014250 |
POL-18395 |
After the ADB patch, the extract activity failed with |
|
Description: |
The extract activity failed with ORA-00028 (your session has been killed) following the ADB patch. During the patching process, DBMS_CLOUD was temporarily invalidated. Since OHI_OBJECTSTORAGE_PKG depends on DBMS_CLOUD, some existing application/JDBC sessions continued to use a cached (stale) package state. As a result, the scheduled exchanges/extract activities referenced the stale package state, and the affected sessions were terminated, causing the activity failures. |
||
Resolution: |
ORA-00028 is now handled by the application, and the affected activities are automatically re-tried when this error is encountered. |
||
38978223 |
POL-18370 |
Error message is shown in GrountAccountProduct while saving |
|
Description: |
Since it is not possible to Add GrountAccountProduct while creating Group Account, disable 'Add Group Account Product' until the Group Account is saved and enable only in View Edit page. |
||
Resolution: |
Custom 'Add GrountAccountProduct' Button is changed to 'Add' button and 'sequence' column is added to table |
||
39084103 |
4-0002265614 |
POL-18444 |
When a lot of Quote requests are executed (a high load) with same new (dummy) person the performance slows down |
Description: |
When the volume of Quote IP requests is high, the database experienced significant ITL wait events. Analysis shows that ~95% of these waits occurred on the index REL_RELATION_IDX1, which is based on the NAME column of persons. The issue is caused by multiple Quote IP requests inserting rows with identical or very similar relation names, causing concurrent inserts to target the same index blocks. This leads to index block contention and ITL allocation waits, effectively creating a hotspot in the index. |
||
Resolution: |
For new persons in Quote request, the name of those persons is randomized to avoid contention in indexes on name. The response will still show the original person names in the request, so no functional changes. |
||
38973502 |
4-0002159777 |
POL-18360 |
The Person API does not accept non Latin or accented characters in the local part or user name of the email address. |
Description: |
The Person API does not accept non Latin or accented characters in the local part or user name of the email address. |
||
Resolution: |
The Person API now accepts non Latin or accented characters in the local part or user name of the email address. |
||
38226843 |
3-40724895331 |
POL-17508 |
Tracking/Tracing of requests should not be sent to external systems |
Description: |
Tracing headers (such as B3 headers) are being sent to external systems. This leads to a 500 error response. However, when the spanId header is removed, the request goes through successfully with a 201 response |
||
Resolution: |
B3 Tracing headers will be added when the host of the request and the application are identical. |
||