Release Notes for Oracle Health Insurance Claims Adjudication Patch 4.24.1.0.7
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 4.24.1.0.7.
Version compatibility: Oracle Health Insurance Claims Adjudication Release 4.24.1.x is only compatible with other Oracle Health Insurance applications release version 4.24.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. |
Enhancements
ID | Summary | Patch |
---|---|---|
NXT-31617 |
Increase the length of scope attribute on OAuthClientCredentialsGrantConfiguration entity The scope attribute in the OAuthClientCredentialsGrantConfiguration entity is currently limited to 100 characters. This is not sufficient to store scope values provided by OIC. |
Bug Fixes
BugDB | SR | Internal | Summary |
---|---|---|---|
37886025 |
3-40242015751 |
NXT-31485 |
Generate financial message fails when length of invoice bulking group on transactions exceeds 100 |
Description: |
Generate financial message fails when length of invoice bulking group on transactions exceeds 100 |
||
Resolution: |
Generate Financial message activity will complete successfully for transactions with invoice bulking group of length greater than 100 . |
||
37881462 |
3-40524754251 |
NXT-31474 |
Download icon is missing for limit consumptions in adjudication limit counters page |
Description: |
It is not possible to download limit consumptions |
||
Resolution: |
Download icon is added now for limit consumptions |
||
37814260 |
NXT-31387 |
ClaimLine message marked as Suppress logging in UI is displayed in expanded mode |
|
Description: |
A Claimline message with suppress logging in UI enabled is still displayed in UI when claimline is configured as results view and expanded view toggle is enabled in Claims page |
||
Resolution: |
ClaimLine message marked as Suppress logging in UI is not displayed in expanded view mode |
||
37780464 |
NXT-31353 |
The additional fields on the summary page is not aligned properly |
|
Description: |
The additional fields is not aligned properly in claimline summary drawer and some information is hidden and not displayed for users |
||
Resolution: |
The additional fields under claim line summary drawer, are properly aligned and clearly visible |
||
37917896 |
3-40601455857 |
NXT-31557 |
Flter with context string is not working in claim line table edit mode |
Description: |
When a user attempts to filter claim line "procedure2" based on the user selection of "procedure" field, the filter is only applied during trigger condition of value change. It is not applied during the claim line edit operation through filter. |
||
Resolution: |
The context being evaluated to correct value during the claim line edit operation when used with filter for a field. |
||
37681681 |
NXT-31197 |
Dynamic fields in multiple floorplan sets are displaying incorrectly |
|
Description: |
When a usage is added to Floorplan to display the same dynamic field in multiple sets of the entity page, the respective fields are not rendering the values as expected. |
||
Resolution: |
When a usage is added to the floorplan to display an existing dynamic field in a different section of the entity page, it detects any prior usage of that field and updates it with the latest configuration. As a result, there are no longer multiple occurrences of the same dynamic field |
||
37882455 |
NXT-31478 |
In claims page the section separator shows up only for the last section |
|
Description: |
In Claims page, Section seperator is not shown when there are more than one section. The seperator is missing between section 1, 2, 3 |
||
Resolution: |
Section seperator is displayed for all the sections in form component |
||
37853034 |
NXT-31443 |
Apply and next button fails to navigate to next claim line when claimline page is in edit state |
|
Description: |
While editing a claim line on the claimline details page, clicking the 'Apply and Next' button does not navigate to the next claim line. |
||
Resolution: |
The claim line navigation issue with the 'Apply and Next' button on the Claim Line Details page has been resolved. The button now correctly saves the current claim line and navigates to the next one as expected. |
||
37893793 |
NXT-31510 |
PUT and PATCH operations on claims API does not update external claims data. |
|
Description: |
PUT and PATCH operations on claims API gives success response, but does not update external claims data. |
||
Resolution: |
User can now edit external claim data using PUT or PATCH operation on claims API |
||
37693756 |
3-39900404711 |
NXT-31291 |
Conditional default value is not getting set based on trigger condition |
Description: |
Default value setting of one flex code field based on trigger condition of the value selected in another flexcode field is not working. Instead the default value which was set earlier is getting cleared |
||
Resolution: |
Default value is not getting cleared based on trigger condition |
||
37728096 |
NXT-31249 |
Claim Line Detail Page - Blank screen is displayed when summary section is opened after clicking on next or previous button |
|
Description: |
The summary section goes blank whenever its opened on claim line detail page after clicking on Next or previous button while navigating from one claim line to another. |
||
Resolution: |
Claimline summary section can be viewed properly after clicking on next or previous button |
||
37774614 |
NXT-31345 |
Labels are not displayed when configured in search page |
|
Description: |
When flexcodes are configured as labels in search page, it is not displayed. The labels are displayed properly in hierarchical recursive page |
||
Resolution: |
Labels for flex code fields are working as expected when configured in search page |
||
37849069 |
3-40346571471 |
NXT-31437 |
Not able to retrieve parent context values in view mode of the page in a tab |
Description: |
For a use case when a user wants to filter out a field in the tab, based on the type of the claim, the following condition works correctly in create mode : "condition": "context.claim.type === 'R'". It does not work when the page is opened in view mode |
||
Resolution: |
For tab detail pages conditional evaluation issue is fixed for both create and edit mode |
||
37944428 |
NXT-31634 |
User information is not available to use in floorplans using userJET property |
|
Description: |
The userJET property in the floorplan does not support setting default values or filtering data based on the current user. |
||
Resolution: |
Id and displayName fields of userJET property can be used in the floorplan for setting default values or filtering data based on the current user. |
||
37923334 |
NXT-31566 |
Global activity page does not load messages |
|
Description: |
In the ADF UI, it is possible to troubleshoot why an activity fails with technical errors. The dynamiclogic error on the child activity is shown. User does not see this in the JET UI, making troubleshooting difficult. |
||
Resolution: |
All the messages are getting displayed properly in the activity messages tab on Global Activities page. |
||
37851825 |
3-40376948101 |
NXT-31439 |
Unable to add a claimline before it is saved in results view |
Description: |
When the property Inline Expand (dualDefault) is not present for the claims floorplan (claimline open in separate page rather than inline) then while creating a claim, we are unable to add a claimline in create mode. Only after it is saved, user is able to add a claimline |
||
Resolution: |
Users can add claimline while creating the claim together before Save |
||
37940890 |
NXT-31603 |
Evaluation through init condition is not working for claim line edit |
|
Description: |
When user wants to filter the procedure2 field in claim line based on the selected value in the "procedure" field. Currently, the filter is only being applied during the value change trigger, but it is not being applied when using the initConditions while in edit |
||
Resolution: |
The filter based on conditional evaluation in edit mode is getting retained |