Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.20.3.0.4
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.20.3.0.4.
Enhancements
ID | Summary | Description | Included in Patch |
---|---|---|---|
OIG-1366 |
Dynamic Logic Hooks/Extensions |
Country packs involves delivering configuration. This configuration includes dynamic logic to process country specific usecases. These dynamic logic can be extended by customers to provide their specific changes/extensions. This enhancement allows to do that. This is enabled by introducing a new signature 'Extension' for all such extensions with a reference to the base dynamic logic that it is extending. At runtime, the application finds out all the extensions and invoked them. |
|
POL-6791 |
Scope on Surcharge on Premium Schedule Type |
Before this release, when a surcharge rule is set up to apply to the base premium (this is the SCHEDULE DEFINITION entity) then the percentage or function gets applied to the sum of the different premium schedules.This enhancement makes it possible for a more granular approach that enables the user to specify a premium schedule of type X, so that the surcharge rule only takes in premium from schedules of type X as its input. This enhancement is available via API. |
UI Changes
Ref | Action | Subject | Description |
---|---|---|---|
OIG-1366 |
Modified |
Dynamic Logic Page |
Added Base dynamic logic. This is done for both UI (ADF and Jet) where applicable. |
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
32251691 |
POL-6934 |
BP |
An error occurs when user tries to save the LOV value without selecting from the search results |
|
Description: |
The error occurs when user tries to save the LOV value without selecting from the search results. If the user doesn’t select any value, the value does not get saved. |
|||
Resolution: |
If the user wants to select a value from an LOV, then they must enter the complete value of the LOV and press Enter key. This will pick the first value from the search results of LOV. |
|||
32355762 |
3-24806255191 |
POL-7100 |
BP |
Percentage based adjustment is not applied to a base premium of zero |
Description: |
When the base premium is configured as zero and if two adjustments are configured - the first adjustment (with sequence 1) with amount and the second adjustment (with sequence 2) with percentage, then the second adjustment is not applied (on base premium + amount from the first adjustment). |
|||
Resolution: |
Percentage based adjustment is now correctly applied to a base premium of zero. |
|||
32453673 |
3-25013086391 |
POL-7281 |
BP |
NullPointerException when accessing new entity’s attributes in "Change Event Rule (Effective Date)" dynamic logic |
Description: |
When PATCH operation is used on policies API to add a new dynamic field and if a change event rule is configured that monitors for an update on the dynamic field, NullPointerException is thrown when accessing the new entities (like bind variable newPolicy) attributes (like code) in "Change Event Rule (Effective Date)" dynamic logic. |
|||
Resolution: |
It is now possible to add a new dynamic field/record using PATCH and have a reference to all attributes on the new entity (like newPolicy when applicable) in "Change Event Rule (Effective Date)" dynamic logic. |
|||
32463996 |
POL-7292 |
BP |
Getting exceptions while running SampleInvoice IP or Invoice IP if trace logging is enabled |
|
Description: |
NPE was thrown while running SampleInvoice IP or Invoice IP if trace logging is enabled for calculatePremium packages |
|||
Resolution: |
When trace is enabled for calculatepremium package(s), these exceptions no longer occur when premium is calculated (with calculate premium activity, example calculation etc.) |
|||
32465266 |
3-24868305941 |
POL-7298 |
BP |
APPLY_REGISTRATIONS activity and processandapplyregistrations operation doesn’t work properly during policy edit |
Description: |
When a new enrollment is added, a policy event with effective date as start date of policy enrollment product is not getting handled by apply reg activity and process and apply reg operation. After edit of the newly added policy enrollment product then running apply reg and process and apply reg operation, there are 2 issues.
|
|||
Resolution: |
The lookBackDate in processandapplyregistrations operation is now correctly set, so the Date Paid To is not moved up. |
|||
32468894 |
3-24901222791 |
POL-7303 |
BP |
Task is stuck in 'PROCESSING' status if the node leaves the cluster |
Description: |
When the node processing a task leaves the cluster or if the node is stopped while the task is being processed, then the task remains in 'PROCESSING' status. The other nodes in the cluster should recover/re-queue that task. |
|||
Resolution: |
When a node leaves the cluster, then the tasks that are currently being processed by that node are now recovered by the other node(s) in the cluster. |
|||
32477351 |
POL-7318 |
BP |
Adjustment Rules API and Premium Schedule Lines API are returning incorrect location header |
|
Description: |
Adjustment Rules API and Premium Schedule Lines API were returning incorrect location header |
|||
Resolution: |
Adjustment Rules API and Premium Schedule Lines API are now returning correct location header with id of AdjustmentRule/PremiumScheduleLine that is created |
|||
32485728 |
3-25008194831 |
POL-7341 |
BP |
Create time valid dynamic records for policy enrollments without start date |
Description: |
The dynamic record related business validations were not done for policy enrollments. |
|||
Resolution: |
The business rule validations related to policy enrollments will now be triggered and correct error message will be sent e.g. GEN-DYNA-010 for missing start date on time valid record. |
|||
32488144 |
POL-7354 |
BP |
Unable to query policy enrollments on person.relationIdentifierList.identifier |
|
Description: |
Generic HTTP API search on <child>.relation(+)relationIdentifierList.identifier.like("123â€) gave error: For example on policyenrollments: api/generic/policyenrollments?q=person.relationIdentifierList.identifier.like("123â€) |
|||
Resolution: |
When a search is done on a relation child, like policy enrollments, addresses, using relationIdentifierList, this search is now properly executed. |
|||
32508961 |
3-25179866201 |
POL-7409 |
BP |
NullPointerException when original PCP is segmented due to a change which results in two discounts within same month |
Description: |
If the PCP is segmented on a time valid flex code dynamic field, which is used as a dimension on adjustments, then the run example calculation returns a NullPointerException which is not expected. |
|||
Resolution: |
The NullPointerException will not be raised any more. |
|||
32519020 |
3-25196339551 |
POL-7432 |
BP |
Input amount of non-prorated adjustment function in the last PCP is incorrect |
Description: |
When system is configured with two adjustments of different types (one being % adjustment and other being non prorated function adjustment scoped on one of the premium schedule) and having the same sequence, then input amount of non-prorated adjustment function in the last PCP is incorrect. |
|||
Resolution: |
The correct input amount is passed to the non-prorated function dynamic logic now. |
|||
32523878 |
POL-7437 |
BP |
Reference sheet import element datatype is not registered in all the nodes of cluster |
|
Description: |
Reference sheet Import element datatype is not registered in all the nodes of cluster. |
|||
Resolution: |
Reference sheet lines are now being imported successfully in multi-nodes cluster setup. |