Release Notes for Oracle Health Insurance Claims Adjudication Release 4.25.1.0.0
This document contains the release notes for Oracle Health Insurance Claims Adjudication Release 4.25.1.0.0.
| Version compatibility: Oracle Health Insurance Claims Adjudication Release 4.25.1.x is only compatible with other Oracle Health Insurance applications release version 4.25.1.x unless explicitly stated otherwise. |
| In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases. |
Enhancements
| ID | Summary | Patch |
|---|---|---|
CPN-2919 |
Operational Reports and Data Transfer This release introduces two new features:
Documentation Links: |
|
CPN-3076 |
Move PHI Logs to OCI Object Storage With the introduction of the PHI logging feature in operational reporting and the new data transfer IP, a significant increase in PHI log volume is expected. To optimize database storage usage and improve overall performance, PHI logs are migrated from the database to lower-cost storage options. In cloud deployments, logs are stored in OCI Object Storage, while in on-premise environments, logs are stored in the file system. This change reduces database load, ensuring better efficiency and scalability as log volumes grow. Following this enhancement, PHI logs are retained in the database for 60 days, allowing customers to retrieve recent logs via the existing This enhancement improves database performance by significantly reducing storage overhead while maintaining access to recent logs. If you are a cloud customer and if you have relied on long-term PHI log retention, review your internal processes and work with AMS as needed to ensure continued access to historical data. No changes are required for application integrations querying logs within the 60-day window, but if you are a cloud customer, plan for an alternative retrieval approach for older logs. |
|
CPN-3218 |
Groovy 4 upgrade This release includes an upgrade from Groovy 3.x to Groovy 4.0.24. This upgrade introduces performance enhancements, new syntax options, and improved security. The upgrade also introduces breaking changes that may impact existing dynamic logic, as some APIs and packages are removed. For detailed information, please refer to the Groovy 4.0 Release Notes. Groovy 3 provided duplicate versions of several classes in legacy packages to ease migration. With Groovy 4, these legacy classes are removed. For detailed information, please refer to the Groovy 3.0 Release Notes. For example, classes previously available in both To enable compatibility with Groovy 4, the bytecode of existing dynamic logic is reset during the upgrade. This reset causes the application start-up time to be slightly longer on the first startup after the upgrade, as the dynamic logic are recompiled at startup time. Future application restarts do not recompile this bytecode, so subsequent startups are faster. |
|
CPN-3246 |
File type validation This enhancement introduces a new validation check that ensures uploaded files (for example, via |
|
CPN-3247 |
Removed database details from error messages Certain database error responses, such as ORA-12899 ("value too large for column") expose internal database details, such as table and column names. To prevent this information from being revealed in API/IP responses, these error messages are modified to replace direct references to table and column names with corresponding entity and attribute names. |
|
CPN-3249 |
Cache control headers for sensitive data This enhancement prevents sensitive information from being stored locally in a browser using the property Documentation Links: |
|
CPN-3356 |
Antivirus Scanning for Uploaded Files in Cloud Deployments This enhancement introduces Antivirus scan for files uploaded to OHI (for example, through Data File Sets IP or Exchanges IP in OIG application) in cloud deployments. Only files that pass the Antivirus scan are processed, ensuring that uploaded files do not pose a security risk. |
|
CPN-3377 |
Document maximum number of dynamic fields on objects This enhancement extends the generic tables API with information about the maximum number of single-value non-time-valid dynamic fields available on an entity. Documentation Links: |
|
CPN-3456 |
Channel HTTP headers This enhancement introduces two new custom HTTP headers:
These headers enable tracking of API/IP request origins by identifying the type and context of the originating channel (e.g., JET UI, portals, etc.). This structured tracking provides reliable data for improved monitoring and analytics. When making calls to OHI APIs from external systems, such as portals, customers are encouraged to set these headers. Doing so enhances the ability to monitor request origins, supporting better operational insights and tracking. Documentation Links: |
|
NXT-24521 |
Optimized data file storage using OCI Object Storage in SaaS Prior to this release, data files were stored in the database. To optimize storage cost and improve overall performance, data files are now stored in Oracle-managed OCI Object Storage for SaaS deployments. The interfaces for uploading and downloading data files (via Data File Sets IP and Exchanges IP in OIG application) remain unchanged. For on-premise deployments, data files continue to be stored in the database, so existing behavior is unaffected. |
|
NXT-25384 |
GET search through query API isn’t supported The GET method for searching entities via /generic/<entityName>?queryParams is no longer supported. Instead, you can use POST requests to /generic/<entityName>/search with the query parameters included in the request body. |
|
NXT-27727 |
New page for draft provider pricing clauses across pricing worksheets With this enhancement, a new page in JET user interface is introduced to view the draft provider pricing clauses across the pricing worksheets. Also, the advance search on the draft provider pricing clause tab of the pricing worksheet page is enhanced to include all the attributes of the draft provider pricing clauses which were not available in the previous release. |
|
NXT-28043 |
Extend the advanced search fields for the Usages page This enhancement makes it possible to expand the advanced search fields on the Usages page. |
|
NXT-28070 |
New page for Eligibility Checks A new JET UI page, "Eligibility Checks" has been added to search for and view the eligibility check details. |
|
NXT-28899 |
JET 17 upgrade This enhancement upgrades the JET (JavaScript Extension Toolkit) core library to version 17, bringing the following changes:
Documentation Links: |
|
NXT-29151 |
Increased length on first name field This enhancement increases the length of the person first name and middle name fields to 120 characters. |
|
NXT-29153 |
Validation that prevents a claim line from being submitted with a negative charged amount This enhancement introduces an embedded validation that prevents a claim line from being submitted with a negatively charged amount. |
|
NXT-29186 |
Claim Code Sequence This enhancement introduce the ability to use user-defined sequence for claim code generation Documentation Links: |
|
NXT-29279 |
Allow Iframe content in OHI applications This enhancement enables customers to integrate Oracle Health Insurance Components with Oracle Guided Learning (OGL). This is meant for customers who have purchased OGL. Documentation Links: |
|
NXT-29355 |
Improve performance of operational and search pages This enhancement removes redundant fields from the POST request payload, such as fields configured in Quick Search, Advanced Search of Search and View and Edit Object List floorplans, as well as in the Search and Popup Tail sections of LOV floorplans. It replaces the use of expand: "all" in operational pages with specific expand values for parent and child resources as defined in the floorplan, reducing the overall response payload for API requests originating from the UI. It further reduces duplicate API calls made during application login and improves the performance of View and Edit Object – Recursive pages by deferring API calls used to construct the property model for dynamic data under the Tab Table More section until the Download action is triggered. Collectively, these changes reduce API calls and API response payload sizes for a faster UI experience. |
|
NXT-29605 |
Support for deeplink is available for static/dynamic fields of string type This enhancement supports deeplink for static/dynamic fields of string type Documentation Links: |
|
NXT-29732 |
Improved performance of user interface searches This enhancement removes all the non-operational links from the response at header level and the child lists level unless specified in the post request body. Changes are done to remove links for dynamic fields and records as well. The 'excludelinks' parameter is set to true to reduce the overall response payload for the API requests originating from the UI Documentation Links: |
|
NXT-29973 |
Support Accept and Deny actions in the Claim Submit API This enhancement introduces additional parameters to the Claim Submit API, making it possible to deny a claim directly through the submit API. This capability precludes multiple API calls when denying a claim, introducing a performance gain that improves user experience. Documentation Links: |
|
NXT-30347 |
Introduces native support for limits that aggregate by group or event. This enhancement makes it possible to support a mix of both group-level limits and family-level limits. |
|
NXT-30352 |
Exclude links from dynamic fields for generic API POST search operation New parameter "excludelinks" have been added for removing the non-operational links of child and reference resources (as per search result) until the user explicitly mention the field link in fields section. For Dynamic fields and dynamic records in response a new attribute "linkId" will be returned containing the value as id of the link. Documentation Links: |
|
NXT-30439 |
Resolve pends and remove messages actions on large claim page The group (sub-claims) page tab-level actions are extended with the below actions, that give the capability for a user to directly: * Resolve Pends * Remove Messages by selecting one or more groups (sub-claims) that belongs to a large claim. |
|
NXT-30614 |
Additional dynamic fields on the relation entity This enhancement increases the number of single-value non-time-valid dynamic fields that can be stored on the Relation entity. |
|
NXT-30615 |
Claim Submit History This enhancement introduces the ability to capture the user and time when a claim is submitted. Documentation Links: |
|
NXT-30620 |
Reference Sheet Lines: As-of Date & Search Filtering for Time-Based Records This enhancement enhances the search functionality for time valid reference sheet lines by enabling users to filter data between a start and end date, as well as specify an "asOfDate" within that range. This will improve both the accuracy and convenience of retrieving time-sensitive data. |
|
NXT-30624 |
View Technical Errors, System Event Logs, and Queue Information Page. This enhancement improves operational efficiency and simplifies troubleshooting by giving users more control over error management. It includes an enhanced View Technical Errors page for a better user experience, a new System Event Logs page for easy access to system events, and a new View Queue Information page (for Claims only) to help users manage and monitor queue-related data more effectively. Documentation Links: |
|
NXT-30781 |
Additional financial message attributes on invoice and invoice lines This enhancement extends the number of available attributes on invoice and invoice lines in the financial message by additional sixty bringing the total number of available attributes to ninety. |
4.24.1.0.3 |
NXT-30994 |
Reinsurance Regimes (Data Model) This enhancement introduces native entities to store reinsurance regimes and related configurations, along with new entities at the claim and claim line levels to store reinsurance coverage details. The following entities have been added:
Additionally, the following entities have been updated:
Also, the following new labels have been introduced:
|
|
NXT-31159 |
Update in LogBack Configuration In this release, the Please update your |
|
NXT-31440 |
Claims in progress and tasks processing performance reporting views This release introduces two new reporting views:
Documentation Links: |
|
POL-14428 |
New OHI specific HTTP library to make HTTP calls from dynamic logic The While this release continues to support both |
|
POL-15307 |
Financial: Ability to Send Accounting Details Separately OHI application sends out accounting details along with the financial message. So, the granularity of the grouping of account details is bounded by invoice grouping. That is, only the details within an invoice can be grouped. This poses challenges for customers who require accounting to be done at a different level compared to the invoice. For example, an invoice is per member, but accounting is across members for a product. With this enhancement, it will be possible to send out accounting details as part of a separate batch Documentation Links: |
4.24.1.0.4 |
POL-15334 |
Additional Data Masking Functions This enhancement introduces two new data masking functions:
Along with the new masking functions:
|
|
POL-15369 |
Create/Update Registration Records to Handle Payments This enhancement allows users to register policy binder payments in OHI as "Generic" Payments. It allows users to manage binder payments and generate accounting details. Documentation Links: |
|
POL-15792 |
Memory optimization in extract activity Improved memory efficiency when loading dynamic fields with single, non-time-valid values in extract activity. |
4.23.1.0.10, 4.23.2.0.4, 4.24.1.0.1 |
POL-15884 |
User Defined Validations for Registrations This enhancement introduces the ability to define additional validations for the registrations entity when using generic APIs to create or update registrations. A new dynamic logic of signature User Defined Validation (Registration) is introduced to support this functionality. Documentation Links: |
4.24.1.0.5 |
POL-16031 |
Start integration gateway exchange using a list of payment registrations as its payload This enhancement introduces the ability to invoke an insurance gateway exchange, using a list of payment registrations as its payload. The exchange is invoked either by API or through a new set of controls in the user interface. Documentation Links: |
4.24.1.0.4 |
POL-16447 |
Repeatable Generation of Accounting Details This enhancement introduces embedded logic that ensures that the same accounting details for a given grouping value and registration combination are not generated twice. |
4.24.1.0.5 |
POL-16484 |
Accounting Details Per Financial Transaction Set This enhancement allows accounting details, as generated in the financial message, to be persisted. It also enables the inclusion or exclusion of the subject (policy/claim) and reversal indicator as bulking criteria when creating accounting details. Note: For financial transactions created prior to this feature, the reversal indicator cannot be excluded as part of the bulking criteria. |
4.24.1.0.6 |
Additional Upgrade Steps
Pre-Upgrade Phase
-
Execute the below SQL statement with the user: OHI_CLAIMS_OWNER and commit.
UPDATE OHI_MESSAGES_B SET CODE = CODE || '_TO_BE_DELETED' WHERE CODE IN ('OHI-TASK-IP-001', 'OHI-TASK-IP-002', 'OHI-TASK-IP-003');
commit;1) Groovy 4 upgrade
Migration Details for groovy.util Classes
The following classes are removed from groovy.util package in Groovy 4. Update the dynamic logic to import the classes from groovy.xml package instead:
-
groovy.util.XmlNodePrinter -
groovy.util.XmlParser -
groovy.util.XmlSlurper -
groovy.util.XmlUtil -
groovy.util.slurpersupport.Attribute -
groovy.util.slurpersupport.Attributes -
groovy.util.slurpersupport.FilteredAttributes -
groovy.util.slurpersupport.FilteredNodeChildren -
groovy.util.slurpersupport.GPathResult -
groovy.util.slurpersupport.NamespaceAwareHashMap -
groovy.util.slurpersupport.NoChildren
In Groovy 3, classes from groovy.util package are automatically imported. With Groovy 4, these classes in groovy.xml package require explicit import statements.
|
To identify dynamic logic scripts that require modification, use the following POST request to api/generic/dynamiclogic/search:
{
"resource": {
"q": "logic.like('%XmlNodePrinter%').or.logic.like('%XmlParser%').or.logic.like('%XmlSlurper%').or.logic.like('%XmlUtil%').or.logic.like('%groovy.util.slurpersupport%')"
}
}Make these changes before upgrading to this release. The minimum required OHI version to apply these changes is 4.23.1. So, perform these changes if you are currently on version 4.23.1, 4.23.2, or 4.24.1.
Code Migration Examples
Example 1: Using XmlSlurper Without Import
Current dynamic logic: Uses XmlSlurper without an explicit import (implicitly relying on groovy.util):
def result = new XmlSlurper().parseText(response)Updated dynamic logic: Add an explicit import for groovy.xml.XmlSlurper:
import groovy.xml.XmlSlurper
def result = new XmlSlurper().parseText(response)Or use the fully qualified name:
def result = new groovy.xml.XmlSlurper().parseText(response)Example 2: Explicitly Importing groovy.util.XmlSlurper
Current dynamic logic: Imports groovy.util.XmlSlurper explicitly:
import groovy.util.XmlSlurper
def result = new XmlSlurper().parseText(response)Updated dynamic logic: Update the import to groovy.xml.XmlSlurper:
import groovy.xml.XmlSlurper
def result = new XmlSlurper().parseText(response)Post-Deploy Phase
1) New OHI specific HTTP library for dynamic logic
Migration details
Identify the existing dynamic logic
To identify dynamic logic that require modification, use the following POST request to api/generic/dynamiclogic/search:
{
"resource": {
"q": "logic.like('%.path(%').or.logic.like('%.request(%').or.logic.like('%.invoke(%')"
}
}If the number of dynamic logic is large, use the (new) Data Transfer IP to query and export all the impacted dynamic logic.
Post-Upgrade Phase
-
Execute the below SQL statement with the user: OHI_CLAIMS_OWNER and commit.
SET SERVEROUTPUT ON
DECLARE
v_new_id OHI_MESSAGES_B.ID%TYPE;
v_sql VARCHAR2(1000);
v_table_name VARCHAR2(30);
v_column_name VARCHAR2(30);
CURSOR c_child_tables IS
SELECT acc.TABLE_NAME, acc.COLUMN_NAME
FROM ALL_CONSTRAINTS ac
JOIN ALL_CONS_COLUMNS acc ON ac.CONSTRAINT_NAME = acc.CONSTRAINT_NAME
WHERE ac.CONSTRAINT_TYPE = 'R'
AND ac.R_OWNER = 'OHI_CLAIMS_OWNER'
AND ac.R_CONSTRAINT_NAME = (SELECT CONSTRAINT_NAME
FROM ALL_CONSTRAINTS
WHERE TABLE_NAME = 'OHI_MESSAGES_B'
AND CONSTRAINT_TYPE = 'P'
AND OWNER = 'OHI_CLAIMS_OWNER')
-- Condition to avoid updating refernce in TL table, keep dyn as we want to replace those records to point to new values
AND acc.TABLE_NAME NOT IN ('OHI_MESSAGES_TL');
BEGIN
FOR i IN (SELECT ID, CODE FROM OHI_MESSAGES_B WHERE code LIKE 'OHI-TASK-IP-00%') LOOP
SELECT ID INTO v_new_id
FROM OHI_MESSAGES_B
WHERE CODE = 'OHI-IP-TASK-00' || SUBSTR(i.CODE, 15, 1);
DBMS_OUTPUT.PUT_LINE('Updating references for ' || i.CODE || ' to OHI-IP-TASK-00' || SUBSTR(i.CODE, 15, 1));
OPEN c_child_tables;
LOOP
FETCH c_child_tables INTO v_table_name, v_column_name;
EXIT WHEN c_child_tables%NOTFOUND;
v_sql := 'UPDATE ' || v_table_name || ' SET ' || v_column_name || ' = :v_new_id WHERE ' || v_column_name || ' = ' || i.ID;
EXECUTE IMMEDIATE v_sql USING v_new_id;
IF SQL%ROWCOUNT > 0 THEN
DBMS_OUTPUT.PUT_LINE('Updated ' || SQL%ROWCOUNT || ' rows in ' || v_table_name);
END IF;
END LOOP;
CLOSE c_child_tables;
DELETE FROM OHI_MESSAGES_B WHERE code = i.CODE;
END LOOP;
COMMIT;
END;
/Upgrade Steps for Installation
To perform the upgrade, perform the following steps:
-
Perform any pre-upgrade steps.
-
Stop all the managed nodes running the existing version of the application.
-
Perform any pre-undeploy steps.
-
Undeploy the existing version of the application.
-
Back up the database.
-
Perform any post-undeploy steps.
-
Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.
-
Change Installation Configuration: In
<OHI_ROOT>/util/install, make a copy ofohi_install.cfg.templateand name itohi_install.cfg. -
Edit
ohi_install.cfgto contain your specific database connection data and other configuration settings. The settings are explained in the file itself. -
Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)
-
Run the Upgrade script:
-
Open a command window and browse to
<OHI_ROOT>/util/install. -
Run the upgrade by executing
./ohi-update.sh .
-
-
Make the required changes to the ohi properties file
-
Perform any post-upgrade steps
-
Start WebLogic application server
-
Deploy the Application
-
Perform any post-deploy steps
Additional Upgrade Steps for Installation
|
The following phases are defined:
|
Post-Undeploy Phase
1) Create a new database user ohi_claims_rpt_user
As an admin user, create a new user ohi_claims_rpt_user, which is used to run operational report queries.
create user ohi_claims_rpt_user identified by <password>;
grant create session to ohi_claims_rpt_user;
grant create synonym to ohi_claims_rpt_user;2) Create a data source ohi-operational-reporting-datasource
Configure a new data source named ohi-operational-reporting-datasource in the WebLogic Server to connect to ohi_claims_rpt_user. For detailed steps, refer to the Installation Guide.
3) Configure Data Transfer
-
On-premise deployments:
-
Follow the steps mentioned in Configure Database Directories and Properties
-
Install DBMS_CLOUD package in on-premise deployments. Refer to My Oracle Support Doc ID 2748362.1 for details.
-
-
SaaS deployments:
-
Follow the steps mentioned in Configure Object Storage Buckets and Properties
-
As an admin user, grant the following permission to
ohi_claims_ownerin SaaS deployments only.
-
grant select on v$pdbs to ohi_claims_owner;
4) Apply WLS PATCH SET UPDATE and Coherence 14.1.1 Feature Pack 22.06 Cumulative Patch
Refer Required Software for details.
Post-Upgrade Phase
2) Update logback configuration file
In this release, the logback-core library is upgraded. As a result, the component previously named SizeAndTimeBasedFNATP is renamed to SizeAndTimeBasedFileNamingAndTriggeringPolicy.
Please update your logback.xml configuration file to reflect this change.
3) Configure Data Transfer
-
On-premise deployments: Follow the steps mentioned in Configure Database Scheduler Job
-
SaaS deployments: Follow the steps mentioned in Configure Object Storage Use Cases and Database Scheduler Job
Configuration Properties
| Ref | Action | Description |
|---|---|---|
CPN-2919 |
Added |
ohi.views.metrics Timer metrics to indicate time taken to execute the query. |
CPN-2919 |
Added |
ohi.data.transfer.target.db.directory.name Name of the database directory where the files generated for data transfer operation will be stored. Applicable only for on-premise deployments. |
CPN-2919 |
Added |
ohi.phi.logs.data.transfer.target.db.directory.name Name of the database directory where the PHI logs will be stored. Applicable only for on-premise deployments. |
CPN-2919 |
Added |
ohi.reporting.fetched.rows.count.per.view Counter metrics which indicate the number of rows fetched per view. |
CPN-3356 |
Added |
ohi.antivirus.scan.enabled Added a new mandatory property to enable/disable Antivirus scanning for data file uploads. Set the value of this property (in properties file, not using properties API) to true in cloud deployments and false in on-premise deployments. |
NXT-24521 |
Added |
ohi.datafile.object.storage.bucket.folder.structure Folder structure in OCI Object Storage bucket where data files are stored. Folder structure must end with '/'. Example - CLAIMS/DATAFILES/. Default value is {appName}/DATAFILES/. This property is applicable only in SaaS deployments. |
NXT-24521 |
Added |
ohi.datafile.object.storage.part.size Size of each data file part in bytes when data file is uploaded to OCI Object Storage using multipart upload. Big data file is split in multiple parts of mentioned size. Default size is 10000000 bytes (10 MB). This property is applicable only in SaaS deployments. |
NXT-24521 |
Added |
ohi.datafile.object.storage.enabled Enables storing data file content in OCI Object Storage. By default, data files are in the database. This property is applicable only in SaaS deployments. |
NXT-25384 |
Removed |
ohi.service.queryapi.get.support Removed deprecated property. |
NXT-29279 |
Added |
ohi.ui.iframe.allowlist.url This property contains list of URLs to be allowed to load inside iFrame in OHI application. |
POL-15307 |
Added |
ohi.processing.datafilesize.GENERATE_ACCOUNTING_DETAIL_MESSAGES Utilized to to create one or multiple data files for generated accounting detail message. Default value = 1, allowed value: postive numeric value. |
POL-15307 |
Added |
ohi.financialmessage.create.noninvoiceaccdetail Decides the creation of non-invoice accounting details in financial message. If set to true, activity creates non-invoice account details in financial message. If the property is set to 'false', non-invoice accounting details won’t be created |
Web Services
| Ref | Action | Description | ||
|---|---|---|---|---|
CPN-2919 |
Added |
reportingviews IP Added a new IP reportingviews to generate reporting views. |
||
CPN-2919 |
Added |
reportingviews metadata IP Added a new IP to query reporting views columns metadata. |
||
CPN-2919 |
Added |
reportingviews API Read-only API to query reporting views metadata. |
||
CPN-2919 |
Added |
userviewpreferences API Added a new API to configure search preferences for operational reporting. |
||
CPN-2919 |
Added |
viewfloorplans API Added a new API to configure floorplan for operational reporting. |
||
CPN-2919 |
Added |
operationalreporting IP Added a new IP to query the reporting views. |
||
CPN-2919 |
Added |
datatransfer IP Added a new IP to export data from base views (including PHI data). |
||
CPN-2919 |
Added |
datatransferlogs API Read-only API to query data transfer logs. |
||
CPN-2919 |
Added |
objectstoragecredentials API Added a new API to configure credentials to connect to the OCI Object Storage. Applicable only for SaaS deployments. |
||
CPN-2919 |
Added |
objectstorageapikeyusecases API Added a new API to configure credentials to connect to the OCI Object Storage using API keys authentication method. Use objectstoragecredentials API to configure the credentials prior to creating data using this API. Applicable only for SaaS deployments. |
||
CPN-2919 |
Added |
objectstorageconfigurationfileusecases API Added a new API to configure credentials to connect to the OCI Object Storage using OCI configuration file. Applicable only for SaaS deployments. |
||
CPN-2919 |
Added |
objectstorageresourceprincipalusecases API Added a new API to configure credentials to connect to the OCI Object Storage using resource principal authentication method. Applicable only for SaaS deployments. |
||
CPN-3076 |
Modified |
autopurgemetadata API The option to configure the retention period for PHI logs is removed. |
||
CPN-3076 |
Modified |
logphievents API PHI logs are retained in the database for 60 days, allowing customers to retrieve recent logs via the existing |
||
CPN-3249 |
Modified |
All APIs When |
||
CPN-3356 |
Modified |
Data File Sets IP
|
||
CPN-3356 |
Modified |
datafilesets API Added 2 new optional attributes status and extraInfo. |
||
CPN-3356 |
Modified |
datafiles API Added 2 new optional attributes status and extraInfo. |
||
CPN-3377 |
Modified |
tables API Added a new attribute sizeCategory to tables API. |
||
CPN-3456 |
Modified |
All APIs/IPs Two new custom optional headers are introduced: |
||
NXT-29973 |
Modified |
Parameters action: Specifies the action to be taken. Allowed values are: accept: Proceed with processing the claim. deny: Reject the claim submission. fatalMessageCode: A code that specifies the reason for denying the submission. This parameter is required only if action is deny. |
||
NXT-30347 |
Added |
Claims In Integration Point new optional attribute familyCode in enrollment>products>product |
||
NXT-30347 |
Added |
Enrollment Integration Point - Response new optional attribute familyCode in products>product |
||
NXT-30615 |
Modified |
Purge Claims Claim submit history is purged when a claim is purged from the system |
||
NXT-30615 |
Modified |
Submit Large Claim API A claim submit history record is created when a large claim is submitted. |
||
NXT-30615 |
Modified |
Submit Claim API A claim submit history record is created when a claim is submitted. |
||
NXT-30615 |
Modified |
Claims In Integration Point Create claim submit history when a claim is submitted through the integration point |
||
NXT-30615 |
Modified |
Claims update API Create claim submit history when a claim is submitted through the claims update API |
||
NXT-30624 |
Added |
systemeventlogs API Added a new API to view and update System Event Logs. |
||
NXT-30624 |
Modified |
taskprocessing IP Added a new operation to restart a list of errored task in the system. |
||
POL-15307 |
Added |
financialtransactions/{id}/accountingdetails/undo IP New IP to make accounting details for a specific transaction void |
||
POL-15307 |
Added |
accountingdetails API Read-only API to query on accounting details (new entity). |
||
POL-15307 |
Modified |
financialtransactionprocessdata API Added attribute accountingDetailsGeneratedDateTime |
||
POL-15369 |
Added |
Create Accounting Details from Registrations IP New long running operation to create accounting details for the selected registrations |
||
POL-15369 |
Added |
registrations/{id}/accountingdetails/undo New IP to undo accounting details for a specific registration |
||
POL-15369 |
Added |
registrations/{id}/accountingdetails/create New IP to create accounting details for a specific registration |
||
POL-15369 |
Modified |
registrations API New type added: "G"(eneric) and automatic generation of code. And added attributes Currency and Grouping. GET, PUT, POST, PATCH, DELETE is enabled on the registration entity
|
||
POL-16031 |
Modified |
Generic API for Macro history Subject ID is made optional |
||
POL-16031 |
Modified |
Macro IP Attribute requestContextList is added |
||
POL-16031 |
Modified |
Generic API for Macro definition Value REGI ("Registration" ) and list indicator are added. |
||
POL-16447 |
Added |
accountinggroupingdetails API New read-only API |
||
POL-16447 |
Modified |
registrations/{id}/accountingdetails/undo IP Added removal of accounting detail groupings |
||
POL-16447 |
Modified |
registrations API Added accountingDetailGroupingList (display only) |
||
POL-16447 |
Modified |
registrations/{id}/accountingdetails/create IP Added check if accounting detail grouping already exists: FIN-IP-REGI-007 |
||
POL-16484 |
Modified |
basefinancialobjects API Object has been made auditable |
||
POL-16484 |
Modified |
financialtransactions API Object has been made auditable |
||
POL-16484 |
Modified |
financialtransactiondetails API Object has been made auditable |
||
POL-16484 |
Modified |
Run Calculation and Produce Invoice for a Policy New parameters added in the request:
|
||
POL-16484 |
Modified |
financialtransactionprocessdata API Attribute accountingDetailGeneratedDateTime has been removed |
||
POL-16484 |
Modified |
accountingdetails API Reference to financial transaction has been replaced by financialMessageId. Attribute stampId is added. Reversal indicator has been made optional |
||
POL-16484 |
Modified |
Cancel Policy and Produce Invoice IP New parameters added in the request:
|
||
POL-16484 |
Removed |
Long running operation for creating accounting details for financial transaction Has been replaced by functionality in Generate financial message. |
||
POL-16484 |
Removed |
financialtransactions/{id}/accountingdetails/undo IP Has been replaced by functionality in unsend financial message |
Data Conversion
| Ref | Action | Description |
|---|---|---|
NXT-24521 |
Added |
DataFile Storage Type The storage type of the existing data files is set to 'DB' in dat_data_files table. |
POL-16031 |
Added |
List indicator New indicator list on Macro definition is set to false |
Dynamic Logic
| Ref | Action | Description |
|---|---|---|
CPN-3218 |
Modified |
Groovy 4 upgrade Upgraded Groovy from 3.x to 4.0.24. |
POL-14428 |
Added |
New HTTP Library Introduced new OHI-specific HTTP library to make HTTP calls from dynamic logic. |
POL-14428 |
Deprecated |
initCallOut initCallOut method is deprecated. |
POL-14428 |
Deprecated |
webTarget webTarget method is deprecated. |
POL-15369 |
Added |
Registration Code Generation New signature for automatic generation of registration.code |
POL-15369 |
Added |
Create accounting detail with dual for registration New signature for creating accountingDetail and accountingDetailDual for a specific registration |
POL-15369 |
Added |
Create Accounting Detail (Registrations) New signature for creation of accounting detail for registration |
POL-15369 |
Added |
AddRegistration New pre-defined method to add a registration of type "G"(eneric) |
POL-15369 |
Added |
UpdateRegistration New pre-defined method to update a registration of type "G"(eneric) |
UI Changes
| Ref | Action | Description |
|---|---|---|
CPN-2919 |
Added |
Search Reports Added page to search for reports. |
CPN-2919 |
Added |
Operational Reports Added page to view operational reports. |
CPN-2919 |
Added |
View Floorplans Added page to view, add, update floorplans for reporting views. |
NXT-27727 |
Added |
DPPC Across Worksheets New page added to view draft provider pricing clauses across worksheets |
NXT-27727 |
Modified |
DPPC Per Worksheet Advance search of DPPC (per worksheet) is enhanced and Copy Selected rows, Delete Selected rows feature is added |
NXT-28043 |
Modified |
Usages Page The advance search in the Usage page is extended with more attributes |
NXT-28070 |
Added |
Eligibility Checks A new JET UI page, "Eligibility Checks" has been added to search for and view the eligibility check details. |
NXT-29605 |
Added |
Episodes page Deeplink added to Claim code (applicable only to the Claims application) |
NXT-29605 |
Added |
Claims page Deeplink added to Authorization code and Reservation code at claimline tab (applicable only to the Claims application) |
NXT-30439 |
Modified |
Claims page Two actions added to Groups (Sub-Claims) page to Resolve Pends and Remove Messages |
NXT-30440 |
Modified |
Claims Page - Groups Tab The actions "Resolve Pends" and "Remove Message" have been added to the "More" dropdown under Group Tab - Table actions. |
NXT-30615 |
Modified |
Claims Page: Claim History Claim submit history is visible in the claim history section of the page |
NXT-30620 |
Modified |
Reference Sheet page Added "asOfDate" field in quick search to filter data between a start and end date |
NXT-30624 |
Added |
Queue Information page (Claims) New page added to view Queue Information |
NXT-30624 |
Added |
System Event Logs page New page added to view System Event Logs |
NXT-30624 |
Modified |
View Technical Errors page Page is enhanced to provide efficiency and simplifies troubleshooting |
POL-15307 |
Added |
FI0027 Accounting Details Added Accounting Details page as object navigation link in claims page (Claims application) and policies page (Policies application) |
POL-15307 |
Modified |
FI0014 Registrations Create, Update, Delete support is added in Registrations page (Policies application) |
POL-15307 |
Modified |
FI0027 Accounting Details Custom UI properties i.e. 'segmentsJET' and 'accountingAttributesJET' are introduced for the accounting details in claims page (Claims application) and policies page (Policies application) |
POL-16031 |
Added |
Macro Definitions New page added to create, update, delete Macro Definitions in Claims Application |
POL-16031 |
Modified |
Payment Registrations Registrations page renamed to Payments registrations to support create, update, delete Registration and also to start a macro and view macro history |
Breaking Changes
| Ref | Action | Description |
|---|---|---|
CPN-3076 |
Modified |
autopurgemetadata API The option to configure the retention period for PHI logs is removed. |
CPN-3076 |
Modified |
logphievents API PHI logs are retained in the database for 60 days, allowing customers to retrieve recent logs via the existing |
CPN-3218 |
Modified |
Groovy 4 upgrade Upgraded Groovy from 3.x to 4.0.24. |
NXT-27610 |
Removed |
Generic search api Existing GET calls if used would need to be changed to use the POST call instead. Workflows like external enrollment callout where GET is being used for the callout might need to be changed to use POST. |
NXT-29319 |
Modified |
Date format The APIs/IPs accept value for date fields in ISO 8601 format (YYYY-MM-DD), for example 2025-01-01. Any other formats result in an error. |
NXT-30624 |
Modified |
Error Messages The following error messages have been modified as follows,
Note: These message codes are used in Oracle Health Insurance Claims Adjudication. |
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
32477460 |
NXT-22010 |
Base views for reference sheet lines are not created |
|
Description: |
Base views for reference sheet lines are not created using base views generator. |
||
Resolution: |
Base views generator is updated to generate base views for reference sheet lines. |
||
34164741 |
NXT-24723 |
Outbound exchange attributes are not set |
|
Description: |
When trying to build a data set the attributes exactVersionMatch and disableDeleteByOmission are not getting updated. The attribute inclusionDate is not updated when passing an empty value. |
||
Resolution: |
The fields exactVersionMatch, disableDeleteByOmission and inclusionDate are now updated correctly when building a data set. |
||
Backports: |
4.24.1.0.3 |
||
34231559 |
NXT-24849 |
Financial transaction reversal not sent out with new version |
|
Description: |
The reversal financial transaction that is sent out and marked mandatory gets the bulking group of that sent out transaction. So when the next version of the transaction is selected, the previous reversal is not included. |
||
Resolution: |
The bulking group of the reversal selected is now copied from the next, non-superseded, non-reversed transaction in set. |
||
34270456 |
3-29505983391 |
NXT-24879 |
Claim start and end dates are not set |
Description: |
Claim start and end dates are not populated based on the claim line’s start and end dates |
||
Resolution: |
The claim start and end dates are now set according to specs |
||
Backports: |
3.22.1.0.6 |
||
36846356 |
3-37391765051 |
NXT-29905 |
Parameters are ignored when building CMT sets |
Description: |
When building a CMT Set with an Inclusion Date using Jet UI, the inclusion date does not get stored on the Outbound Data Set and does not get applied when building the CMT zip file |
||
Resolution: |
When using the Jet UI, users can mention the inclusion date when building the CMT Set and it gets stored and applied. |
||
Backports: |
4.24.1.0.3 |
||
37323901 |
NXT-30746 |
Checkbox is updatable at the view mode in claim events rule detail page |
|
Description: |
Go to claim event rules page. Search and view any of the claim event rule. "Applicable to sub-claims?" check-box is updatable even in the view mode of the page. |
||
Resolution: |
Checkbox is only editable in edit mode in claim events rule detail page |
||
37344756 |
3-35321985291 |
NXT-30783 |
All the 'fee schedule line import activity messages' are not visible on 'global activities' page |
Description: |
All the 'Fee Schedule Line Import activity messages' are not visible on 'Global Activities' page. The messages for the child activities are not displayed. |
||
Resolution: |
If activity has subactivities, multiple message tabs are displayed in UI. |
||
Backports: |
4.24.1.0.5 |
||
37387586 |
3-38835357681 |
NXT-30829 |
Manual benefits pop-up shows all the details including superseded values |
Description: |
Manual Benefits pop-up is supposed to show only the non-superseded details. View the claim and open manual benefits pop-up. It shows all the claim line rule coverage list. |
||
Resolution: |
Manual Benefits pop-up displays only the non-superseded details |
||
Backports: |
4.24.1.0.5 |
||
37408333 |
3-39029653111 |
NXT-30843 |
Referencesheet lines table page on select / deselect action of columns, previous data is not visible |
Description: |
In JET UI, in the referencesheet lines table page, when column preferences is selected or deselected table reloads and complete data is not visible |
||
Resolution: |
Table reload doesn’t happen when columns are selected/deselected from columns dropdown in Referencesheet lines page |
||
Backports: |
4.24.1.0.5 |
||
37610161 |
3-38056877861 |
NXT-31139 |
Default color is not working when flex code values are not mentioned in labels section for multivalue fields |
Description: |
Create a flexcode definition, configure it to claims page as a multivalue from usages page. Add this to floorplan as a label with displayLabel attribute. If the flexcode has 5 values, while configuring label values mention only 3. Now while configuring multivalue , select the field that is not mentioned in labels. None of the labels are coming on the claim |
||
Resolution: |
Default color is applied when flex code values are not mentioned in labels section for multivalue fields |
||
Backports: |
4.24.1.0.5 |
||
37703747 |
NXT-31217 |
Financial transaction detail Process Dats is not displayed when there is a space in query criteria |
|
Description: |
When there is a space in value of stampLevelCriteria, InvoiceBulkingCriteria etc in financial transaction detail process data, it results in error about unreserved string |
||
Resolution: |
Error is not shown when and financial transaction detail process data tab gets displayed properly even when there is a space in value of stampLevelCriteria, InvoiceBulkingCriteria etc |
||
37737600 |
NXT-31255 |
Claim Lines Search Page - Claim Line Summary section, pend reason details does not appear |
|
Description: |
For the claim lines, where claim line level pend reason is added, the summary section does not show up pend reason details |
||
Resolution: |
Pend reason details are displayed properly in Claim Line Summary section in ClaimLines page |
||
Backports: |
4.24.1.0.6 |
||
37751307 |
NXT-31296 |
Resolve pend reasons integration point stamps 'resolved by' user as internal system user |
|
Description: |
When a pend reason on a claim or claim line is resolved from claim lines page, the system records it as being resolved by an internal system user instead of the actual user who took the action. |
||
Resolution: |
The system now correctly records the actual user who resolved the pend on a claim or claim line, instead of the internal system user. |
||
Backports: |
4.24.1.0.6 |
||
36906213 |
3-37140647951 |
NXT-30029 |
Retrieval access restrictions Brand/Payer missing for CtrClaims and related entities. |
Description: |
Retrieval access restrictions for Brand/Payer are not present in generic API. When the brand/payer is restricted, a user can still get the CtrClaim and its related entities with the API. |
||
Resolution: |
Brand and payer access restriction have been added on retrieval of a ctrclaim and its related entities such as ctrclaimLine, ctrclaimmesssage, ctrclaimlinemessage, etc. Now these records will not be accessible through API without proper access roles granted to the user. |
||
Backports: |
4.23.2.0.4, 4.24.1.0.1, 4.23.1.0.10 |
||
36987784 |
NXT-30085 |
Inbound Benefits/Products(Http) : Console error on Download Response Files |
|
Description: |
When a user tries to download a response file on the Inbound Benefits/Products (Http) page, the download does not go through and results in a console error |
||
Resolution: |
The user must ensure the appropriate response file has been imported. The download now goes through and there is no console error. |
||
Backports: |
4.23.1.0.9, 4.23.2.0.3, 4.24.1.0.1 |
||
36988240 |
NXT-29776 |
Error on updating a dynamic field usage from single value non time-valid to multi value non time-valid |
|
Description: |
NPE error is thrown on updating a dynamic field usages from single value non time-valid to multi value non time-valid |
||
Resolution: |
Modified logic so that conversion of single-valued non time-valid field to multi-valued does not throw any NPE exception. |
||
Backports: |
4.24.1.0.5 |
||
36989174 |
NXT-29239 |
AutoFetch is not working in search pages with sort |
|
Description: |
The AutoFetch is not working when search pages have Sort configured |
||
Resolution: |
AutoFetch is now working in all pages where it is configured as true. |
||
37757258 |
NXT-31312 |
Users are able to edit the same claim at the same time |
|
Description: |
Two users are able to edit the same claim at the same time. System is not throwing an error message that claim is being edited by another user and cannot be saved |
||
Resolution: |
Error message is shown when same version of claim is locked and being edited by another user. This prevents overwriting of the updates made by another user. |
||
Backports: |
4.24.1.0.6 |
||
36967405 |
NXT-30183 |
ID of single-valued flex code is returned as "null" in the generic API response |
|
Description: |
ID of single-valued flex code is returned as "null" in the generic API response. |
||
Resolution: |
ID attribute of single value flex code is now excluded from the generic API response. |
||
Backports: |
4.23.2.0.3, 4.23.1.0.10, 4.24.1.0.1 |
||
36901735 |
OHISD-3644 |
NXT-30020 |
Unable to update widget descriptions |
Description: |
Unable to update the description for system specific widget entry. |
||
Resolution: |
The restriction to update the widget description is removed. |
||
36931468 |
3-37639583021 |
NXT-30096 |
Init conditions not working on initial page load in table |
Description: |
User have a condition that a field must be hidden while another field has no value. This condition is not being met when trying to enter the first record. Once user enter values to the field that has the condition, the condition then starts working when adding/modifying other records. |
||
Resolution: |
Init conditions works as expected on initial page load in table both for a new row added and while editing existing row |
||
Backports: |
4.24.1.0.1 |
||
36930505 |
3-37528423954 |
NXT-30091 |
Data points missing under claims pricing tab |
Description: |
Claims Pricing tab needs to be restructured with the following changes: Description to be added under set 1 of applied provider pricing clause tab. Deeplink needs to be enabled for Type field placed under title. Provider Pricing Clause should be displayed with deeplink enabled. |
||
Resolution: |
Claims Pricing tab is restructured to display more information and deeplinks |
||
Backports: |
4.23.2.0.3, 4.24.1.0.1, 4.23.1.0.10 |
||
36584465 |
3-36499732951 |
NXT-29313 |
Reservation line limit action not working |
Description: |
Action of limit is not getting applied for Claim Line Limit for Reservation claim when arg3 in predefined method claimLine.setClaimLineLimit is null. |
||
Resolution: |
If the reached action is null, then system will search if any non null value exist for reached action ( as per priority). If a Non null value exist then that will be used for limit action (as per priority). |
||
Backports: |
4.23.2.0.3, 4.24.1.0.1, 4.23.1.0.10 |
||
36531389 |
3-36392583761 |
NXT-29211 |
Pend resolution IP does not evaulate correct access restrictions |
Description: |
When a user invokes the pend resolution integration point, the application uses the internal system user to determine pend resolution access restrictions. This is not correct. |
||
Resolution: |
The user who triggered the pend resolution batch IP is now used to evaluate pend resolution access restrictions |
||
Backports: |
4.23.2.0.3, 4.23.1.0.10, 4.24.1.0.1 |
||
36477414 |
3-35321985291 |
NXT-29116 |
All Fee Shedule Line Import Activity messages are not visible on Global Activities page |
Description: |
All the Fee Schedule Line Import activity messages are not visible on Global Activities page. The messages for the child activities are not displayed. |
||
Resolution: |
The activity response now also returns links for the subactivity messages that were triggered while processing this activity. |
||
Backports: |
4.24.1.0.5 |
||
36641838 |
NXT-29407 |
Determining the Cover Withhold Category when RCL-PBSL-004 is being raised |
|
Description: |
When importing the generated product into Claims the message RCL-PBSL-004: All product benefit specification limits for the same cover withhold category must count either units, days or amounts is being raised multiple times. It takes quite a bit of time to figure which cover withhold category caused the trouble. |
||
Resolution: |
We have modified the message text for RCL-PBSL-004 to include the cover withhold category. The message now reads, "All product benefit specification limits for the same cover withhold category {0} must count either units, days or amounts." The placeholder will be populated with the cover withhold category code. |
||
36547585 |
NXT-29241 |
Predefined method getClaimLineWorkflowPendReasons returns lines without pends |
|
Description: |
In the predefined method getClaimLineWorkflowPendReasons keys are included for lines that do not have pend reasons, or lines that do not have pend reasons with indicator publish. Both are not expected |
||
Resolution: |
Keys for claim lines that do not have pend reasons, or lines that do not have pend reasons with indicator publish are not attached anymore. |
||
36329205 |
3-35746764831 |
NXT-28820 |
Error when updating a procedure via the integration point |
Description: |
The incorrect status is returned when updating a procedure through the integration point. |
||
Resolution: |
The status it is returning is expected, because the code which we use is always in UpperCase, so by passing code in uppercase should fix the issue |
||
36337417 |
NXT-28341 |
Conflicting keyboard shortcuts |
|
Description: |
Users can set up set a custom shortcuts using an existing key combination. This creates a conflict when the key combination is used. |
||
Resolution: |
A new business rule is introduced to ensure that all custom shortcuts have unique key combinations |
||
36943798 |
3-37656947111 |
NXT-30119 |
Flexcode field does not save null value when updated |
Description: |
When Empty/Null value is selected from flexcode dropdown and page is saved , the PATCH payload should have null value set for the flexcode field |
||
Resolution: |
Flexcode field values can be cleared and set to null value in JET UI page |
||
Backports: |
4.23.2.0.3, 4.24.1.0.1 |
||
36902074 |
3-37468227341 |
NXT-30022 |
Boilerplate translation not working |
Description: |
Translation is not working on the following pages: - Claims page, add card -code and description are not translated - Bookmarks, Alias & Remarks - Informative message - Claim History - Activities under the Operations menu |
||
Resolution: |
All mentioned fields are now translated correctly |
||
Backports: |
4.24.1.0.1 |
||
36977426 |
NXT-30198 |
Remove Copy from Global activities details page |
|
Description: |
Copy action should not be shown for view only details pages |
||
Resolution: |
Copy action is not shown for view only details pages |
||
Backports: |
4.24.1.0.1 |
||
36989134 |
NXT-30086 |
While updating derivation rule of level claim line, getting dynamic logic of level claim. |
|
Description: |
The filter of the dynamic logic is not correctly applied for all the rows in Derivation Rules page. |
||
Resolution: |
The filter of the dynamic logic is correctly applied based on the conditions for all the rows in Derivation Rules page. |
||
37004572 |
NXT-30233 |
Boilerplate text displays incorrectly on large claim page |
|
Description: |
Boilerplate issue at view activity page of large claim. |
||
Resolution: |
Labels are showing properly in View activity page of Large Claim. |
||
Backports: |
4.24.1.0.1 |
||
37030525 |
NXT-30277 |
Hovering on procedure does not bring up procedure popup tail on claim line for a finalized claim |
|
Description: |
Hovering on procedure does not bring up procedure description on claim line for a finalized claim.The popup tail is broken in 4.23.1, the module is not loaded properly. |
||
Resolution: |
Hovering on procedure brings up procedure popup tail on claim line for a finalized claim |
||
Backports: |
4.23.1.0.9 |
||
36967740 |
NXT-30186 |
Activities remain in QD status after OutOfMemoryProtector is triggered |
|
Description: |
After exceeding the critical memory threshold and having recovered the application memory, the queued activities are not dequeued and remain in QD status. |
||
Resolution: |
Once the application memory reaches normal state, the activities in QD status are re-queued to resume processing of the activities. |
||
36588981 |
NXT-29319 |
Number and Date incorrectly converted based on locale in API/IP requests |
|
Description: |
Dates are incorrectly converted based on the locale value in API/IP requests. |
||
Resolution: |
The date conversion no longer considers the locale value. |
||
37033042 |
NXT-30282 |
Auto Fill Start Date/End Date on the Claim Line from any of the Claim Level Date Fields doesn’t work in Edit Mode |
|
Description: |
When in edit mode, the fields in tab table list can be defaulted to parent context property like claim region. But these values are not getting picked in edit mode although it works fine in create mode. |
||
Resolution: |
Auto Fill Start Date/End Date on the Claim Line From Any of the Claim Level Date Fields works in Edit Mode |
||
Backports: |
4.24.1.0.2 |
||
37072210 |
3-37897137551 |
NXT-30332 |
Deny message with overturned set to NO not working as expected |
Description: |
Deny message with overturned set to NO not working as expected when attached from Waiting period regime |
||
Resolution: |
Logic to decide on when should claim line be denied did not consider non-overturned deny messages attached on a claim line from a waiting period regime. We have modified the logic to check for the message severity and the origin and perform the action accordingly. |
||
Backports: |
4.24.1.0.2 |
||
37106068 |
NXT-30422 |
Toggle once set "ON" does not remain in the same state upon page refresh or reload. |
|
Description: |
The claim page when toggled to be viewed in new view mode does not retain the state on reload or refresh of the page. |
||
Resolution: |
The claim page will retain the state of the new view toggle on refreshing or reloading the claim in the current browser session. |
||
Backports: |
4.24.1.0.2 |
||
37033213 |
NXT-30285 |
Additional flex code fields cannot be used in flex code conditional checks. |
|
Description: |
Additional flex code fields when used as a part of conditional checks does not work. |
||
Resolution: |
Additional flex code fields can be used as a part of conditional checks and other condition driven updates in edit mode. |
||
Backports: |
4.24.1.0.2 |
||
37201554 |
NXT-30560 |
Context value not adding default values for LOV fields |
|
Description: |
The LOV fields are not getting populated with default context values, but if we hard code as value, it is working |
||
Resolution: |
The LOV fields are getting populated with default context value conditions |
||
Backports: |
4.24.1.0.2 |
||
37173490 |
NXT-30463 |
Quantifier value is not displaying |
|
Description: |
When opening a finalized claim with a covered amount and navigating to the Pricing section under the 'Applied Provider Pricing Clause' tab, the Quantifier value is not displayed. |
||
Resolution: |
The Quantifier value is displayed correctly in the 'Applied Provider Pricing Clause' tab. |
||
Backports: |
4.24.1.0.2 |
||
37122708 |
:3-38125209661 |
NXT-30452 |
The spacing between the currency code and the amount field is missing when there is only a single currency |
Description: |
When there is only one currency in system, there is no space showing between the currency code and amount field |
||
Resolution: |
The spacing is present between the currency code and the amount field even when there is a single currency |
||
Backports: |
4.24.1.0.2 |
||
37021839 |
NXT-30274 |
Exchange rates incorrectly displayed |
|
Description: |
Navigate to Exchange rate page. Click on add and enter any number with decimal like 12.345 or 12.789. Value is getting rounded up and decimal is not shown. It is displayed as 12 and 13 after round off |
||
Resolution: |
Exchange Rate: Decimals are displayed exactly without being rounded off in rate field |
||
Backports: |
4.24.1.0.2 |
||
37045498 |
NXT-30293 |
Flex code sets cannot be selected as definition for procedures on the claim forms page |
|
Description: |
In the JET UI, on the claim forms page, it is not possible to select a flex code set, like the PROCEDURES flex code set as the definition for procedure1, procedure2 or procedure3. |
||
Resolution: |
It is now possible to display and allow the selection of flex code sets, such as PROCEDURES, on the claim forms page. |
||
37257355 |
NXT-30643 |
Sorting at tab table is not working |
|
Description: |
Create a Dynamic record. Add the record to tab table in floorplan. On Saving the data at tab table the records are not getting sorted as expected. |
||
Resolution: |
Sorting is now applied at tab table |
||
Backports: |
4.24.1.0.2 |
||
37118436 |
NXT-30442 |
Title is not coming in summary and detailed view of list view Tabs |
|
Description: |
Title property is not enhanced for the dynamic record when added as tab result. As well as in the title property of the corresponding detail page |
||
Resolution: |
Title property is now displayed for dynamic record when added as tab result |
||
Backports: |
4.24.1.0.2 |
||
36992916 |
NXT-30217 |
Missing details in claim line summary on claim lines search page |
|
Description: |
Missing details in claim line summary on claim lines search page |
||
Resolution: |
Fix added for missing details in Claim Lines Summary display. |
||
37306192 |
NXT-30723 |
In Individual Provider Page - Rendering Addresses tab, Service Address LOV field is not loading the values |
|
Description: |
On clicking Service Address LOV in Individual Providers page, an error appears on top of the page as well as in the console. And when any search criteria like '1%' is entered, its not loading the values |
||
Resolution: |
Service address values are displayed in service address dropdown |
||
Backports: |
4.24.1.0.3 |
||
37319375 |
NXT-30556 |
In claims page Benefit section is not loading any data |
|
Description: |
Navigate to claims page and fetch any of the claim which has limit consumption/benefit section data and click on benefits section. Data is not reflecting in benefits section |
||
Resolution: |
In claims page Benefit section, data is displayed properly |
||
Backports: |
4.24.1.0.3 |
||
37331782 |
3-38836924391 |
NXT-30767 |
Procedure group details does’t filter by flexcodedefinitioncode |
Description: |
When filter condition is applied on Flex code definition in advance search of procedure group details object navigation, the results are not returned. |
||
Resolution: |
The results are displayed for any filter condition applied on flex code definitions in procedure group details page |
||
37266871 |
NXT-30659 |
Unable to view new field added in user defined floorplan using number format type as 'Number', Integer', 'Formatted Integer' |
|
Description: |
While creating a usage of type 'field', if number format type is selected as 'Number', Integer', 'Formatted Integer', the field is not showing up on the respective page |
||
Resolution: |
The dynamic fields are working fine with all type of values in Number Format Type field on usage page. |
||
37105973 |
3-36396091781 |
NXT-30421 |
Claim fails with pricing mismatch when covered amount on claim and its lines are in different currencies |
Description: |
If a claim meets a benefit error during claims processing, system tries to clear previous results on claim lines. If given claim is not paid, total covered amount of claim is adjusted by considering claim lines. If claim’s currency is different from covered amount currencies on claim lines, claim’s total covered amount adjustment goes wrong. |
||
Resolution: |
During claim line cleanup, claim line which is having covered amount currency different as compared to claim’s covered amount currency is not considered for claim’s total covered amount adjustment. |
||
Backports: |
4.24.1.0.5, 4.23.1.0.10 |
||
37299771 |
3-38801531281 |
NXT-30711 |
Auto fill fields from claim to claim line in create/edit mode is not working. |
Description: |
Default values from the context of the claim is not being populated in claim line when driven by conditions. |
||
Resolution: |
Default values from the context of the claim is populated onto claim line fields through conditions. |
||
Backports: |
4.24.1.0.3 |
||
37274102 |
3-38590722441 |
NXT-30687 |
Flexcode status field in a dynamic record is toggling back and forth |
Description: |
When user sets a dynamic record in a tab as a list with details, the flex code value is set back to default, when he edits the page. |
||
Resolution: |
The flexcode value in dynamic record is not set back to default when user edits the record |
||
Backports: |
4.24.1.0.3 |
||
37294222 |
3-38464320061 |
NXT-30709 |
Custom LOV is not configurable for a primitive field |
Description: |
When a custom LOV is used as refType configuration for a primitive field, the page is not loading. |
||
Resolution: |
Custom LOV configuration can be done on a string field based on another resource |
||
Backports: |
4.24.1.0.3 |
||
37369631 |
3-38862064491 |
NXT-30808 |
Conditional readonly- false is opening the field as editable even in view mode |
Description: |
Make a field readonly:true/false based on a condition. It is noticed that when "readonly": false is set for a field, the field remains editable even in view mode. |
||
Resolution: |
Field is not editable in view mode when it is set as readonly through condition |
||
Backports: |
4.24.1.0.4 |
||
37302363 |
NXT-30713 |
DisplayLabel is not working when multivalue flex code fields are configured as labels |
|
Description: |
When multi-value flex code fields are configured as labels and "displayLabel" property is used in the configuration, the labels should display the value configured for "displayLabel" over the value property. |
||
Resolution: |
Multivalue fields can be configured as labels and displayLabel values are shown in UI |
||
Backports: |
4.24.1.0.3 |
||
37121395 |
3-38012093931 |
NXT-30450 |
Incorrect metadata for the Reference Sheet of a flex code set |
Description: |
The metadata for the reference sheet of a flex code set is inconsistent with the metadata from usages. The query parameter value is incorrect and should be similar to the usages metadata. |
||
Resolution: |
The metadata of a referencesheet with a flexcode set now contains the id of the containing flex code definitions instead of the id of the flexcode set itself. |
||
Backports: |
4.24.1.0.3 |
||
37356609 |
3-38861515651 |
NXT-30792 |
Conditional readonly setting is clearing the defaulted values |
Description: |
Dynamic record changes to make a field readonly/editable based on a condition. The default value added to that field "Status" is clearing off after "Save". |
||
Resolution: |
Conditional readonly setting is not clearing the default values |
||
Backports: |
4.24.1.0.4 |
||
37447017 |
NXT-30900 |
Value in flexcode field vanishes after saving on defaulting and with readonly as true |
|
Description: |
On any detail floorplan, if we default a flex Code and also used readOnly as true, but after saving the page record, the value of the flexCode is disappearing. So, the combination of readOnly and default properties is not working on flex code fields. |
||
Resolution: |
Value in flexcode field retains as is after saving on defaulting and with readonly as true |
||
Backports: |
4.24.1.0.4 |
||
37151567 |
NXT-30472 |
Internal system user is used for resolving the claim pends via pend resolution criteria IP |
|
Description: |
When pend reasons are resolved by the pendresolution criteria IP, internal system user is used for resolving the claim or claim line pends. Instead of this the current user should be used to resolve the pends via pend resolution criteria IP. |
||
Resolution: |
Instead of System User , the information of user who triggered the pend resolution criteria IP will now be used for resolving the pend. |
||
Backports: |
4.23.2.0.4, 4.24.1.0.4, 4.23.1.0.11 |
||
37331495 |
3-38866889371 |
NXT-30766 |
Access mapping missing for Inbound and Outbound Exchange Page |
Description: |
Access restriction mapping is missing for inbound and outbound exchange pages |
||
Resolution: |
The missing access restriction added as part of seed data for Inbound and Outbound Exchange Page |
||
37436505 |
3-38082342431 |
NXT-30869 |
Improve the Activity recovery query when node crashes |
Description: |
When a node is crashed, the other nodes try to recover the activities from the crashed node. During this recovery the select query on activities was too costly resulting in SQLException "Socket read interrupted" - i.e connection timeout. |
||
Resolution: |
The SELECT query was optimized, and the index on the activity table was updated to prevent a full table scan. This significantly reduced the recovery cost and effectively resolved the connection timeout issue. |
||
Backports: |
4.24.1.0.5, 4.23.1.0.11 |
||
36672936 |
3-37477788691 |
NXT-29480 |
When a flex code field is configured with reftype property which has propertyselection = true, lookup option does not appear |
Description: |
Create a flex code in claims page with flex code definition 'CPT_CODES'. Add the field to the claims custom floorplan. Load the claims page. The flex code field which has reftype: procedures is displayed on UI but look up option does not appear. |
||
Resolution: |
When a flex code field is configured with reftype property which has propertyselection = true, lookup option appears and dialog opens |
||
Backports: |
4.24.1.0.3 |
||
37552741 |
3-39589897271 |
NXT-31051 |
Processing of activities stuck with NPE on AggregateResumableActivityTask during node initialization |
Description: |
The Coherence service started processing activities too early, before the node was fully initialized, causing the ServiceLocator to initialize prematurely and resulting in a NullPointerException (NPE), which destabilized the entire application. |
||
Resolution: |
Delayed Coherence session creation until system initialization is complete, ensuring a stable environment for subsequent operations. |
||
Backports: |
4.24.1.0.5 |
||
37661111 |
3-39441721251 |
NXT-31167 |
Query to fetch user role history list for a user should be case insensitive |
Description: |
Query to fetch user role history list was performing a case sensitive match for the user login name, so when a new role was added/deleted for the user with a different case in login name, the said query could not retrieve the complete list from the database. |
||
Resolution: |
The query is fixed to perform a case insensitive match on the user login name. |
||
Backports: |
4.24.1.0.6, 4.23.1.0.11 |
||
37075408 |
3-37991339551 |
NXT-30358 |
Message RCL-CADE-002 shouldn’t be obsolete |
Description: |
Message RCL-CADE-002 is used in case definition validation. Currently it has been marked as obsolete. Obsolete messages aren’t shifted with product. Hence case definition validation can’t find this message. |
||
Resolution: |
Marked message as not obsolete. |
||
Backports: |
4.24.1.0.5 |
||
37069942 |
3-37991339551 |
NXT-30330 |
Case definition PATCH fails with message RCL-CADE-002 |
Description: |
While patching (with dynamic data) a case definition which has primary dynamic logic already set fails with message RCL-CADE-002. |
||
Resolution: |
Instead of considering dynamic logic ID in validation, considered dynamic logic entity reference itself. |
||
Backports: |
4.24.1.0.5 |
||
37397161 |
NXT-30834 |
Initialize the attributes for joining in the Authorization filter at startup and remove explicit calls |
|
Description: |
A GEN-PROC-ERR error intermittently occurs when accessing certain APIs. Once this error happens, all subsequent API calls to the same resource fail with the same error. The only workaround is to restart the specific node/JVM. To resolve such issues, modify the initialization of the attributes for joining in the Authorization filter so that it is invoked during startup, eliminating the need for explicit calls. |
||
Resolution: |
All the filters are initialized during the application start up or during the object creation so that no exception happens during the initialization process later. |
||
Backports: |
4.24.1.0.6 |
||
37843413 |
3-38685467541 |
NXT-31431 |
Restrict directly setting startDate and endDate on a Claim |
Description: |
The standard start/end date on the claim header are display-only fields, i.e., their values are automatically derived from the start and end dates on the claim lines and user should not be able to update these. |
||
Resolution: |
Users can no longer manually set the Start Date and End Date on a Claim. |
||
37554219 |
3-36700304951 |
NXT-31061 |
New nodes in the cluster remain unresponsive when added during ongoing application activities |
Description: |
Node startup fails due to a NullPointerException caused by premature invocation of ServiceLocator while loading ReferenceSheets objects |
||
Resolution: |
The NullPointerException was fixed by replacing ServiceLocator with required objects during node startup |
||
Backports: |
4.24.1.0.4 |
||
37251063 |
NXT-30632 |
Filter condition error when using wildcard |
|
Description: |
When wildcard % is configured in the context based filter value which evaluates to a value with space the query is included with extra quotes. |
||
Resolution: |
When % is configured in the context based filter value which evaluates to a value with space the query is constructed correctly. |
||
Backports: |
4.24.1.0.2 |
||
36206119 |
3-34786906091 |
NXT-28549 |
Thread code of CtrClaimEvent task not set correctly |
Description: |
For high priority claim,CtrClaimEvent task is initialized and submitted to WLS work manager. If WLS assigns a different thread, the thread code on CtrClaimEvent task is not overwritten. |
||
Resolution: |
The thread code and processing start date time is now updated by the current value of thread code and date time. |
||
37095711 |
3-38012093931 |
NXT-30402 |
Reference sheet line flex code menu not working |
Description: |
In JET UI, Reference Sheets page, when a record definition has the flex code set then lov shows "no record found" |
||
Resolution: |
LOV on Procedures configured as flexcode set displays proper values in Reference Sheets page |
||
Backports: |
4.24.1.0.4 |
||
37914266 |
3-40524754251 |
NXT-31550 |
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 |
||
Backports: |
4.24.1.0.7 |
||
37386898 |
NXT-30826 |
Flex Code Group Details Page - End date is missing in the table |
|
Description: |
Navigate to object navigation: "Flex Code Group Details" of Flex Code group page. In the table, only 2 fields - Start Date and Flex Code is displayed, end date is missing |
||
Resolution: |
End date field is added to Flex Code Group Details Page |
||
Backports: |
4.24.1.0.4 |
||
37110367 |
NXT-30433 |
Popuptail is displaying title as "Default" in all popups regardless of resource |
|
Description: |
PopupTail is displaying title as "Default" in all popups regardless of resource. "Default" is displayed for most popupTails but for certain resources from the JET code we display them as Procedures, Providers etc( ie ResourceName from a fixed list) |
||
Resolution: |
Popuptail displays the Title as per the resource name. |
||
Backports: |
4.23.2.0.4, 4.24.1.0.1, 4.23.1.0.10 |
||
35841806 |
NXT-27763 |
Exception when using the claim entry page |
|
Description: |
When checking the 'Benefits External?' checkbox in the UI when creating a version 2 of a claim, an exception is thrown |
||
Resolution: |
The conflict that caused the exception is resolved |
||
37003968 |
NXT-29773 |
Combination of quick search and advanced search isn’t working |
|
Description: |
When user does a search with some criteria in quick search & then add another criteria in advanced search, the quick search criteria is ignored and only advanced search criteria is considered but the advance search criteria should be in concatenation with quick search |
||
Resolution: |
When search is triggered with criteria in both quick search & advanced search, advance search criteria is concatenated with quick search. |
||
37004481 |
NXT-30052 |
Messages LOV doesn’t show data properly on add message pop-up |
|
Description: |
Messages LOV when selected occupies the entire page, hiding many fields. |
||
Resolution: |
Messages LOV display width is reduced and is now displayed similar to other LOVs. |
||
Backports: |
4.23.2.0.4, 4.24.1.0.1 |
||
37004593 |
NXT-30251 |
Linking Relation: A relation link is not deleted when a relation is deleted |
|
Description: |
When a relation link was deleted using the generic person API, the corresponding counterpart remains intact. |
||
Resolution: |
Deleting one of the relation links via the generic person API will now also remove its counterpart. |
||
Backports: |
4.24.1.0.2 |
||
37004581 |
NXT-30243 |
Submitting a group from the tab resolved the pends automatically |
|
Description: |
Currently, we are able to successfully process a subclaim which has unresolved pend reasons and subclaim is moving to Finalized status and large claim is in status In Process. We should not be processing subclaim which has unresolved pend reasons. |
||
Resolution: |
During submit, if there are any unresolved pend reasons on subclaim(s) then further processing of that subclaim will not happen and this results in large claim failure, indicating the unresolved pends. Failed activity can be restarted after resolving the pends |
||
Backports: |
4.24.1.0.1 |
||
37078784 |
3-37575252321 |
NXT-30366 |
Financial message generation fails with ora-06502: PL/SQL: numeric or value error: number precision too large |
Description: |
The financial message generate step is erroring out when the fin_base_financial_objects id is greater than 14 digits as the ohi_id_code_rec_tp still has id column definition as number ( 14,0) |
||
Resolution: |
The financial message generate step works when the fin_base_financial_objects id is greater than 14 digits and lessthan 19 digits |
||
Backports: |
4.23.2.0.3, 4.24.1.0.1, 4.23.1.0.10 |
||
37190541 |
NXT-30551 |
Auto Populate Is Not Working For New View Mode For Dynamic Tab Fields |
|
Description: |
Conditional setting of properties not working for dynamic record as a tab in new-view mode. |
||
Resolution: |
Conditional setting of properties works for a dynamic record which is configured as a tab in new-view mode. |
||
Backports: |
4.24.1.0.2 |
||
37202993 |
NXT-30563 |
User is able to create boolean type dynamic field usages |
|
Description: |
Boolean type is not supported for any dynamic field usages. POST /generic/fields API allows boolean type field creation. Due to this it can be linked to any dynamic field usages. |
||
Resolution: |
Prevented boolean type field creation |
||
Backports: |
4.24.1.0.2 |
||
37123150 |
NXT-30454 |
Filter condition with multiple contexts used is freezing the page. |
|
Description: |
Multiple context object when accessed in a single filter, the page becomes unresponsive. |
||
Resolution: |
Filter conditions with multiple context objects works without freezing the page. |
||
Backports: |
4.24.1.0.2 |
||
37094860 |
NXT-30397 |
Dynamic field usage condition is not being invoked on patch API call |
|
Description: |
Dynamic Field (flex code) Usage Condition is not being invoked on PATCH API call. Creation API invokes successfully the configured Dynamic Field Usage Condition and works as per expectation. |
||
Resolution: |
The Dynamic Logic mapped to Dynamic Field (flex code) Usage Condition is now invoked and shows the Message mapped on the Dynamic Logic on PATCH API call. |
||
Backports: |
4.24.1.0.2 |
||
37227993 |
NXT-30600 |
Unable to reprocess a claim using reprocess button. |
|
Description: |
Claims page is not refreshing after performing the reprocess action. |
||
Resolution: |
Claims page refreshes to show the updated data after performing the reprocess action. |
||
Backports: |
4.24.1.0.2 |
||
37142039 |
NXT-30464 |
While changing the version value from working copy to any other, getting boilerplate errors in dropdown values |
|
Description: |
Open any claim in Finalized status. Change the dropdown value from working copy to any other value. Click on dropdown again. Boilerplate errors coming in dropdown values |
||
Resolution: |
Boilerplates are not shown in Claims page version dropdown and proper values are shown now |
||
37020552 |
3-37883444451 |
NXT-30272 |
Referencesheet query API not working correctly |
Description: |
The referencesheet query API does not work according to specs for the operators gte and lte. |
||
Resolution: |
The referencesheet query API now interprets the operators gte and lte correctly. The data type inference logic was change from explicit casting to type inference from the record definition column. |
||
Backports: |
4.24.1.0.2 |
||
37072196 |
NXT-30331 |
Multivalue flexcodes are not working as labels |
|
Description: |
When user adds a multivalue flexcode in Labels section, it is listing blank occurrences instead of actual values |
||
Resolution: |
Multivalue fields can be configured as labels and actual values are shown |
||
Backports: |
4.24.1.0.2 |
||
37286533 |
NXT-30701 |
Derivation Rules - "Unsaved changes" pop up on search page |
|
Description: |
"Unsaved changes" popup appears on the Derivation Rules page after performing a '%' search, even though no changes have been made. |
||
Resolution: |
"Unsaved changes" popup doesn’t appear now, after performing a search without any modifications |
||
Backports: |
4.24.1.0.3 |
||
37331030 |
NXT-30763 |
Context value not adding default values for String fields on another resource |
|
Description: |
The LOV fields (string fields with reference to other resources ) are not getting populated with default context values, but if we hard code as value, it is working |
||
Resolution: |
String fields with reference to other resources are getting populated with default context value conditions |
||
Backports: |
4.24.1.0.3 |
||
37121445 |
3-38012093931 |
NXT-30451 |
Unable to fetch the flex code set in a record definition |
Description: |
The flex code set cannot be retrieved on a record definition. For example, in a flex code set with definitions x and y, when attempting to select the flex code definition on a record definition, the flex code set(s) do not appear. |
||
Resolution: |
In Create Record definition page, code definition flex code sets is shown in list |
||
Backports: |
4.24.1.0.3 |
||
36173196 |
NXT-26446 |
Deselection of claim lines is not working |
|
Description: |
When claimlines tab is configured as results, 'Select all' checkbox is not de-selecting the claimlines selected |
||
Resolution: |
The Select All option in the claim lines results tab is now working for both select and de-select |
||
Backports: |
4.24.1.0.6 |
||
37406946 |
3-38991321131 |
NXT-30840 |
Clicking on the “eye” of a products benefits specifications, no results appear |
Description: |
When clicking on the "eye" icon for a product’s benefit specifications, no results are displayed. |
||
Resolution: |
It is now possible to open and view product benefit specifications details page. |
||
Backports: |
4.24.1.0.4 |
||
37446716 |
NXT-30897 |
Multivalue field labels not display correctly |
|
Description: |
When user configures label for multivalue field which has displayLabel, it is showing boilerplate text “code” instead of the actual boilerplate text value |
||
Resolution: |
Boilerplate text values are shown while configuring labels for multivalue fields |
||
Backports: |
4.24.1.0.4 |
||
37393246 |
3-38974835961 |
NXT-30833 |
Overturned value, overturn action and severity label is not displayed |
Description: |
Overturned value is not displayed in the claim messages tab. Overturn action is not available for a claim in Manual Adjudication Status. Severity of the messages with value "Deny" does not have a label associated to it in the claim messages tab. |
||
Resolution: |
Overturned value, overturn action and severity label is displayed for a claim in Manual Adjudication Status |
||
Backports: |
4.24.1.0.5 |
||
37552063 |
NXT-31048 |
Error on create macro definition page |
|
Description: |
Create Macro definition page is not loading for second page. User has to do hard reload to create the record |
||
Resolution: |
"Create Macro Definition" page opens without issue for second time. |
||
Backports: |
4.24.1.0.5 |
||
37662226 |
NXT-31169 |
Reference sheet lines: Copy feature is missing |
|
Description: |
It is not possible to copy reference sheet lines. Copy functionality is missing and copy button is not visible in UI |
||
Resolution: |
Reference sheet lines table has the copy button enabled. |
||
37665674 |
NXT-31171 |
Activities are not purged when auto-purge job is enabled |
|
Description: |
Auto-purge job fails due to integrity constraint violation when child record is present in act_activity_dyn table |
||
Resolution: |
Changing the deletion order to delete child entries first before deleting act_activities entries resolved the issue. |
||
Backports: |
4.24.1.0.6, 4.23.1.0.11 |
||
37761336 |
NXT-31330 |
Mandatory fields validation not working in UI and doesn’t prevent user to click save |
|
Description: |
UI (client side) validation not working when a record is collapsed or new row is added without filling mandatory fields for previously added row when the page is in drill down view mode. Instead business error is shown for mandatory field |
||
Resolution: |
UI validation error is shown for mandatory fields when they are not filled in and subsequent new row is added in drill down view mode |
||
Backports: |
4.24.1.0.6 |
||
36997400 |
NXT-30229 |
Claim line drawer not displayed correctly |
|
Description: |
Click on More link in claimlines tab so that drawer opens with the details. It is seen that some of the sections are not displayed completely |
||
Resolution: |
Alignment issues are fixed in claimlines section More drawer and information is displayed completely |
||
Backports: |
4.24.1.0.1, 4.24.1.0.4 |
||
33430793 |
NXT-23460 |
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 |
||
Backports: |
4.24.1.0.7 |
||
37147332 |
NXT-30467 |
Search component improvements for Activity pages |
|
Description: |
Search experience has to be improved in Financial Transaction Set, Global Activities pages. Criteria mandatory must be applied for quick search and advance search must be extended with date fields |
||
Resolution: |
Financial Transaction Set, Global Activities pages are modified for quick search and advance search to enable better search experience |
||
37110221 |
3-37830283897 |
NXT-30429 |
Definition of flex codes under a dynamic record is not consisting of addtional fields |
Description: |
Definition of flex codes configured under a dynamic record does not contain additional fields (fields other than code and descriptor) |
||
Resolution: |
All fields configured on a flex code other than code and descriptor are available in the definition when the flex code is configured on a record definition |
||
Backports: |
4.24.1.0.2 |
||
37644790 |
NXT-31135 |
Zero is Not Allowed as Display Sequence for a Macro Parameter |
|
Description: |
The system previously allowed the display sequence of a macro parameter to be set to 0 within a macro definition. |
||
Resolution: |
Setting the display sequence to 0 for macro parameters in a macro definition is no longer allowed. |
||
37248614 |
NXT-30630 |
Error while uploading file in Inbound configuration migration |
|
Description: |
401 Unauthorized error is returned while uploading file in Inbound configuration migration |
||
Resolution: |
Able to upload file without any error in Inbound configuration page |
||
Backports: |
4.24.1.0.3, 4.23.1.0.10, 4.23.2.0.4 |
||
37235814 |
3-38352943611 |
NXT-30607 |
Limit consumptions do not appear if there are more than 50 records. |
Description: |
Only upto 50 limit consumptions can be displayed in the claims benefits tab. |
||
Resolution: |
All the limit consumptions on the claim are displayed. |
||
Backports: |
4.24.1.0.3, 4.23.2.0.4, 4.23.1.0.11 |
||
36844423 |
NXT-28272 |
Search results from Advanced Search are not retained after browser reload |
|
Description: |
Perform the search in any search page, open one of the search results. Come back to the floorplans page using breadcrumbs. The previously selected search criteria is not retained. |
||
Resolution: |
Search results from Advanced Search are retained after browser reload |
||
37258217 |
3-38669109641 |
NXT-30652 |
Suppress logging in UI claimLine message still appears in JET |
Description: |
User has a claimLine message configured with "Suppress Logging in UI" set to Yes. This message is still visible in JET. |
||
Resolution: |
ClaimLine messages configured with "Suppress Logging in UI" set to Yes is not displayed in JET UI |
||
Backports: |
4.24.1.0.3 |
||
37262983 |
3-38504308631 |
NXT-30654 |
Title of sub-section is showing and not hiding even after hiding all the property fields |
Description: |
The user has a use case to hide a set of fields from different sub-sections and also some of the sub-sections as a whole based on certain context conditions. Title of sub-section is showing and not hiding even after hiding all the property fields. |
||
Resolution: |
Title of sub-section is not shown after hiding all the property fields. |
||
Backports: |
4.24.1.0.3 |
||
37387077 |
NXT-30827 |
Authorization page does not show consumption |
|
Description: |
Authorization consumption is not loaded in the view authorization page |
||
Resolution: |
Authorization consumption are now displayed according to specifications |
||
Backports: |
4.24.1.0.4 |
||
37012690 |
NXT-27220 |
Import history is not displaying messages |
|
Description: |
After importing a file using the Inbound Benefits/Products (HTTP), no messages are shown in the import history (neither success nor failure messages). |
||
Resolution: |
Messages are displayed for both failed and success record |
||
Backports: |
4.24.1.0.4 |
||
37385464 |
3-38959466811 |
NXT-30823 |
Error when validating date dynamic fields |
Description: |
The system throws a data type validation error when the user defaults the field to SystemDateJET: GEN-HTTP-005: Value "2024-12-08T23:32:59.231-05:00" is not of type "Date" |
||
Resolution: |
The validation error is no longer raised |
||
Backports: |
4.24.1.0.4 |
||
37446780 |
NXT-30899 |
In Benefit Specification UI unable to save as "Y" using radio button for "Consume Auth" |
|
Description: |
In Claims component in Benefit Specification UI unable to save as "Y" for radio button of “Consume Auth?”. In Postman response Yes and No is displayed but UI does not save Consume Auth?” as Yes. |
||
Resolution: |
It is possible to save as "Y" using radio button for "Consume Auth" in Benefit Specifications |
||
37636120 |
3-39375247731 |
NXT-31150 |
Claim Lines page fails to load from Claims window when a condition is configured for Claim Lines floorplan. |
Description: |
When a floorplan condition is set on the Claim Lines floorplan for a referenced resource (e.g., context.claim.claimForm.code == 'FORM2'), along with the necessary tags for claim and claim line, the Claim Lines page fails to load even if the claim form matches. |
||
Resolution: |
Claim Line page loads when a condition is configured on the floorplan based on claim context |
||
Backports: |
4.24.1.0.5 |
||
37677684 |
NXT-31195 |
Claimline summary drawer shows blank in claimline results configuration |
|
Description: |
When claimline is configured as result, clicking on claimline summary action shows blank summary dialog. |
||
Resolution: |
While triggering claimline summary action from claim details page, claimline summary dialog loads with the required data. |
||
Backports: |
4.24.1.0.5 |
||
37842978 |
NXT-31424 |
Base View generation fails for an entity which has an apostrophy character in the display name |
|
Description: |
For entities which have dynamic attributes, base view generation adds column remark using display name. If display name has apostrophy character ('), it fails with following exception: java.sql.SQLSyntaxErrorException: ORA-00933: SQL command not properly ended |
||
Resolution: |
No SQL exception is thrown when a display name has apostrophy character (') |
||
37744370 |
NXT-28800 |
User defined message is not shown when regex validation happens |
|
Description: |
Users can configure a Floorplan property to add Message Code and that readable message should be displayed in UI when regex validation happens as error message |
||
Resolution: |
User defined message will be displayed when regex validation happens for String and Number field |
||
Backports: |
4.24.1.0.6 |
||
37744688 |
3-40137684801 |
NXT-31264 |
Claim Unfinalize Reasons: Default value set on the field or through conditional setting is not working |
Description: |
Default value on flexcode field (ex:unfinalizeDate) on unfinalize reason like "default": "${context.systemDateJET}" should set unfinalizeDate with system date. This is not working. |
||
Resolution: |
systemDateJET can be used in Claim Unfinalize Reasons dialog to set default value |
||
Backports: |
4.24.1.0.6 |
||
37749676 |
NXT-31281 |
Single value non-time valid dynamic records cannot be cleared/deleted |
|
Description: |
It is not possible to clear all the values in Single value non-time valid dynamic record |
||
Resolution: |
'Clear All' action is made available on Single value non-time valid dynamic records to clear all the values in record |
||
Backports: |
4.24.1.0.6 |
||
37804796 |
NXT-31378 |
User information is not available as a parameter in deepLink (external URL) |
|
Description: |
An external link created with param to display logged in user information doesn’t gets replaced by user’s displayName |
||
Resolution: |
Logged in user information can be used as param in external Links in JET UI |
||
Backports: |
4.24.1.0.6 |
||
37779655 |
3-40014494281 |
NXT-31349 |
Claimline status value is different in claimLine Tab of Claim details page and claimline details page |
Description: |
Consider a claim in 'Manual Adjudication' status with multiple claimlines in 'To Be Approved' / 'To Be Denied' status. Claimline status value is different in results tab of claim details page and on claimline details page |
||
Resolution: |
Claimline status value is displayed consistently in claimLine results tab of Claim details page and when claimline details page is opened |
||
Backports: |
4.24.1.0.6 |
||
35686780 |
NXT-27433 |
Dynamic logic unit test statistics are incorrect |
|
Description: |
When the user queries something in the testunit dynamic logic and then tests another dynamic logic in the same testunit dynamic logic, the value/count for all query parameters displays incorrect |
||
Resolution: |
The reset method in the QueryStatisticsService is called for each dynamic logic because of which the statistics are cleared by the second dynamic logic. We need to ensure the reset method is called only once for every test unit call |
||
Issues that were backported in previous Release / Patch
| BugDB | Internal | Summary | Backport | BugDB | SR |
|---|---|---|---|---|---|
33430793 |
NXT-23460 |
Dynamic fields in multiple floorplan sets are displaying incorrectly |
4.24.1.0.7 |
37681681 |
|
34164741 |
NXT-24723 |
Outbound exchange attributes are not set |
4.24.1.0.3 |
37303050 |
|
34270456 |
NXT-24879 |
Claim start and end dates are not set |
3.22.1.0.6 |
34714036 |
3-29505983391,3-30769733971 |
36173196 |
NXT-26446 |
Deselection of claim lines is not working |
4.24.1.0.6 |
37838432 |
|
37012690 |
NXT-27220 |
Import history is not displaying messages |
4.24.1.0.4 |
37012707 |
|
37744370 |
NXT-28800 |
User defined message is not shown when regex validation happens |
4.24.1.0.6 |
37765155 |
|
36477414 |
NXT-29116 |
All Fee Shedule Line Import Activity messages are not visible on Global Activities page |
4.24.1.0.5 |
36993989 |
3-35321985291 |
36531389 |
NXT-29211 |
Pend resolution IP does not evaulate correct access restrictions |
4.23.2.0.3 |
36531393 |
3-36392583761 |
36531389 |
NXT-29211 |
Pend resolution IP does not evaulate correct access restrictions |
4.23.1.0.10 |
36531397 |
3-36392583761 |
36531389 |
NXT-29211 |
Pend resolution IP does not evaulate correct access restrictions |
4.24.1.0.1 |
36993984 |
3-36392583761 |
36584465 |
NXT-29313 |
Reservation line limit action not working |
4.23.2.0.3 |
36584497 |
3-36499732951 |
36584465 |
NXT-29313 |
Reservation line limit action not working |
4.24.1.0.1 |
36993980 |
3-36499732951 |
36584465 |
NXT-29313 |
Reservation line limit action not working |
4.23.1.0.10 |
36584496 |
3-36499732951 |
36672936 |
NXT-29480 |
When a flex code field is configured with reftype property which has propertyselection = true, lookup option does not appear |
4.24.1.0.3 |
36946552 |
3-37477788691 |
36988240 |
NXT-29776 |
Error on updating a dynamic field usage from single value non time-valid to multi value non time-valid |
4.24.1.0.5 |
36988242 |
|
36846356 |
NXT-29905 |
Parameters are ignored when building CMT sets |
4.24.1.0.3 |
36946520 |
3-37391765051 |
36902074 |
NXT-30022 |
Boilerplate translation not working |
4.24.1.0.1 |
36946565 |
3-37468227341 |
36906213 |
NXT-30029 |
Retrieval access restrictions Brand/Payer missing for CtrClaims and related entities. |
4.23.2.0.4 |
37014448 |
3-37140647951 |
36906213 |
NXT-30029 |
Retrieval access restrictions Brand/Payer missing for CtrClaims and related entities. |
4.24.1.0.1 |
37014435 |
3-37140647951 |
36906213 |
NXT-30029 |
Retrieval access restrictions Brand/Payer missing for CtrClaims and related entities. |
4.23.1.0.10 |
37014450 |
3-37140647951 |
37004481 |
NXT-30052 |
Messages LOV doesn’t show data properly on add message pop-up |
4.23.2.0.4 |
37015993 |
|
37004481 |
NXT-30052 |
Messages LOV doesn’t show data properly on add message pop-up |
4.24.1.0.1 |
37015988 |
|
36987784 |
NXT-30085 |
Inbound Benefits/Products(Http) : Console error on Download Response Files |
4.23.1.0.9 |
37056643 |
|
36987784 |
NXT-30085 |
Inbound Benefits/Products(Http) : Console error on Download Response Files |
4.23.2.0.3 |
37078595 |
|
36987784 |
NXT-30085 |
Inbound Benefits/Products(Http) : Console error on Download Response Files |
4.24.1.0.1 |
36987811 |
|
36930505 |
NXT-30091 |
Data points missing under claims pricing tab |
4.23.2.0.3 |
36930567 |
3-37528423954 |
36930505 |
NXT-30091 |
Data points missing under claims pricing tab |
4.24.1.0.1 |
36962127 |
3-37528423954 |
36930505 |
NXT-30091 |
Data points missing under claims pricing tab |
4.23.1.0.10 |
36930591 |
3-37528423954 |
36931468 |
NXT-30096 |
Init conditions not working on initial page load in table |
4.24.1.0.1 |
36946559 |
3-37639583021 |
36943798 |
NXT-30119 |
Flexcode field does not save null value when updated |
4.23.2.0.3 |
36943895 |
3-37656947111 |
36943798 |
NXT-30119 |
Flexcode field does not save null value when updated |
4.24.1.0.1 |
36962412 |
3-37656947111 |
36967405 |
NXT-30183 |
ID of single-valued flex code is returned as "null" in the generic API response |
4.23.2.0.3 |
36967427 |
|
36967405 |
NXT-30183 |
ID of single-valued flex code is returned as "null" in the generic API response |
4.23.1.0.10 |
36967429 |
|
36967405 |
NXT-30183 |
ID of single-valued flex code is returned as "null" in the generic API response |
4.24.1.0.1 |
37052626 |
|
36977426 |
NXT-30198 |
Remove Copy from Global activities details page |
4.24.1.0.1 |
36977435 |
|
36997400 |
NXT-30229 |
Claim line drawer not displayed correctly |
4.24.1.0.1 |
36997405 |
|
36997400 |
NXT-30229 |
Claim line drawer not displayed correctly |
4.24.1.0.4 |
36997405 |
|
37004572 |
NXT-30233 |
Boilerplate text displays incorrectly on large claim page |
4.24.1.0.1 |
37004575 |
|
37004581 |
NXT-30243 |
Submitting a group from the tab resolved the pends automatically |
4.24.1.0.1 |
37004585 |
|
37004593 |
NXT-30251 |
Linking Relation: A relation link is not deleted when a relation is deleted |
4.24.1.0.2 |
37004602 |
|
37020552 |
NXT-30272 |
Referencesheet query API not working correctly |
4.24.1.0.2 |
37020553 |
3-37883444451 |
37021839 |
NXT-30274 |
Exchange rates incorrectly displayed |
4.24.1.0.2 |
37021861 |
|
37030525 |
NXT-30277 |
Hovering on procedure does not bring up procedure popup tail on claim line for a finalized claim |
4.23.1.0.9 |
37030529 |
3-37895611261 |
37033042 |
NXT-30282 |
Auto Fill Start Date/End Date on the Claim Line from any of the Claim Level Date Fields doesn’t work in Edit Mode |
4.24.1.0.2 |
37033057 |
|
37033213 |
NXT-30285 |
Additional flex code fields cannot be used in flex code conditional checks. |
4.24.1.0.2 |
37033230 |
|
37069942 |
NXT-30330 |
Case definition PATCH fails with message RCL-CADE-002 |
4.24.1.0.5 |
37075387 |
3-37991339551 |
37072196 |
NXT-30331 |
Multivalue flexcodes are not working as labels |
4.24.1.0.2 |
37088668 |
|
37072210 |
NXT-30332 |
Deny message with overturned set to NO not working as expected |
4.24.1.0.2 |
37072217 |
3-37897137551 |
37075408 |
NXT-30358 |
Message RCL-CADE-002 shouldn’t be obsolete |
4.24.1.0.5 |
37196914 |
3-37991339551 |
37078784 |
NXT-30366 |
Financial message generation fails with ora-06502: PL/SQL: numeric or value error: number precision too large |
4.23.2.0.3 |
36911451 |
3-37575252321 |
37078784 |
NXT-30366 |
Financial message generation fails with ora-06502: PL/SQL: numeric or value error: number precision too large |
4.24.1.0.1 |
36926778 |
3-37575252321 |
37078784 |
NXT-30366 |
Financial message generation fails with ora-06502: PL/SQL: numeric or value error: number precision too large |
4.23.1.0.10 |
36911468 |
3-37575252321 |
37094860 |
NXT-30397 |
Dynamic field usage condition is not being invoked on patch API call |
4.24.1.0.2 |
37162813 |
|
37095711 |
NXT-30402 |
Reference sheet line flex code menu not working |
4.24.1.0.4 |
37095725 |
3-38012093931 |
37105973 |
NXT-30421 |
Claim fails with pricing mismatch when covered amount on claim and its lines are in different currencies |
4.24.1.0.5 |
37188392 |
3-36396091781 |
37105973 |
NXT-30421 |
Claim fails with pricing mismatch when covered amount on claim and its lines are in different currencies |
4.23.1.0.10 |
37183340 |
3-36396091781 |
37106068 |
NXT-30422 |
Toggle once set "ON" does not remain in the same state upon page refresh or reload. |
4.24.1.0.2 |
37167370 |
|
37110221 |
NXT-30429 |
Definition of flex codes under a dynamic record is not consisting of addtional fields |
4.24.1.0.2 |
37110332 |
3-37830283897 |
37110367 |
NXT-30433 |
Popuptail is displaying title as "Default" in all popups regardless of resource |
4.23.2.0.4 |
37110398 |
|
37110367 |
NXT-30433 |
Popuptail is displaying title as "Default" in all popups regardless of resource |
4.24.1.0.1 |
37110389 |
|
37110367 |
NXT-30433 |
Popuptail is displaying title as "Default" in all popups regardless of resource |
4.23.1.0.10 |
37110410 |
|
37118436 |
NXT-30442 |
Title is not coming in summary and detailed view of list view Tabs |
4.24.1.0.2 |
37153174 |
|
37121395 |
NXT-30450 |
Incorrect metadata for the Reference Sheet of a flex code set |
4.24.1.0.3 |
37343169 |
3-38012093931 |
37121445 |
NXT-30451 |
Unable to fetch the flex code set in a record definition |
4.24.1.0.3 |
37381267 |
3-38012093931 |
37122708 |
NXT-30452 |
The spacing between the currency code and the amount field is missing when there is only a single currency |
4.24.1.0.2 |
37122728 |
:3-38125209661 |
37123150 |
NXT-30454 |
Filter condition with multiple contexts used is freezing the page. |
4.24.1.0.2 |
37151818 |
3-38218061471 |
37173490 |
NXT-30463 |
Quantifier value is not displaying |
4.24.1.0.2 |
37173496 |
|
37151567 |
NXT-30472 |
Internal system user is used for resolving the claim pends via pend resolution criteria IP |
4.23.2.0.4 |
37151579 |
|
37151567 |
NXT-30472 |
Internal system user is used for resolving the claim pends via pend resolution criteria IP |
4.24.1.0.4 |
37151575 |
|
37151567 |
NXT-30472 |
Internal system user is used for resolving the claim pends via pend resolution criteria IP |
4.23.1.0.11 |
37151585 |
|
37190541 |
NXT-30551 |
Auto Populate Is Not Working For New View Mode For Dynamic Tab Fields |
4.24.1.0.2 |
37196935 |
|
37319375 |
NXT-30556 |
In claims page Benefit section is not loading any data |
4.24.1.0.3 |
37319369 |
|
37201554 |
NXT-30560 |
Context value not adding default values for LOV fields |
4.24.1.0.2 |
37201571 |
|
37202993 |
NXT-30563 |
User is able to create boolean type dynamic field usages |
4.24.1.0.2 |
37203141 |
3-38478259058 |
37227993 |
NXT-30600 |
Unable to reprocess a claim using reprocess button. |
4.24.1.0.2 |
37228013 |
|
37235814 |
NXT-30607 |
Limit consumptions do not appear if there are more than 50 records. |
4.24.1.0.3 |
37235823 |
3-38352943611 |
37235814 |
NXT-30607 |
Limit consumptions do not appear if there are more than 50 records. |
4.23.2.0.4 |
37235834 |
3-38352943611 |
37235814 |
NXT-30607 |
Limit consumptions do not appear if there are more than 50 records. |
4.23.1.0.11 |
37235842 |
3-38352943611 |
37248614 |
NXT-30630 |
Error while uploading file in Inbound configuration migration |
4.24.1.0.3 |
37248611 |
|
37248614 |
NXT-30630 |
Error while uploading file in Inbound configuration migration |
4.23.1.0.10 |
37248605 |
|
37248614 |
NXT-30630 |
Error while uploading file in Inbound configuration migration |
4.23.2.0.4 |
37248618 |
|
37251063 |
NXT-30632 |
Filter condition error when using wildcard |
4.24.1.0.2 |
37251078 |
|
37257355 |
NXT-30643 |
Sorting at tab table is not working |
4.24.1.0.2 |
37257360 |
|
37258217 |
NXT-30652 |
Suppress logging in UI claimLine message still appears in JET |
4.24.1.0.3 |
37287766 |
3-38669109641 |
37262983 |
NXT-30654 |
Title of sub-section is showing and not hiding even after hiding all the property fields |
4.24.1.0.3 |
37266894 |
3-38504308631 |
37274102 |
NXT-30687 |
Flexcode status field in a dynamic record is toggling back and forth |
4.24.1.0.3 |
37274112 |
3-38590722441 |
37286533 |
NXT-30701 |
Derivation Rules - "Unsaved changes" pop up on search page |
4.24.1.0.3 |
37286449 |
|
37294222 |
NXT-30709 |
Custom LOV is not configurable for a primitive field |
4.24.1.0.3 |
37294268 |
3-38464320061 |
37299771 |
NXT-30711 |
Auto fill fields from claim to claim line in create/edit mode is not working. |
4.24.1.0.3 |
37299816 |
3-38801531281 |
37302363 |
NXT-30713 |
DisplayLabel is not working when multivalue flex code fields are configured as labels |
4.24.1.0.3 |
37302369 |
|
37306192 |
NXT-30723 |
In Individual Provider Page - Rendering Addresses tab, Service Address LOV field is not loading the values |
4.24.1.0.3 |
37309921 |
|
37331030 |
NXT-30763 |
Context value not adding default values for String fields on another resource |
4.24.1.0.3 |
37331047 |
|
37344756 |
NXT-30783 |
All the 'fee schedule line import activity messages' are not visible on 'global activities' page |
4.24.1.0.5 |
37657244 |
3-35321985291 |
37356609 |
NXT-30792 |
Conditional readonly setting is clearing the defaulted values |
4.24.1.0.4 |
37356754 |
3-38861515651 |
37369631 |
NXT-30808 |
Conditional readonly- false is opening the field as editable even in view mode |
4.24.1.0.4 |
37371167 |
3-38862064491 |
37385464 |
NXT-30823 |
Error when validating date dynamic fields |
4.24.1.0.4 |
37385469 |
3-38959466811 |
37386898 |
NXT-30826 |
Flex Code Group Details Page - End date is missing in the table |
4.24.1.0.4 |
37391824 |
|
37387077 |
NXT-30827 |
Authorization page does not show consumption |
4.24.1.0.4 |
37387101 |
|
37387586 |
NXT-30829 |
Manual benefits pop-up shows all the details including superseded values |
4.24.1.0.5 |
37436848 |
3-38835357681 |
37393246 |
NXT-30833 |
Overturned value, overturn action and severity label is not displayed |
4.24.1.0.5 |
37434653 |
3-38974835961 |
37397161 |
NXT-30834 |
Initialize the attributes for joining in the Authorization filter at startup and remove explicit calls |
4.24.1.0.6 |
37397503 |
|
37406946 |
NXT-30840 |
Clicking on the “eye” of a products benefits specifications, no results appear |
4.24.1.0.4 |
37406960 |
3-38991321131 |
37408333 |
NXT-30843 |
Referencesheet lines table page on select / deselect action of columns, previous data is not visible |
4.24.1.0.5 |
37413415 |
3-39029653111 |
37436505 |
NXT-30869 |
Improve the Activity recovery query when node crashes |
4.24.1.0.5 |
37436516 |
3-38082342431 |
37436505 |
NXT-30869 |
Improve the Activity recovery query when node crashes |
4.23.1.0.11 |
37436525 |
3-38082342431 |
37446716 |
NXT-30897 |
Multivalue field labels not display correctly |
4.24.1.0.4 |
37446723 |
|
37447017 |
NXT-30900 |
Value in flexcode field vanishes after saving on defaulting and with readonly as true |
4.24.1.0.4 |
37447203 |
|
37552063 |
NXT-31048 |
Error on create macro definition page |
4.24.1.0.5 |
37552077 |
|
37552741 |
NXT-31051 |
Processing of activities stuck with NPE on AggregateResumableActivityTask during node initialization |
4.24.1.0.5 |
37552774 |
3-39589897271 |
37554219 |
NXT-31061 |
New nodes in the cluster remain unresponsive when added during ongoing application activities |
4.24.1.0.4 |
37554246 |
3-36700304951 |
37610161 |
NXT-31139 |
Default color is not working when flex code values are not mentioned in labels section for multivalue fields |
4.24.1.0.5 |
37610167 |
3-38056877861 |
37636120 |
NXT-31150 |
Claim Lines page fails to load from Claims window when a condition is configured for Claim Lines floorplan. |
4.24.1.0.5 |
37644169 |
3-39375247731 |
37661111 |
NXT-31167 |
Query to fetch user role history list for a user should be case insensitive |
4.24.1.0.6 |
37761338 |
3-39441721251 |
37661111 |
NXT-31167 |
Query to fetch user role history list for a user should be case insensitive |
4.23.1.0.11 |
37761311 |
3-39441721251 |
37665674 |
NXT-31171 |
Activities are not purged when auto-purge job is enabled |
4.24.1.0.6 |
37665679 |
|
37665674 |
NXT-31171 |
Activities are not purged when auto-purge job is enabled |
4.23.1.0.11 |
37665685 |
|
37677684 |
NXT-31195 |
Claimline summary drawer shows blank in claimline results configuration |
4.24.1.0.5 |
37677689 |
|
37737600 |
NXT-31255 |
Claim Lines Search Page - Claim Line Summary section, pend reason details does not appear |
4.24.1.0.6 |
37751467 |
|
37744688 |
NXT-31264 |
Claim Unfinalize Reasons: Default value set on the field or through conditional setting is not working |
4.24.1.0.6 |
37744755 |
3-40137684801 |
37749676 |
NXT-31281 |
Single value non-time valid dynamic records cannot be cleared/deleted |
4.24.1.0.6 |
37812748 |
|
37751307 |
NXT-31296 |
Resolve pend reasons integration point stamps 'resolved by' user as internal system user |
4.24.1.0.6 |
37751312 |
|
37757258 |
NXT-31312 |
Users are able to edit the same claim at the same time |
4.24.1.0.6 |
37757276 |
|
37761336 |
NXT-31330 |
Mandatory fields validation not working in UI and doesn’t prevent user to click save |
4.24.1.0.6 |
37764969 |
|
37779655 |
NXT-31349 |
Claimline status value is different in claimLine Tab of Claim details page and claimline details page |
4.24.1.0.6 |
37779677 |
3-40014494281 |
37804796 |
NXT-31378 |
User information is not available as a parameter in deepLink (external URL) |
4.24.1.0.6 |
37805248 |
|
37914266 |
NXT-31550 |
Download icon is missing for limit consumptions in adjudication limit counters page |
4.24.1.0.7 |
37881462 |
3-40524754251 |
Known Issues
| BugDB | SR | Internal | Summary |
|---|---|---|---|
- |
NXT-15947 |
Uppercase code not implemented in HTTP API |
|
Description: |
The generic API is not applying the uppercase function to 'code' attributes. As a result it is possible to create mixed case codes, which is not according to specs. |
||
32945627 |
NXT-22704 |
SetRecalculateBenefits function fails intermittently |
|
Description: |
After setting the amount on a 'claimLineRuleCoverage' using the 'setAmountManually' method, the amount is set to the desired value. However, after recalculating the benefits, the amount (cover label) on the 'claimLineCoverage' is not aligned with the override. This issue occurs intermittently. |
||
36418631 |
NXT-23558 |
In table-region component setting up properties as notNull isn’t working properly when used in widgets |
|
Description: |
There is a blank space where notNull was used on a property. Whenever we use notNull it shouldn’t take up that space and the next property should move up |
||
33698723 |
NXT-24018 |
Failed match of dynamic records during replication not detected |
|
Description: |
If there is a mismatch in dynamic records, the replication activity should fail with an error, but in this case, the activity was completed with "CO" status. Only the log file contained the error. |
||
34189805 |
NXT-24484 |
Combined filter condition not working |
|
Description: |
The query 'claimPendReasonList.pendReason.code.eq('MEDICAL').or.claimLineList.claimLinePendReasonList.pendReason.code.eq('MEDICAL')' does not return the correct search results. It returns only claims that have pend reasons at both levels (claim & claim line). |
||
34169837 |
NXT-24731 |
Execution of callout rule dynamic logic fails from test unit |
|
Description: |
For callout rule dynamic logic, the endpoint placeholder is set on callout rule code and not dynamic logic code (ohi.{0}.endpoint.request); this leads to an execution error in a unit test. |
||
34445139 |
3-30161147631 |
NXT-25161 |
Test unit signature applies incorrect restrictions |
Description: |
In the DYLO test unit signature, few restrictions are there to set values for an object. It should be possible to define any object in any given state as input under the test unit. |
||
34456508 |
3-30172109281 |
NXT-25191 |
It should not be possible to add pend reasons to a claim or claim line at entry state |
Description: |
Claims are having the option to add pend reason to a claim or claim at ENTRY state. This should not be allowed. |
||
36337409 |
NXT-25288 |
API metadata does not show which dynamic record fields are required |
|
Description: |
The metadata API does not show which dynamic record fields are configured as mandatory |
||
34875997 |
NXT-25987 |
Episode inclusion rules not working according to specs |
|
Description: |
When a claim line with null episode identifier hits an episode inclusion rule, it does not evaluate all episodes in the event that there is more than one and they overlap during the service date of the claim line |
||
34938143 |
3-31591920981 |
NXT-26091 |
Incorrect response when alias 'D' is used for claimDiagnosis.diagnosis in accept header |
Description: |
When accepting the header for claims, the API has aliases with alias d for |
||
35000725 |
3-31898611651 |
NXT-26257 |
Not possible to update multi-value flexcodes with the feeschedule integration point |
Description: |
When a multi-value flexcode is added to the feeScheduleLine via the feeSchedule integration point, the line is not updated. |
||
35018330 |
3-31969350441 |
NXT-26277 |
Query API returns incorrect results for combined conditions |
Description: |
When you do a query search with a combination of a null, for instance (multicore.eq('Y').or.multicore.eq(null)), the result shows the records having value Y and not the ones with a null value. |
||
36423204 |
NXT-26342 |
Unabe to update pricing worksheet code and description |
|
Description: |
In the API an error is thrown when updating the code. In the user interface an error is thrown only when both code and description are changed. |
||
35056041 |
NXT-26369 |
Exception on brand mismatch between claim and member’s product |
|
Description: |
When a claim is sent in via IP and enrollment, the response returns a product that belongs to another brand than what is specified in the claim request; an NPE is returned instead of an error. |
||
35059098 |
3-31234252921 |
NXT-26375 |
Fee schedule line condition applies incorrect restriction |
Description: |
FeeScheduleline dynamic fields are currently not accepted by fee schedule line condition dynamic logic. |
||
35242524 |
NXT-26709 |
Episode start date dynamic logic is not working according to specs |
|
Description: |
A triggeringClaimLine in Episode Start Date dynamic logic works as triggering or include line. |
||
35262820 |
NXT-26745 |
Counter period not always created for calendar year external limit consumptions |
|
Description: |
Counter period not always created for calendar year external limit consumption. |
||
35263469 |
NXT-26749 |
Carry-over counter period not created for insurance limits |
|
Description: |
A carry-over counter period is not created for Insurance limits that count per product per provider. |
||
35750879 |
NXT-26852 |
Adjudication case consumptions are not counted towards carry over counter periods |
|
Description: |
Adjudication case consumptions are not counted towards carry-over counter periods. |
||
35340860 |
NXT-26860 |
External consumptions are not updating counter periods |
|
Description: |
When external consumptions with an unspecified provider or aggregation level are added to a counter, they do not count towards existing counter periods that count per provider or product. |
||
36989357 |
NXT-26876 |
Widgets : When context.<referenceproperty> is null, the widgets keeps spinning |
|
Description: |
When context.<referenceproperty> is null, the widgets keeps spinning with console error is shown |
||
35409222 |
3-31969350441 |
NXT-26979 |
Limit counters search returns incorrect results |
Description: |
A search on limit counters does not include family counters if the request has an 'OR' condition on the insurable entity |
||
35439093 |
NXT-27031 |
Default Search on the basis of dates, location provider and Service provider does not work in Claims page |
|
Description: |
In floorplan configuring default sort order as "asc" for parameters receiptDate, locationProvider, serviceProvider. doesn’t show the results as expected. |
||
35675158 |
NXT-27060 |
Widget title not loading for context based widget when we close and add again |
|
Description: |
Navigate to the page of context based widgets. Click on add card. Add any context based widget, wait for it to load. Once loaded, close the widget and click on add card. Add the same widget again. The widget title/header is not displayed |
||
35471119 |
3-33156986581 |
NXT-27076 |
Target events not periodically committed |
Description: |
The commit of the events happen at the end of the activity (main transaction), even though the propagation (transaction boundary) is set as REQUIRES_NEW on the processor. This gives the false impression to the user that the events are still not processed or running infinitely. |
||
34871682 |
NXT-27278 |
Auto Include Extensibility Error Handling |
|
Description: |
When there is an error in any multivalue dynamic field or dynamic record, the error path does not indicate the particular property along with the index as shown for other multivalue list items present in the metadata. |
||
36369661 |
3-35545685791 |
NXT-27339 |
Claim line page fails when using same tags as claim page |
Description: |
If a custom claim floorplan and a custom claim line floorplan use the same tag, it sometimes causes an error when the user tries to view the claim line page. |
||
35675153 |
NXT-27395 |
Widgets:- Boilerplates are not loading when multiple widgets with same resource are loaded |
|
Description: |
While adding widgets through "Add-Card", boilerplates are not loading when multiple widgets are loaded with same resource and Template as "Data Table". |
||
35728057 |
NXT-27531 |
Renaming the usage name of the default insurable entity type for person, breaks the UI prompt |
|
Description: |
To align the person insurable object between the different components it needs to be renamed from servicedMember to person in OHI Claims. This is required for integration purposes. After updating the different floorplans to use the new usage name, the prompt is displayed as <person> |
||
35874448 |
NXT-27796 |
CMT import with all provider groups override existing provider group affiliations |
|
Description: |
Existing provider group affiliations are not retained after CMT import of a set that has all provider groups |
||
36246830 |
NXT-28649 |
Combination check for mandatory procedure within claimlines of the same claim works erroneously in certain cases |
|
Description: |
When combination check dynamic logic checks messages that were attached on another claim line on the same claim during its combination check, it does not work as expected |
||
37266270 |
NXT-28713 |
Evaluation of combination check fetches all the claim lines in the memory instead of doing it in paginatino manner. |
|
Description: |
Evaluation of combination check fetches all the claim lines in the memory . Expected behavior is to fetch the lines from DB in a paginated manner to prevent memory issues . |
||
36429395 |
3-36007720391,3-35991130131 |
NXT-29045 |
Access mapping issues for UI Pages |
Description: |
For some pages there are some missing access mappings which the user should directly get upon getting access for the UI page. |
||
36480420 |
3-35999586298 |
NXT-29121 |
Loading time of widgets is more when many widgets are configured for a page |
Description: |
When more than 5 widgets are configured for a page, loading all the widgets take considerably more time and performance must be optimized while loading these widgets. |
||
36505971 |
NXT-29172 |
Access to consumptions is not tracked in audit log |
|
Description: |
PHI logging does not track access to adjudication counter and provider limit counter related entities |
||
36611305 |
NXT-29363 |
No base view for interfaced messages |
|
Description: |
In claims, there is no base view OHI_INTERFACED_MESSAGES_BV created for OHI_INTERFACED_MESSAGES. |
||
36630484 |
3-34332951041 |
NXT-29394 |
Config migration inbound operation during claims benefit processing leads to database deadlocks |
Description: |
Performing a cmt import while a claim is processing benefits leads to deadlock errors . |
||
36703909 |
3-37528423931 |
NXT-29515 |
Additional Field values when filled are not retained after save |
Description: |
Additional field values of a dynamic record for a claim cannot be nullified by passing in empty tags |
||
36691212 |
3-36700304951 |
NXT-29523 |
System randomly throws optimistic locking exception while updating dynamic logic on CFS deployments |
Description: |
On cloud deployment (specifically on CFS) optimistic locking exceptions are thrown occasionally while updating the dynamic logic, as the update DYLO is not propagated properly on other nodes. |
||
36745607 |
NXT-29609 |
Line of Buisness does not exist as configurable entity in OHI CLAIMS |
|
Description: |
Access restrictions of type 'Line of Business' exist in Claims, but no lines of business can be configured. |
||
36746374 |
NXT-29611 |
Relation replication fails due to restricted identifiers |
|
Description: |
Relation replication fails due to relation identifiers with an identifier type has an access restriction in the even that the subscribing application’s system user does not have the appropriate access |
||
36765095 |
NXT-29642 |
Empty ID for dynamic fields in query results |
|
Description: |
The ID for single-value non-time-valid dynamic fields returned as null in the search results |
||
36784712 |
NXT-29679 |
coverage Regime Page: When an error appears at Cover Withold Level, it appears only at top level tab |
|
Description: |
coverage Regime Page: When an error appears at Cover Withold Level, it appears only at top level tab |
||
36821181 |
3-34615815211 |
NXT-29756 |
Business rule CLA-FL-FINA-001 is applied incorrectly |
Description: |
BR should be invoked after currency conversion. |
||
36833641 |
3-37366560871 |
NXT-29806 |
Generic claims API search using query params on service member doesn’t work with OR operator |
Description: |
Generic claims API search using query params on service member doesn’t work with OR operator |
||
36881104 |
NXT-29962 |
Providers and relations searches are not expanding dynamicData |
|
Description: |
Searches on super entities such as providers and relations are not expanding the dynamicData with the expand option in the request |
||
36937551 |
3-37567401981 |
NXT-30109 |
When there are multiple brands from the members enrollment, benefit flow considers other brands though claim is not related to other brands, which resulted in the unwanted fatal message. |
Description: |
When there are multiple brands from the members enrollment, benefit flow considers other brands though claim is not related to other brands, which resulted in the unwanted fatal message. |
||
36970114 |
3-37743857111 |
NXT-30190 |
Incorrect use of ohi.ws.client.readtimeout propperty to set the entire request/response timeout |
Description: |
The system property ohi.ws.client.readtimeout is intended to control the time (in milliseconds) that the client will wait for a response from the server after sending a request. However, it is currently being incorrectly applied to set the timeout for the entire request/response conversation, rather than just the response wait time. |
||
36971905 |
NXT-30193 |
Predefined method getTotals is not applicable for dynamic fields |
|
Description: |
Predefined method getTotals is not applicable for amount dynamic fields. |
||
36972536 |
3-37582942001 |
NXT-30195 |
Large chronicle queue files of size 180GB were created by applicationDBAppender while capturing application log events |
Description: |
The applicationDBAppender that captures the application log events in DB generated a large chronicle queue files of size 180GB due to an exception that got re-queued in an end-less while loop |
||
36997930 |
NXT-30235 |
Replacing a large claim via claimsimport IP does not work as expected |
|
Description: |
When claimsimport IP is executed to overwrite existing large claims, issues faced includes and are not limited to intermittent optimistic locking exceptions, data integrity violation exceptions, issues with reattaching pend reasons and replacing locked lines. |
||
36998042 |
NXT-30237 |
Sub claim does not accept enrollment list on large claim request for processing |
|
Description: |
When a large claim is sent in via claimsimport IP, the enrollmentlist details are not used by the subclaims for processing. |
||
36998125 |
NXT-30238 |
Large claim import fails with InvalidDataAccessApiUsageException when replacement rule applies |
|
Description: |
When a large claim is imported and a replacement rule applies on one of its claim lines, the import activity fails with status 'Completed with technical error' and trace log is generated for InvalidDataAccessApiUsageException. |
||
37831074 |
NXT-30342 |
Claims: It is not allowed to do subsequent updates in Financial Transaction Process Data |
|
Description: |
When an update is done in Financial Transaction Process Data and without closing the dialog another update is done, optimistic lock exception is displayed in UI. User has to refresh to perform a subsequent update |
||
37126786 |
:3-38128452811 |
NXT-30461 |
Unable to clear/delete end date in flex codes |
Description: |
Not able to remove the start/end date of the flex code tab in the flex code definitions page. It should be removable as per expected behavior. |
||
37151503 |
3-38171733161 |
NXT-30471 |
Changed coverage regime not completely loaded |
Description: |
Not all changes are being reflected when loading a changed coverage regime with CMT |
||
37210599 |
3-38374882641 |
NXT-30577 |
Enrollment callout does not raise error when the response does not contain a product code |
Description: |
User accidentally forgot to attach the (Claims) product to the enrollment product. As a result the response to the enrollment callout from Claim to Policies did not contain the product code. Although we see an error being present in the application log, this error does not get raised and as a results the Claim 'hangs' in the Enrollment Call Out Step. |
||
37223884 |
NXT-30596 |
Draft provider pricing clause without a method type or rule type can be created |
|
Description: |
A draft provider pricing clause can be created with generic API or UI without a method type or rule type filled. A real provider pricing clause can be built from this situation, leading to an incorrect real provider pricing clause |
||
37233849 |
3-38543286041 |
NXT-30606 |
Dynamic logic search builder expression sometimes inaccurately returns null values |
Description: |
Dynamic logic search builder expression sometimes inaccurately returns null values |
||
37257530 |
3-38637505211 |
NXT-30646 |
Query API does not return correct results when the search criteria contains an apostrophe. |
Description: |
Query API does not return correct results when the search criteria contains an apostrophe. |
||
37294171 |
3-38536697971 |
NXT-30708 |
Claim line shows reservation limit exceeding message erroneously |
Description: |
Claim line shows reservation limit exceeding message erroneously |
||
37912915 |
NXT-30779 |
Manual pricing - allowed amount set to USD when pricing is skipped on reprocessing a claimline with a different claimed amount currency |
|
Description: |
When claimed amount is not in default currency, reprocessing makes allowed amount currency as default currency if no provider pricing clauses are found. Even when it is priced manually, the claim line allowed amount is showing default currency and cannot be changed. |
||
37345449 |
3-38807633941 |
NXT-30784 |
Limit maximum fetched from product benefit specification limit even when enrollment response overrides it |
Description: |
When the adjudication limit maximum is overridden by parameter in enrollment response, claims are alternatively using product benefit specification limit maximum |
||
37938007 |
NXT-30809 |
Diminishing Rates - When a record is updated with end date, 'Diminishing Rates Block' table shows block range as 'undefined' for all the records |
|
Description: |
On the Diminishing Rates page, while updating the Diminishing Rate Blocks tab, if we try to add/update the Diminishing Rate Block Sizes and Diminishing Rate Block Amounts tabs with an End Date, the Block Range is appearing as undefined. |
||
37526111 |
NXT-30819 |
Overturn link is not displayed next to claim denied message for a claim in Manual Adjudication Status |
|
Description: |
Navigate to claims page and fetch a claim which has denied message. Overturn link is not displaying next to denied message. |
||
37489530 |
NXT-30929 |
Countries LOV only shows the code, it doesn’t show Name |
|
Description: |
In all the LOVs where the lov is configured to show anything apart from code and description for example code and name in those cases it is only returning code. It doesn’t show name in those cases even when those are configured in its related LOV floorplan. |
||
37818421 |
NXT-30969 |
Quick search criteria from search page is auto populated in quick search of dialogs opened |
|
Description: |
When a search is done using quick search criteria, the criteria is populated to any other dialog opened subsequently. User has to clear the criteria in the dialog to see expected data |
||
37527540 |
NXT-31010 |
Configuring a bank that references itself in its bank account number detail breaks the UI |
|
Description: |
Configure a bank (make it active). Add a bank account number relation. Set the bank value on it to the bank created. Navigate to banks page and try to open the bank, UI stays in a loading state |
||
37677184 |
NXT-31193 |
Prefix is not working for multi value fields while configuring it in labels |
|
Description: |
Label Component needs to to extend to support Prefix for multi value fields |
||
37733971 |
NXT-31198 |
It is not possible to save a claim after duplicating a claimline |
|
Description: |
After using Copy Claimlines feature, it is not possible to save the claim even after entering a new code on copied claimline. Error "The claim line already exist" is displayed in UI |
||
37697020 |
NXT-31210 |
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. |
||
37706978 |
3-40007142171 |
NXT-31222 |
Claims search does not expand dynamic fields on serviceprovider |
Description: |
When a post search is performed on claims with expand=all, the dynamic fields on serviceProvider are not expanded. |
||
37693624 |
3-39900404711 |
NXT-31292 |
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 |
||
37824918 |
NXT-31309 |
Claims in progress - facing error on selecting advanced search value |
|
Description: |
If a LOV value is already selected in Advanced Search for a specific criterion in any Operation Reports page, and the operator for that criterion is changed, the selected LOV value is not cleared. As a result, the search query becomes incorrect when the Search button is clicked. |
||
37818431 |
NXT-31338 |
In Search, Date format must be DD/MM/YYYY but not DD-MM-YYYY |
|
Description: |
In Search bar, date must include slash and should be of the format DD/MM/YYYY |
||
37774608 |
NXT-31344 |
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 |
||
37780435 |
NXT-31351 |
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 |
||
37788964 |
3-40242015751 |
NXT-31357 |
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 |
||
37807202 |
NXT-31381 |
ohiHttpRequest and initCallout methods work with any destination code value if correct credentials are set for that value |
|
Description: |
The ohiHttpRequest and initCallout methods accept any destination code value when correct credentials are set for that specific value. |
||
37814244 |
NXT-31386 |
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 |
||
37908534 |
NXT-31389 |
Attributes, Segments, More Section retain previous search result values in Accounting details page |
|
Description: |
In claims accounting details page, when a new search is done without closing Attributes, Segments and more section from previous search, these sections are not refreshed. It retains previous data. |
||
37815786 |
3-40346571471 |
NXT-31392 |
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 |
||
37832371 |
3-40369237351 |
NXT-31413 |
Claimline not highlighted when the claim status is "finalized" and 'details Inline' toggle is off |
Description: |
Claimline not highlighted when the claim status is "finalized" and 'details Inline' toggle is off |
||
37843330 |
3-38722563251 |
NXT-31429 |
Add logging to diagnose missing counter periods for product limits with carry over setting |
Description: |
Add logging to diagnose missing counter periods for product limits with carry over setting |
||
37851423 |
NXT-31442 |
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. |
||
37860280 |
3-40215221901 |
NXT-31449 |
Claim lines are not included in an adjudication case even when it satisfies all criteria for ancillary line |
Description: |
Claim lines are not included in an adjudication case even when it satisfies all criteria for ancillary line and falls within start date and end date of the case. |
||
37866956 |
3-40127122511 |
NXT-31456 |
The base view generation operation sometimes remains stuck in the 'In Process' status indefinitely |
Description: |
When the base view generation operation throws an unhandled exception, it gets stuck in 'In Process' and never terminates. |
||
37870555 |
3-40388321491 |
NXT-31458 |
No resolve link for pend reasons under "see more" |
Description: |
No resolve link for pend reasons under "see more" in Claims page |
||
37908921 |
NXT-31466 |
Apply Options drawer - On Mouse dragging action, the drawer closes abruptly |
|
Description: |
Apply Options drawer - On Mouse dragging action, the drawer closes abruptly |
||
37882134 |
NXT-31475 |
Zip and Unzip operations in Data File Sets IP return HTTP 405 in SaaS |
|
Description: |
The Zip and Unzip operations in Data File Sets IP return HTTP 405 (Method Not Allowed) in SaaS. |
||
37882380 |
NXT-31476 |
Default value for a dynamic record SVNTV is showing for existing records even in edit mode |
|
Description: |
The default value for the dynamic record SVNTV is currently appearing for existing records even in edit mode. This default value should only be applied in create mode and should not be displayed during editing of existing records. |
||
37882446 |
NXT-31477 |
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 |
||
37887109 |
NXT-31489 |
Generateaccountingmessage IP populates reversal as false for null reversal accounting details |
|
Description: |
Reversal has been made optional for POL-16484 since an option is added to not group accounting details on reversals, but the generate account message operation was not adjusted to reflect that the reversal indicator could be empty. |
||
37893768 |
NXT-31508 |
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. |
||
37898186 |
3-40602279631 |
NXT-31520 |
Explicit datatype conversion on record definition fields instead of implicit for char types. |
Description: |
Earlier, referencesheetline query api returned incorrect results when any comparative query like gt(>), lt(<) etc was used on number type fields. Some refactoring was done to fix this behavior, where the datatype of the query field was determined from the datatype defined on the record definitions and the datatype was implicitly inferred in the database query for char type. This caused some datatype mismatch when some records were defined as char but the values were of number type like 1, 2, etc. |
||
37921013 |
NXT-31523 |
Able to add duplicate values in the combobox in DPPC page |
|
Description: |
Able to add duplicate values in the combobox in DPPC page |
||
37907995 |
NXT-31531 |
Dynamic Record: Sort not working when we have any blank record |
|
Description: |
Dynamic Record: Sort not working when we have any blank record |
||
37908456 |
NXT-31536 |
Form table: Sort is not working when records are loaded after changing the sort in form table |
|
Description: |
On changing the sort order from ascending to descending or vice versa in form table, sort is not working |
||
37910372 |
3-40601455857 |
NXT-31539 |
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. |
||
37912299 |
NXT-31540 |
Mandatory multivalued fields create extra row and it does not allow saving data |
|
Description: |
For multivalued fields, if we give mandatory as true in floorplan, newly created empty row is not allowing to save data . |
||
37924299 |
NXT-31571 |
User sequences cannot be migrated via CMT |
|
Description: |
Configuration Migration does not consider user sequences as a top level item in claims application |
||
37926308 |
NXT-31576 |
Claims in progress - Previously opened tab is showing up instead of home page |
|
Description: |
Claims In Progress: click on any of the claim code hyperlink, Navigate to any other tab and close the pop up. Try to open any other claim code. It stays on previously opened tab instead of opening claim details. |
||
37924959 |
NXT-31577 |
Data File Sets IP does not return the message text in the response for error codes DAT-IP-DAFI-013 and DAT-IP-DAFI-014 |
|
Description: |
When encountering error codes DAT-IP-DAFI-013 and DAT-IP-DAFI-014, the associated error messages are not being displayed in the response. The expected behavior is that the error messages corresponding to these error codes should be returned in the response, providing more context and information about the error |
||
37931699 |
NXT-31589 |
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. |
||
37966574 |
NXT-31668 |
Flex Code Base Views are both removed and updated at the same time |
|
Description: |
During Base View generation, the system removes all Base Views related to Flex Codes and creates new ones for all the configured Flex Codes. Sometimes the system removes a Flex Code Base View while generating a new one with the same name, resulting in an error saying "table or view does not exist". This issue happens intermittently. |
||
Deprecated Items
These features will be removed in a future release. Customers are advised to review the documentation and take timely action.
| JIRA Key Announced | Release Announced | Summary |
|---|---|---|
NXT-25000 |
3.22.2.0.0 |
The use of parameters that influence the resource representation in the 'Accept' header of an HTTP request is deprecated. |
POL-7669 |
3.22.2.0.0 |
The type of the marital statuses of a Person has changed from an enumerated, fixed list of types to a configurable list. |
CPN-3249 |
4.25.1.0.0 |
HTTP API Caching override feature is deprecated in this release and will be removed in a future release. |
POL-14428 |
4.25.1.0.0 |
The |