Release Notes for Oracle Health Insurance Product Definition Patch 4.25.1.0.1
This document contains the release notes for Oracle Health Insurance Product Definition Patch 4.25.1.0.1.
| Version compatibility: Oracle Health Insurance Product Definition 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. |
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
37894793 |
3-40594714131 |
PRD-4988 |
"Not Authorized Error" when user attempts to modify/add regime with Products JET access |
Description: |
System throws "Not Authorized Error" when user attempts to modify/add regime with "PR0014, PR0014 products JET" access |
||
Resolution: |
Error when trying to modify/add regime for user with products JET access is resolved after adding access mapping for coverageregimeparameters API to PR0014 |
||
37976012 |
PRD-4997 |
Sort by is not working in some of oj-table pages and change from asc/desc is not showing sorted values properly in all pages |
|
Description: |
The Sort By functionality is not working consistently across some oj-table pages. Changing the sort order between ascending and descending does not update the displayed data correctly. |
||
Resolution: |
Sort By is now working as expected and displaying data correctly based on the selected sort criteria across all oj-table pages |
||
38178935 |
PRD-5031 |
Performance degradation in activity processing due to the overhead caused by the heartbeat query |
|
Description: |
The cleanup_act_status activity monitoring heart-beat query, which performs a SELECT on the ACT_ACTIVITIES table to fetch records with status 'IP', is experiencing performance issues. The query is currently executing a full table scan as the status field is not indexed, resulting in increased execution time. |
||
Resolution: |
The query was optimized by using the VIRTUAL_UNPROCESSED_STATUS column, which is indexed and offers better performance. |
||
37756964 |
PRD-4859 |
Dynamic field on generated benefit specifications does not get cleared. |
|
Description: |
We have created a Dynamic Field (Flex Code) with the same name in both the Service Definition and Benefit Specification entities. When a value is added to this Dynamic Field in the Service Definition, it correctly appears in the generated Benefit Specification during product generation or review. However, when the value is cleared from the Service Definition, it does not get removed from the generated Benefit Specification in subsequent product generations or reviews. |
||
Resolution: |
The implementation has been updated so that when the dynamic field (flex code) value is cleared from the service definition, it is also removed from the generated benefit specification during subsequent product generations or reviews. |
||