Release Notes for Oracle Health Insurance Claims Adjudication Release 4.24.1.0.0

This document contains the release notes for Oracle Health Insurance Claims Adjudication Release 4.24.1.0.0.

Version compatibility: Oracle Health Insurance Claims Adjudication Release 4.24.1.x is only compatible with other Oracle Health Insurance applications release version 4.24.1.x unless explicitly stated otherwise.

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
AUT-3282	Enhance Monitoring/Liveliness Check in OHI applications OHI applications expose a /health endpoint that should report the healthiness of the application on that node. The implementation originally was very limited: it returned a static response. This has been changed in 4.23.1: if memory is lower, /health returns 429. With this release we are extending the /health endpoint to: /health/ready which returns UP if the node is able to process requests, DOWN otherwise. A number of readiness checks have been implemented including memory, database connectivity and cpu utilisation for which the threshold is defined by a new optional system property ohi.system.cpu.threshold.high /health/live which returns UP if the node is still alive, DOWN otherwise. A liveliness check has been implemented using the Coherence Health Check API. Documentation Links: Administration Guide - Application Health Check Endpoint
AUT-3342	Automatic detection of stuck activities As part of this enhancement, when an activity is in queue, the Activities IP returns status QD (Queued). Added new status QD to the domain "ACTIVITY STATUS". Added a new column process_queued_datetime to the table "act_activities". Stuck Activities: Added a new functionality to detect and send notification for the activities that get stuck. This functionality is enabled by default and can be disabled by setting ohi.activityprocessing.heartbeat.frequency property value to '0'. The following system properties have been added to set up heartbeat and cleanup service time intervals for activities: ohi.activityprocessing.cleanup.frequency (default value is 600 seconds) ohi.activityprocessing.heartbeat.frequency (default value is 300 seconds) When an activity is detected as stuck, that is when the root activity’s status changes from InProcess (IP) to TechnicalError (TE) by the cleanup service, it is re-submitted and the maximum number of re-submissions can be configured by the following property: ohi.activityprocessing.max.resubmit.attempt.count (default value is 3) If the stuck activity exceeds max.resubmit.attempt.count, it is sent as a notification to any of the following configured endpoints: ohi.activityprocessing.notification.endpoint.<0>, where 0 is activity type. ohi.activityprocessing.notification.endpoint Documentation Links: Developer Guide - Activities Developer Guide - Activity Model
CPN-3037	Automatically gather SQL monitor report for REST API call In many scenarios, evaluating the SQL execution plan for REST API calls is crucial to determine the efficiency of their access paths and to gauge their potential resource cost. The current manual process of enabling SQL logging, identifying relevant SQL statements within the logs, and retrieving their execution plans/SQL monitor plan is time consuming for the DBA/AMS team (in SaaS deployments). This enhancement aims to automate the creation and retrieval of SQL monitor reports for Query API calls, eliminating the need for manual intervention and streamlining the process. As part of this feature, a new header parameter enablesqlmonitorreport is introduced in Query API. This parameter is intended for use only in Non-Production environments and can have the following values: all: Monitors all SQL queries generated in the Query API rootResourceOnly: Monitors only the SQL query generated on the root resource Not specified: If this header is not included, no SQL monitor report is generated for any SQL query, maintaining the current behavior Documentation Links: Developer Guide - Gathering of SQL Monitor Report
CPN-3079	Auto purge feature As data volume in Oracle Health Insurance applications continue to grow with the processing of more data, it becomes essential to manage the database efficiently. Oracle Health Insurance applications include various PL/SQL packages for purging processes. However, these processes currently require manual intervention by customer DBAs/AMS team to configure and schedule purge jobs during planned maintenance windows. To streamline this process and automate database maintenance, we are introducing an auto-purge job feature. This feature eliminates the need for manual scheduling of various purge jobs and ensures that data is regularly purged according to predefined criteria. As part of this enhancement, we have a introduced a new PL/SQL package ohi_auto_purge_pkg.purge_all and modified the following functionalities : The structure of the following procedures has been revised, introducing an optional input parameter p_commit_size to enhance flexibility and control over the purging process cla_data_purge_pkg.purge_data ohi_repl_purge_pkg.purge_data Log message purging is now integrated into the auto-purge feature, and as a result, the following HTTP API resources have been made read-only. logeventretentionperiods API loglevelretentionperiods API Purging of PHI logs is now integrated into the auto-purge feature. So, the property ohi.logging.phi.min.retentionperiod is removed The process now integrates purging of all datafile sets into the auto-purge system, eliminating the need for separate scheduled scavenging and purging of incident files. So, the property ohi.incident.datafileset.retentionperiod is removed Oracle recommends frequent and automatic purging of technical data and operational data using the auto-purge job feature. For example, customer DBA/AMS team (in SaaS) can set up auto purge through the use of a DBMS_SCHEDULER job. See the user guide for more details and for a sample SQL script that creates auto purge job using DBMS_SCHEDULER.create_job PL/SQL procedure. Note that the initial purge job might take longer if the volume of the data is very high (for example, if the system has two years of data to purge and if the retention days for technical data are set to 60 days). So, Oracle recommends the DBA/AMS team to set a higher retention period (for example, one year and 11 months) for the initial run (so only 30 days of data is purged in the very first run). The retention days can be reduced gradually until the historical data is purged. Documentation Links: Administration Guide - Enabling Data Purging for Operational Tables Administration Guide - Auto Purge Administration Guide - Datafile Set Trace Files Retention Administration Guide - Purging Data from Replication Technical Tables Administration Guide - Purging Data from Technical Tables
CPN-3100	Enhancing Environment Name Setup in Oracle Health Insurance Applications We are improving how the environment name is set in Oracle Health Insurance applications using the (existing) system property ohi.environment.identifier which can be set by the DBA for on-prem deployments or by AMS team in case of SaaS deployment. This change will impact the following areas: Property Management: Property entity includes a name, value, and environment attribute. Previously, the environment attribute matched the application’s database name. Going forward, it will reflect the value set in the set for the system property ohi.environment.identifier. Source Environment Tracking: Configuration items selected for migration include eight auditing fields. Previously, the two source environment fields (createdByEnvironment and lastUpdatedByEnvironment) stored the database SID. These fields will now reflect the value set in the system property ohi.environment.identifier. Note that in the UI, the environment name in the configuration migration import page will show the database SID for the old imports, but going forward (for new imports), the value set in the system property ohi.environment.identifier will be shown. Data Set Operations Integration Point: When importing from an environment, the "sourceEnvironment" attribute is required. Previously, this attribute contained the database SID of the source environment. Now, it will reflect the value set in the system property ohi.environment.identifier from the source system. These changes remove the dependency on the database SID and eliminate the need to access the DBMS to retrieve the environment name. Note: The value of the ohi.environment.identifier system property should not exceed 158 characters, as specified in the property description. Documentation Links: Administration Guide - Property Management Configuration Guide - Source Environment Tracking Developer Guide - Data Set Operations IP - Import From Environment
CPN-3120	Dynamic chunk size for extract activities This enhancement is further optimization in extract execution on top of this enhancement POL-12778, which has been delivered as backports in 4.23.2, 4.23.1 and 3.22.2. This release introduces improvements to the memory utilization of the extract activity, optimizes the loading of dynamic records, and updates several configuration properties related to extract activity. Memory Utilization Improvement When an extract is executed, the application creates a global activity. The global activity spawns multiple child activities. Each child activity extracts a specific number of entities/records and creates a data file. Initially, each child activity extracts records in chunks, based on the system property ohi.processing.chunksize.SELECT_EXTRACT_ITEMS. In this release, the system dynamically adjusts the chunk size based on memory utilization, starting with the value configured in ohi.processing.chunksize.SELECT_EXTRACT_ITEMS and optimizing as needed. Optimization of Dynamic Records Loading The system previously loaded all dynamic records of an entity into memory and then filter for the required dynamic record. In this release, the system directly loads only the required dynamic records into memory, significantly optimizing the process. Configuration Properties Update Following properties have been added in POL-12778 and we have removed them in this enhancement: ohi.extract.datafilesize ohi.extract.datafilesize.{0} We’ve introduced 3 new properties (see Configuration Properties section for more details on these properties): ohi.extract.datafilecount ohi.extract.datafilecount.resourcename.{0} ohi.extract.datafilecount.notificationkey.{0} Documentation Links: Developer Guide - Processing of extracts
NXT-13866	Processing a large claim This enhancement introduces a new integration point to intake a large claim. System processes it by automatically splitting into multiple sub-claims. This functionality is driven when these system properties are enabled: - ohi.claim.split - ohi.largeclaim.claimline.threshold - ohi.subclaim.claimline.threshold Documentation Links: Developer Guide Developer Guide Operations Guide
NXT-21630	View Regime Counters (ADF conversion) This enhancement will introduce view Regime Counter Page in JET
NXT-24066	WebLogic authentication implemented compliant with the Java Authorization and Authentication Service (JAAS) specification This enhancement introduces support for the SAML 2.0 authentication mechanism in the Oracle Health Insurance. Additionally, a new JAR file named "CustomIdentityAsserter" has been created to accommodate the Basic Auth configuration. Refer installation guide for further detail. Documentation Links: Installation Guide - Users and Authentication	4.23.1.0.8, 4.23.2.0.2
NXT-24215	Consumption Date This enhancement introduces the ability to set a consumption date as a new process field on a claim line. This new date controls which counter period is accessed for consumption. This allows customers to consume counters for period A when the actual claim line start date is period A+1. Documentation Links: Configuration Guide - Table 5. Limit Consumption Operations Guide - End-Reservation Derivation Rules
NXT-26997	Additional information on applied benefits This enhancement introduces additional fields on the claim page for the evaluated waiting period, whether the waiting period was served, and benefits applied as a result. This enhancement also introduces the ability to evaluate claim line parameters for a context waiting period logic for cases where a member has yet to serve the waiting period. Documentation Links: Operations Guide - Claim Line Benefit Specifications Operations Guide - Calculate Coverage and Consumption	3.22.2.0.17, 4.23.1.0.4, 4.23.2.0.0
NXT-27561	Selective financial limit carryover This enhancement introduces the ability to decide whether an out-of-pocket-maximum (OOPM) limit consumption counts towards year-end carryover. For example: An OOPM consumption from a coinsurance or a copay do not count towards a carryover. An OOPM consumption from a deductible does count towards a carryover. A new indicator, exclude from carry over is introduced on the product-benefit-specification limit to help make this decision. The decision acts as input to evaluate a coverage regime. Documentation Links: Configuration Guide - Product Benefit Specification Limit Configuration Guide - Adjudication Limits	4.23.1.0.5, 4.23.1.0.8, 4.23.2.0.2
NXT-27703	New REST endpoint to return fully constructed property model using floorplan & metadata A new IP has been introduced, which combines floor plan and metadata in the same response. This reduces the number of REST calls from UI, thereby improving page loading time.
NXT-27728	UI : Applied Parameter This enhancement introduces details about Applied Parameters during claims adjudication
NXT-27899	This enhancement enhances the claims and other entities to support the seamless processing of a large claim (a claim with many number of claim lines) This enhancement enhances the below entities to support the seamless processing of a large claim - CLA Claims entity - CTR Claims entity - Claim Event Rules - Derivation Rules - External Intervention Rules, and - Financial Hold Types Documentation Links: Configuration Guide Configuration Guide Operations Guide - Model - Claims & Claim Lines Operations Guide - CTR Claims, CTR Claim Lines & CTR Large Claim Mapping
NXT-27912	Support for regEx in UI This enhancement introduces ability to: * Specify regular expressions for string and number fields * Define the range for date fields * Override the minimum and maximum field length for number and string fields Documentation Links: Developer Guide
NXT-28011	Search Page for all Providers This enhancement introduces a new search Page for all Providers, where all providers (organizational and individual) can be searched.
NXT-28020	Attach additional diagnoses to a claim This enhancement introduces new predefined methods to replace diagnosis codes in a claim or claim line as part of the automated process flow. The methods help map one type of diagnosis coding system to another, for example, from ICD-9 to ICD-10. Documentation Links: Developer Guide - addDiagnosis and deleteDiagnosis	4.23.1.0.5, 4.23.2.0.1
NXT-28047	This enhancement introduces the various capabilities for a user to handle a large claim (a claim with many number of claim lines) and the linked sub-claims using JET user interface. This enhancement introduces various capabilities for a user to handle a large claim and the linked sub-claims using JET user interface: 1) Submit a Large Claim 2) Bring large claim back to In Process status 3) Unfinalize a sub-claim 4) Add/Remove message on one or more sub-claims 5) Resolve Pend on one or more sub-claims 6) Working capabilities on all the claim lines across the sub-claims that are linked to a large claim
NXT-28050	Improvements to page templates : Search Pages (List and Table) With this enhancement, Search Object List View and Search Object Table View Floorplan look and feel is updated: Global header is fixed when page scrolls Theme strip bar is moved from Global header to App header bottom Floor Plan Selection, Quick Search and Advanced Search are left aligned Page level Primary and Secondary actions are right aligned Table and Result level actions are shown in content area Documentation Links: Developer Guide
NXT-28067	UI: Copy feature for editable table This enhancement allows user to configure copy action on table and tab table components in the floorplan at the row level. Clicking on copy: - Creates a new entry in Edit mode. - Does a deep copy of the object including child resources as configured in the Floorplan.
NXT-28236	UI: Download in Widgets This enhancement introduces ability to download viewed data from widgets
NXT-28241	Upgrade Coherence library in activity processing In this release, we have upgraded Coherence library used in activity processing to enhance the efficiency. Additionally, a new system property has been introduced, giving you the flexibility to disable activity processing on a specific JVM/node if necessary. This can help manage workloads more effectively. Documentation Links: Developer Guide - Disable Activity Processing on a Specific JVM/Node
NXT-28394	Detach PolicyAccountTransactionEvent task from AS2805_A flow The purpose of this enhancement is to detach PolicyAccountTransactionEvent task from AS2805_A flow by making it asynchronous (by enqueuing the task to Oracle AQ) instead of scheduling immediately. This will be helpful when AS2805_A workload is separated to specific JVMs (which will no longer process PolicyAccountTransactionEvent tasks as they will be put in to AQ and the dedicated JVMs processing AS2805_A requests will not dequeue those messages). This leads to high bandwidth/threads available to process AS2805_A claims.
NXT-28449	Additional functionality for UI Form component With this enhancement, the UI Form component now supports: Editable list resources Sort capabilities for tables configured within a Form Conditionally hiding a sub-section
NXT-28465	Optimize REST graph recreation of reference sheet line when a new reference sheet is created It was observed that creating reference sheet line every time a reference sheet creates is expensive process, which is causing huge memory consumption and causing time out issues. To address this, some source code have been optimised in ReferenceSheet.	4.23.1.0.8, 4.23.2.0.2
NXT-28671	Improvements to page templates : View and Edit List (Table) With this enhancement, Search View and Edit Object List (Table) Floorplan look and feel is updated: Global header is fixed when page scrolls Theme strip bar is moved from Global header to App header bottom Floor Plan Selection, Quick Search and Advanced Search are left aligned Page level Primary and Secondary actions are right aligned Table and Result level actions are shown in content area
NXT-29119	Claims page performance improvements. Optimize the loading time of the claims page to improve overall performance. The load time of the claims page is improved by reducing the response sizes of requested data, parallelization of data calls and deferring unused calls.	4.23.1.0.8, 4.23.2.0.2
NXT-29163	Add logging to diagnose duplicate policy products issue in enrollment callout In Oracle Health Insurance Claims Adjudication and Pricing we are adding logging to capture the unique key violation and log the enrollment response received, to diagnose duplicate policy products issue in enrollment callout. The log message contains the enrollment response received and logs it to the file only in case while processing the enrollment response a unique key violation occurs.	4.23.1.0.8, 4.23.2.0.2
NXT-29214	Allow updating the serviced member for an existing episode with no episode details. With this enhancement, it is now possible to update the serviced member for an existing episode with no episode details.	3.22.2.0.19, 4.23.1.0.7, 4.23.2.0.2
NXT-29222	UI: Status history for a CLA Claim and CTR Claim. With this enhancement, the user interface capture the 'Created By' user details on the status history for a CLA Claim and CTR Claim.
NXT-29269	Exclude links from 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. Documentation Links: Developer Guide
NXT-29497	UI: Copy feature on Floorplan, Widget pages and dynamic records This enhancement gives the copy action on Floorplan and Widgets pages out of the box and for tab list (result component) a user can configure copy action for all dynamic records
NXT-29892	Added County and State and County Code to address page With this enhancement: Person’s address page is updated to include County and State and County Code fields Additional restriction added for State and County Code to only allow positive values
NXT-30155	Removal of whitespaces from the HTTP API responses In Oracle Health Insurance Enterprise Claims Adjudication, to optimize the loading time of the claims page to improve overall performance, we have disabled fomatting of HTTP API responses. This reduces the size of the response.
POL-11680	Metadata change for conditional mandatory dynamic field usages When retrieving the metadata for a resource, dynamic field usages configured as conditional mandatory are now excluded from the list of required attributes.
POL-12035	Include Flex Code Identifiers in Extracts For multi-value or time-validity usage: . Unique ID added for for multi-valued or time-validity usage for the field/FlexCode . FlexCodeSystem ID added as "flexCodeDefinitionId” for FlexCode/DynamicRecord . Additional fields to be added which are not marked as key value or descriptors and the actual usage name for FlexCode/DynamicRecord For Single value Non Time Valid usage: . FlexCodeSystem ID added as "flexCodeDefinitionId” for FlexCode/DynamicRecord . Additional fields to be added which are not marked as key value or descriptors and the actual usage name for FlexCode/DynamicRecord
POL-12778	Extracts: Decouple bucket size from fetch size When an extract is executed, the application creates a global activity. The global activity spawns multiple child activities. Each child activity fetches a specific number of entities and stores them in a data file. The ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS system property determines the number of entities fetched per child activity or the fetch size. All the fetched entities per child activity, are stored in the same data file. Therefore, the higher the value of the system property, the higher the number of entities gathered in a single data file. This could cause memory issues when a large number of entities and subresources (from a single data file) are fetched into the memory at the same time. The ohi.processing.chunksize.SELECT_EXTRACT_ITEMS` property determines the size of a chunk and has a default value of 100. The value of this property represents the number of entities fetched at the same time in a single chunk. Setting a higher value for this property (for example, 500) decreases the duration of the extract as the number of entities fetched each time increases. The ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS is no longer required and hence can be removed from the configuration. The change of property values is only recommended if the application is facing issues performing at optimal levels. Documentation Links: Installation Guide - Application Properties	3.22.2.0.18, 4.23.1.0.4, 4.23.2.0.1
POL-12956	Purge data files In Oracle Health Insurance applications, data files generated during various activities (e.g., extract activity, financial messages activity and data files uploaded to initiate long-running operations) remain in the system even after they have been processed/consumed. Currently, there is no mechanism in place to automatically clean up these data files once they have been processed/consumed, leading to inefficiency of the database storage space. This enhancement aims to automate the cleanup process and optimize database storage space. To enable purging data files, we have introduced a new PL/SQL package ohi_purge_datafileset_pkg. Documentation Links: Administration Guide - Purging Data from Data File Sets
POL-13518	Endpoint change for data masking definitions As part of this enhancement, the endpoint to configure and maintain data masking definitions is updated to /datamaskingdefinitions along with updated response messages. Documentation Links: Developer Guide
POL-13924	UI: Improved embedded view for tab component This enhancement introduces additional control for the embedded view for tabs i.e. by configuring 'dualDefault' within the floorplans
POL-14132	Clearance of activities stuck in In Process stage from coherence submission caches using IP Due to excessive load, the processing-pattern grid service stops processing activities, causing them to be stuck in the in process stage for a long time. Manually marking these activities to technical error (TE) and resubmitting them results in an exception as a reference to these activities already exist in coherence submission caches. Thus, the recovery of activities is only possible upon a full restart. The new integration point supports the clearance of coherence submission caches to facilitate the activity recovery process to avoid a complete restart.	3.22.2.0.20, 4.23.1.0.8, 4.23.2.0.2
POL-14140	ADF specific configuration removed This enhancement removes and modifies configuration that was for ADF specific Documentation Links: Developer Guide - External Links Developer Guide
POL-14640	Introducing a scheduler for checking the status of the current tasks The task processing framework has been improved with automated mechanisms for task recovery and notifications in case tasks (for example, data replication synchronization task) become stuck in a particular status for a long time. Documentation Links: Administration Guide - Application
PRD-3738	Product Service Definitions (Across Products) - Bulk actions - Update/Delete multiple Product Service Definitions This enhancement introduces bulks actions for Product Service Definitions (Across Products) UI page : Delete Selected Rows, Add Specific Network, Remove Specific Network, Update Selected Rows. Note: As part of this enhancement the below issue is fixed - Blank row will not show up for mandatory fields (anything in bulk operation)

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

1. Perform any pre-upgrade steps.

2. Stop all the managed nodes running the existing version of the application.

3. Perform any pre-undeploy steps.

4. Undeploy the existing version of the application.

5. Back up the database.

6. Perform any post-undeploy steps.

7. Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.

8. Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.

9. Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.

10. Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)

11. Run the Upgrade script:

    1. Open a command window and browse to <OHI_ROOT>/util/install.

    2. Run the upgrade by executing ./ohi-update.sh .

12. Make the required changes to the ohi properties file

13. Perform any post-upgrade steps

14. Start WebLogic application server

15. Deploy the Application

16. Perform any post-deploy steps

Additional Upgrade Steps for Installation

The following phases are defined: pre-upgrade: Application is still running pre-undeploy: Application is stopped, but not undeployed. post-undeploy: Application is undeployed. Database is backed up post-upgrade: Released upgrade script has run. post-deploy: New application is deployed and is up and running.

post-undeploy

1. See "Users and Authentication" section in the "Install and Configure Oracle WebLogic" topic in the Installation Guide, before deploying the new upgraded EAR if you are using Basic Auth as the authentication mechanism.

2. Install the mandatory Coherence 14.1.1 Feature Pack 22.06 Cumulative Patch 9. See the Installation Guide, section "Required Software" for more details.

3. Removal of the deprecated operational reporting views:
   The support of the operational reporting views has been removed from this release, and their schemas and the roles will no longer be required. The below steps are optional and if the customer wants to use the deprecated operational reporting views, they can retain the below schemas
   OHI_CLAIMS_VIEWS_OWNER
   OHI_CLAIMS_CONF_VWS_OWNER
   OHI_CLAIMS_NONCONF_VWS_OWNER
   

   OHI will not support any changes or fixes to the above mentioned schemas.
   

   As a part of the upgrade, it is recommended to run the following commands as SYSTEM user to remove the below schemas and the roles from the application pdb:

   DROP USER OHI_CLAIMS_VIEWS_OWNER CASCADE;
   DROP USER OHI_CLAIMS_CONF_VWS_OWNER CASCADE;
   DROP USER OHI_CLAIMS_NONCONF_VWS_OWNER CASCADE;
   DROP ROLE OHI_CLAIMS_CONF_VWS_ROLE;
   DROP ROLE OHI_CLAIMS_NONCONF_VWS_ROLE;

4. As part of POL-14140, the HttpLink entity has been removed. If the HttpLink was exported or imported using the Configuration Migration Tool (CMT), the technical tables may still contain references to the HttpLink record. To clear these references, run the following commands as OHI_CLAIMS_OWNER:

   TRUNCATE TABLE OHI$CFG_MIGR_MARSHALLED_ITEMS;
   TRUNCATE TABLE OHI$DATA_SET_PROCESS_FAILURES;

post-upgrade

Note: This action applies only to the production environment.

Action: In the properties file, add a new property ohi.query.api.enable.sqlmonitorreport and set its value to false.

Example: ohi.query.api.enable.sqlmonitorreport=false

Configuration Properties

Ref	Action	Description
AUT-3282	Added	ohi.system.cpu.threshold.high Property to set the system CPU utilisation threshold. If system CPU goes above this value, the system enters the low CPU state.
AUT-3342	Added	ohi.activityprocessing.cleanup.frequency If any in progress activities, (current - last updated date) timestamp is greater than value configured by this property, then the status gets updated to technical error.
AUT-3342	Added	ohi.activityprocessing.max.resubmit.attempt.count This property configures the maximum number of times a stuck root activity can be re-submitted for processing.
AUT-3342	Added	ohi.activityprocessing.heartbeat.frequency This property configures the scheduled time frame for updating the last_updated_date column for the running activities to rectify the activities getting stuck in the progress status.
CPN-3037	Added	ohi.query.api.enable.sqlmonitorreport Property to enable SQL monitor reports. Set to TRUE (by default) for lower environments and set to FALSE for production environment.
CPN-3079	Removed	ohi.logging.phi.min.retentionperiod Purging of logs is now integrated into the auto-purge feature. So, this property is removed. The default retention for PHI logs with the auto-purge function is 2560 days (7 years) and can be managed through the autopurgemetadata API
CPN-3079	Removed	ohi.incident.datafileset.retentionperiod Purging of all datafile sets is now integrated into the auto-purge system, hence, eliminating the need for separate scheduled scavenging and purging of incident files. So, this property is removed.
CPN-3120	Added	ohi.extract.datafilecount A new optional configuration property is added which controls the number of data files generated by the extract activity. This property also determines the number of child activities executed. The value set for this property directly impacts the parallelism of child activities. A higher value allows for more parallel child activities, which can improve performance by making the extraction process multi-threaded, but at the cost of generating more number of data files. On the other hand, Setting a value too low, such as 1 or 10, may result in the extract process functioning as a single-threaded operation, potentially reducing performance. While the default value of this property is set to 100, Oracle recommends to evaluate your specific requirements and performance needs to determine the optimal value.
CPN-3120	Added	ohi.extract.datafilecount.resourcename.{0} This property behaves similar to ohi.extract.datafilecount, but controls the number of data files generated for a specific resourcename/entity. The placeholder value {0} refers to the resourceName used in the extract request.
CPN-3120	Added	ohi.extract.datafilecount.notificationkey.{0} This property behaves similar to ohi.extract.datafilecount, but controls the number of data files generated for a specific notificationKey. The placeholder value {0} refers to the notificationKey used in the extract request.
CPN-3120	Removed	ohi.extract.datafilesize.{0} This property is replaced with new property ohi.extract.datafilecount.resourcename.{0}
CPN-3120	Removed	ohi.extract.datafilesize This property is replaced with new property ohi.extract.datafilecount
NXT-13866	Added	ohi.subclaim.claimline.threshold This system property defines the threshold number of claim lines for each sub-claim. Possible values: Integer ≥ 1 Default value: 30 Change effective: Next Execution Access Mode: Protected
NXT-13866	Added	ohi.claim.split The large claim import integration point starts splitting the claim into multiple sub-claims only when this system property is set to 'Yes'
NXT-13866	Added	ohi.largeclaim.claimline.threshold The Large Claim Import Integration Point should be used for the creation of a claim with more than thethreshold number of claim lines as specified by this property Possible values: Integer ≥ 1 Default value: 1000 Change effective: Next Execution Access Mode: Protected
NXT-28241	Added	ohi.activityprocessing.enabled A new optional system property is introduced to disable activity processing on a specific JVM/node
NXT-28727	Added	ohi.oauth.token.jwt.assertion.param.name Name of JWT assertion parameter used in OAuth token request. It could be different across OAuth server. Default value is "assertion"
POL-12778	Added	ohi.processing.chunksize.SELECT_EXTRACT_ITEMS This property controls how many items the system exports in one chunk. Once a single chunk is extracted, the memory gets cleared and the system will continu with the next chunk. The default value for this property is 100. If the value of ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS is currently set to a lower value than 100, we recommend to use that value for this property as well.
POL-12778	Added	ohi.processing.chunksize.SELECT_EXTRACT_ITEMS.{0} This property controls how many items the system exports in one chunk per entity. Once a single chunk is extracted, the memory gets cleared. The placeholder should be replaced with the entity name, to be similar as the resourceName attribute in the Extract definition.
POL-12778	Removed	ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS This property was formerly used to determine the number of entities fetched within a single child activity and therefore also determines the number of entities to be created in a data file. Now that those sizes as decoupled, this property does not serve any function anymore. Therefore, this property can be removed from the configuration (e.g. properties file)
POL-14640	Added	ohi.taskprocessing.scheduler.pending.overhead The maximum time for which a task can be present in the PROCESSING status. The scheduler will recover the task if it is in PROCESSING status for a time greater than this time interval. Allowable values are the ref_code’s: 'PolicyUpdateRequestPolling', 'DataReplicationTargetSynchronization', 'IntegrationEventAggregateCreator', 'IntegrationTransformation', 'RepublishingFailedMessages'. ref_code replaces {0}.
POL-14640	Added	ohi.taskprocessing.<0>.processing.timeinterval Determines the overhead in seconds over the pending time interval to check if a task is stuck in the PENDING status.
POL-14640	Added	ohi.taskprocessing.scheduler.frequency Determines how frequently the scheduler should run.
POL-14640	Added	ohi.taskprocessing.notification.endpoint The URL to which notifications should be sent by OHI if the task is in PROCESSING/PENDING status for a longer period or if the task is in ERRORED status. (Note that the maximum time a task can be in PROCESSING/PENDING status is configurable)

Web Services

Ref	Action	Description
AUT-3342	Modified	Activities API Attribute resubmitAttemptCount added.
CPN-3037	Modified	Query API A new header parameter enablesqlmonitorreport is introduced in Query API. This parameter is intended for use only in Non-Production environments and can have the following values: all: Monitors all SQL queries generated in the Query API rootResourceOnly: Monitors only the SQL query generated on the root resource Not specified: If this header is not included, no SQL monitor report is generated for any SQL query, maintaining the current behavior
CPN-3079	Added	autopurgemetadata API Added a new autopurgemetadata API
CPN-3079	Removed	loglevelretentionperiods API loglevelretentionperiods API supports only GET operation. POST/PATCH/PUT/DELETE operations are not longer supported
CPN-3079	Removed	logeventretentionperiods API logeventretentionperiods API supports only GET operation. POST/PATCH/PUT/DELETE operations are not longer supported
NXT-24215	Modified	Claims Update Include process field consumption date
NXT-24215	Modified	Claims Out Include process field consumption date
NXT-24215	Modified	Claims Processing New step End Reservation. Process field derivation rules for consumption date can be defined for this step
NXT-24215	Modified	Claims Processing Consumption is registered for the consumption date. When no consumption date is specified the system uses the claim line service date.
NXT-24215	Modified	Claims In Include process field consumption date
NXT-26997	Modified	Claim Line Benefit Specifications API Created the attribute evaluationResult
NXT-26997	Modified	Ctr Claim Line Benefit Specifications API Created the attribute evaluationResult
NXT-27561	Modified	Product Benefit Specification Integration Point Added Exclude From Carry Over indicator on product benefit specification limits
NXT-27703	Added	floorplans This IP will return floor plan combined with metadata in a single response.
NXT-28727	Added	Generic API for OAuthParameter Introduced generic APIs to manage OAuth parameters. Refer /generic/oauthparameters/metadata to know available endpoints to manage OAuthParameter entity
NXT-28727	Modified	generic/oauthclientcredentialsgrantconfigurations Supports configuration of OAuth parameters through oAuthClientParameters
NXT-28727	Modified	generic/oauthassertionjwtbearergrantconfigurations/ Supports configuration of OAuth parameters through oAuthClientParameters
POL-13518	Added	datamaskingdefinitions IP deidentificationmetadata IP got renamed to datamaskingdefinitions IP
POL-13518	Added	datamaskingdefinitions API deidentificationmetadata API got renamed to datamaskingdefinitions API
POL-14132	Added	clearsubmissioncaches IP New IP to clear coherence submission caches.

Data Conversion

Ref	Action	Description
NXT-27561	Added	Product Benefit Specification Limit Exclude From Carry Over indicator set to false
NXT-27703	Added	Access Restrictions Read access for the floorplans IP is provided as a part of mandatory accesses required for the applications in SETUP_ACCESS_ROLE.
NXT-28047	Added	Sub Claim Tab Floorplan added with page name 'claims' to view all the sub-claims linked to Large Claims in tab.
NXT-28047	Added	Sub Claim Page Floorplan added with page name 'subclaims' to view Sub Claims
NXT-28067	Modified	View Object List Pages System floorplan with View Object List template is updated with Copy action (also few system floorplan having tab table configuration)
NXT-29497	Modified	Floorplan and Widgets page System floorplan for Floorplans and widgets is updated with Copy action
POL-13924	Modified	DualDefault property of floorplan is modified The following system floorplans are modified : Claims - "dualDefault": "expandedCreate" Policies - "dualDefault": "expanded" Policies (MedicareAdvantage) - "dualDefault": "expanded"

Dynamic Logic

Ref	Action	Description
NXT-28020	Added	deleteDiagnosis This method removes a diagnoses code from a claim or claimline through dynamic logic within a derivation rule.
NXT-28020	Added	addDiagnosis This method is adds a diagnoses code to a claim or claimline through dynamic logic within a derivation rule.
POL-14140	Removed	country (Entity) Remove dynamic logic addressed to signature (Country Format)

UI Changes

Ref	Action	Description
AUT-3342	Modified	All activity pages A new status - 'Queued' and a new field 'processQueuedDateTime' has been added to these pages.
NXT-21630	Added	Regime Counters Page (CL0054) This enhancement will display regime details , regime counters and regime consumption of regime types coverage and authorization regimes
NXT-24215	Modified	Claims Page Include process field consumption date
NXT-26997	Modified	Claims Page The regime evaluation result is added to the applied benefits section of the page. Also, the applied parameters show the actual values that were applied
NXT-27561	Modified	JET Setup Product Benefit Specifications Added Exclude From Carry Over indicator
NXT-27561	Modified	ADF Setup product benefit specifications Added Exclude From Carry Over indicator
NXT-27728	Added	Applied Parameters Tab under Benefits Section Added Applied Parameters tab under benefits section that displays parameters applied to all claimlines, that are grouped per claimline
NXT-27728	Added	Product Parameters Tab under Benefits Section Added Product Parameters Tab under benefits section that displays Limits, Values and Reinsurance parameters linked to Product Benefit Specification that is referenced by ClaimLine Benefit Specification
NXT-27728	Added	Applied Parameters Tab under Claim Line Detail page Added readonly Applied Parameters Tab under ClaimLine Detail Section that displays parameters applied on claimline currently displayed
NXT-28011	Added	Providers(All)(RM0036) New search page for Providers which displays results from both organization and individual provider. The create button provides a dropdown with the option to create an organization or individual provider.
NXT-28047	Added	CTR Sub Claim Page Floorplan added with page name 'ctrsubclaims' to view CTR Sub Claims
NXT-28047	Added	Claimlines Search Page Page added to view all the claimlines and perform action like 'Add/Remove Message' and 'Add/Resolve Pend'
NXT-28047	Modified	Persons Page An object navigation added to view claimlines linked to that person.
NXT-28047	Modified	Claims Page Users can view large claims by navigating from the search claims page like regular claim. Sub-claims linked to the large claims are displayed in a Groups tab, allowing for easy navigation to the sub-claims view. Additionally, claim lines object navigation is added to the large claims view, enabling users to see all claim lines linked to the sub-claims in one place. User can perform available action at large claim and sub claims level
NXT-28067	Modified	View Object List Pages Copy row action added for view object list pages and in some pages having tab table configuration
NXT-28236	Modified	Widgets Download button added to widgets
NXT-28449	Modified	Policy Enrollment page Form Table is made editable and sort is enabled in the form table for policy enrollment page with 'MEDICARE_ADVANTAGE' tag
NXT-29102	Modified	Configuration Migration Sets Added keyboard shortcuts support to common actions i.e, Edit, Save and Cancel actions across all view edit pages
NXT-29119	Modified	Pend reason flow Resolving a pend reason on claims disables or hides respective resolve links and avoids reload of the claim page.
NXT-29222	Added	Claims - Claims History Added the user name of the user who had created the status History for CLA and CTR Claims
NXT-29497	Added	Floorplan and Widgets page Added copy action in floorplan and widgets hierarchical recursive pages
POL-14140	Modified	Country(RM0004) Removal of below attributes from the country floorplan prompt additional part 1 prompt additional part 2 prompt additional part 3 dynamic function (Number Format)
PRD-3738	Modified	Across Product Page Added bulk edit, delete feature and few other advanced editing features to this page.Blank row do not show up for mandatory fields

Breaking Changes

Ref	Action	Description
CPN-3079	Removed	loglevelretentionperiods API loglevelretentionperiods support only GET operation. POST/PATCH/PUT/DELETE operations are no longer supported. So, it is not possible to purge log messages based on a specific log level. Instead purging of logs (irrespective of the log level) is now integrated into the auto-purge feature
CPN-3079	Removed	logeventretentionperiods API logeventretentionperiods API support only GET operation. POST/PATCH/PUT/DELETE operations are no longer supported. So, it is not possible to purge log messages based on a specific log level. Instead purging of logs (irrespective of the log level) is now integrated into the auto-purge feature
CPN-3100	Modified	properties API If the environment attribute is used when configuring properties using the properties API, the value of the environment attribute should now match the value set for the system property ohi.environment.identifier. If these values differ, update the environment attribute using the properties API. Example: If the following properties (with different values for two different environments) are configured in the system: Property-1 id: 123 name: fusion.financials.url value: http://host-dev:port/fusion environment: DEV_CPN_PDB Property-2 id: 456 name: fusion.financials.url value: http://host-prod:port/fusion environment: PROD_CPN_PDB And if the value of the system property ohi.environment.identifier is set to OHI Capitation Production Environment in the Production environment and to OHI Capitation Development Environment in the Dev environment, then the environment attribute of the above two properties should be updated using the properties API after upgrading to this release, i.e., PATCH http://[hostName]:[portNumber]/[api-context-root]/generic/properties/123 { "environment": "OHI Capitation Development Environment" } and PATCH http://[hostName]:[portNumber]/[api-context-root]/generic/properties/456 { "environment": "OHI Capitation Production Environment" }
NXT-24066	Modified	Installation Configuration Customers using the Basic Authentication mechanism must follow the installation guide to install the newly built JAR file, "CustomIdentityAsserter.jar," and configure the WebLogic security provider accordingly.
POL-13518	Removed	deidentificationmetadata IP deidentificationmetadata IP got renamed to datamaskingdefinitions IP
POL-13518	Removed	deidentificationmetadata API deidentificationmetadata API got renamed to datamaskingdefinitions API
POL-14140	Removed	System Properties Remove system properties ohi.ui.maxrowstoreretrieve
POL-14140	Removed	https-link (Entity) Remove entity (httplinks) Remove dynamic logic addressed to signature (HTTP LINK)
POL-14140	Removed	Usages (Entity) Removal of below attributes In Lov? Search in Lov?
POL-14140	Removed	country (Entity) Removal of below attributes from the country entity . Number format . Amount Number Format . Integer Format . prompt additional part 1 . prompt additional part 2 . prompt additional part 3 . Dynamic Function (Address Format Code)
POL-14140	Removed	MDS Remove signature, Name : MDS (COND) and MDS (FUNC)
POL-14140	Removed	Access Restriction Remove access restriction type : attached data (Policies), financial hold and unlock claim lines (Claims)
POL-14140	Removed	Schedule Dimension (Entity) Removal of below attributes display length
POL-14140	Removed	Claims Forms (Entity) Removal of below attributes . procedure 1 display name . procedure 2 display name . procedure 3 display name
POL-14140	Removed	Agent (Entity) Remove dynamic logic addressed to signature Name Format (Agent)

Bug Fixes

BugDB	SR	Internal	Summary
36194649		NXT-28399	Add new row is shown at the last in table pages
Description:		Click Add new in table page. A new row is getting appended in the last visible row of the screen
Resolution:		Table component is modified with the below changes: 1) On click of Add button, a new row will be added to the top of the available rows. It is a sticky row to the table 2) Two new icons are added to a new row. Check icon would add the new row to the table and clicking on Cross icon would discard the new row. 3) User will have to click on Check icon and Save to persist the newly added data
Backports:		4.23.2.0.2
34159148		NXT-24713	Patch operation not working on Transaction Sources Resource
Description:		Patch operation on Transaction Sources does not work when the user tries to update the —Transaction Source Usages_ of —Transaction Source_.
Resolution:		Patch operation on Transaction Sources works when the user tries to update the —Transaction Source Usages_ of —Transaction Source_.
34145248	3-29423861521	NXT-24682	Enrollment callouts throw a null pointer error when authentication credentials are missing
Description:		Enrollment callouts throw a null pointer error when authentication credentials are missing. Instead, it should return EnrollmentClientException and log a message about credentials missing.
Resolution:		In the occurrence authentication credentials are missing, the message is logged and an EnrollmentClientException is thrown.
34008782	3-28606893871,3-35610906861	NXT-24457	Enrollment callouts throw a null pointer error on the read timeout
Description:		Enrollment callouts should not throw a null pointer exception on read timeout. It should log the timed out message and throw EnrollmentClientException.
Resolution:		In the occurrence of a timeout, the timed out message is logged and an exception is thrown.
Backports:		4.23.1.0.4, 4.23.2.0.1
34113807	3-29168078521	NXT-24626	User friendly message must be thrown instead of TokenMgrError
Description:		If the querystring is not properly formatted, then a parsing exception is thrown in the response with 500 status.
Resolution:		The error message in case of a parsing exception has been modified to convey proper information and looks like the following "title": "GEN-PROC-ERR; nested exception is com.oracle.healthinsurance.http.core.components.generic.search.parser.OhiParserException: Parsing Exception: Lexical error at line 1, column 79. Encountered: <EOF> after : "\\'%)"
34189192		NXT-24773	Add and Edit functionality not working properly for reference sheet object navigation and also results are not displayed correctly for reference sheets in Provider Pricing Clauses Page.
Description:		In the reference sheet based object navigation links for provider pricing clause page, add and edit functionality is not working, also results are not displayed correctly
Resolution:		Add and edit functionality works fine now and results are shown properly
33350875		NXT-23322	Provider limits are not working as expected
Description:		For provider limits without procedure definition, the limit is not applied across all the procedures of all claim lines of certain claims. For provider limits with procedure definitions, the limit should be applied only on the claim lines that have procedures of the same procedure definition. But now it’s getting applied on each claim line individually.
Resolution:
36289743	3-34612052061	NXT-28727	OAuth parameters should be configurable
Description:		OHI product supports only standard OAuth parameters. As its value/name can deviate across OAuth server, OHI application isn’t able to establish connection with OAuth server.
Resolution:		Introduced capability in OHI product to define custom OAuth parameters. These parameters can be reused across different OAuth clients later.
Backports:		4.23.2.0.1
36367681	3-35755073101	NXT-28910	Integration point outboundintegrationpoints shows incorrect values for authentication feature
Description:		The outboundintegrationpoints IP is not always showing the correct value for authenticationFeature when OAuth is used
Resolution:		For ClaimsEventClient and Activity IP in claims, if the authentication feature is set to OAuth, the same will reflect as default values for authentication feature of each use case unless an override for each use case is specified.
36547166	3-34871101921	NXT-29240	Invoking exchange with filename containing diacritics corrupts created datafile name
Description:		Invoking exchange with file upload, where the filename contains diacritics, erroneously transforms the filename to some other characters.
Resolution:		By incorporating standard encoding for UTF-8 and ISO_8859-1 in multiform requests, filename with diacritics is not getting corrupted.
Backports:		4.23.1.0.8, 4.23.2.0.2
36413749		NXT-28073	Claim Callout History details are not displayed on Claim History Panel when toggle button 'Display Claim Callout History' is on
Description:		When a claim with Callout details is selected, the same must be visible in the Claim History drawer when 'Display Claim Callout History' is toggled on. However, the Callout details were not being displayed.
Resolution:		When a user selects a claim with Callout details, and toggles the 'Display Claim Callout History' to On state, a dropdown with the Callout title is shown under which a table displays the Callout details.
Backports:		4.23.2.0.2
36967405		NXT-30183	ID of single value flex code is returned as "null" (String) in the generic API response
Description:		ID of single value flex code is returned as "null" (String) in the generic API response.
Resolution:		ID attribute of single value flex code is now excluded from the generic API response (same behaviour as the previous release).
36949846		NXT-30158	Member lookup not working in claims
Description:		Member lookup when no label is present wasn’t working properly, that is on click of lookup icon,look-up wasn’t being shown on screen.
Resolution:		Member lookup when no label is present is working properly, that is on click of lookup icon,look-up is shown on screen.
35143144		NXT-26549	Create configuration migration set overwrites existing sets
Description:		In the JETUI, if a new configuration migration is created and a code is used of a CMT set that already exists, the existing migration set is overwritten with the data of the "new" set. The expectation is that saving that "new" set would fail because there already is an existing set with that code.
Resolution:		Saving a "new" config migration set will fail when there is an existing set already with that code and shows error message
36521619	3-36416661851	NXT-29199	Conditional Filter doesn’t work in create mode even though object state is declared always
Description:		When an initcondition is configured on a floorplan that changes the value of the filter property on a reference field, even though the condition is configured with object state "always" but the filtering only works correctly in the edit state, filtering doesn’t work in create mode.
Resolution:		init condition configured with objectstate:always to update the filter value of a reference field works both in create and edit mode.
36456415	3-36247582081,3-36912613781	NXT-29088	NEQ query operator & boilerplate issue in claims search page
Description:		NEQ query operator not working in advanced search. "queryOperator":"neq" is not working and have incorrect boilerplate text
Resolution:		Added support for neq for all datatypes in advance search
Backports:		4.23.1.0.8, 4.23.2.0.2
36195686		NXT-28518	All records are not shown in downloaded file, only 10 records are shown even after scrolling in table page
Description:		When a user scrolls through a set of records and clicks on download action in the table, the downloaded file doesn’t show the correct result.
Resolution:		All the records viewed in the table page is downloaded to the file when clicked on download action
Backports:		4.23.2.0.2
36220190		NXT-28578	Relation Links aren’t removed for a relation when empty list is given as payload
Description:		Unable to delete Relation Links by giving empty relation link list as payload for Persons IP.
Resolution:		Relation Links can be deleted by giving empty relation link list as payload in case of Persons IP.
35684712		NXT-27299	For certain special LOV properties configured in the floorplan with suffix 'JET' ,upon selecting a value, the focus moves out of the table row
Description:		On selecting a value from dropdown for special functional LOV properties in table pages, the focus moves out of the table row
Resolution:		On selecting a value from dropdown for the special functional LOV properties in table, the focus remains on the respective field.
35143149		NXT-26550	Create configuration migration set overwrites existing sets
Description:		In the JETUI, if a new configuration migration is created and a code is used for a CMT set that already exists, the existing migration set is overwritten with the data of the "new" set. The expectation is that saving that "new" set would fail because there already is an existing set with that code.
Resolution:		A new parameter "isNew" is added to dataexchange IP which is set to true when creating a new configmigration set and false when updating an already existing set. When this flag is not set, the ip defaults to its previous behavior that is create and update.
36221806	3-35456928411	NXT-28584	User is not able to create External Intervention Rule with Claim Type as blank
Description:		When External Intervention Rule is saved with Claim Type as blank, it gets created with the default Claim Type P.
Resolution:		External Intervention Rule can now be saved with Claim Type as blank.
36261246		NXT-28669	Resolve Pend reason is not working from Claim Line level when the claim line is configured as Tab in Claims floorplan
Description:		When a claimline is configured as tab in claims floorplan, and user tries to resolve pend from claim line level, it does not work and throws console error.
Resolution:		Resolve Pend reason works fine at Claim Line level when the claim line is configured as tab in Claims floorplan
Backports:		4.23.2.0.1
36083975	3-35014512371	NXT-28226	External consumption on sublimit does not create counter period for its composite limit
Description:		As per current OHI behaviour, when an external consumption creates a counter period for an annual or calendar year sub limit counter, it does not create a corresponding counter period for the composite limit. Only the consumption is added to the composite limit counter.
Resolution:		Counter periods are now created for composite limits as well
Backports:		3.22.2.0.19, 4.23.1.0.8, 4.23.2.0.2
36203926	3-34786906091	NXT-28539	Dynamic logic byte code is not loaded during server startup on non master nodes after invalidateall IP is invoked
Description:		Dynamic logic byte code is expected to load at the startup of non-master nodes if the invalidateall API was invoked in master node but was not being observed.
Resolution:		Dynamic logic byte code is now loaded at the startup of non-master nodes if the invalidateall API was invoked in master node.
Backports:		4.23.1.0.4, 4.23.2.0.1, 3.22.2.0.17
36261477	3-35639469161	NXT-28666	Changes are not saved for the code and description of an existing CMT Set in Jet UI
Description:		When changing the code and description of an existing CMT Set in JET UI the message 'Changes are saved successfully' appears but the changes are not stored.
Resolution:		Code, Description can be updated for an existing CMT Set and changes are saved successfully
Backports:		4.23.1.0.4, 4.23.2.0.1
36300635	3-34786906091	NXT-28748	Claim takes more time from INITIAL to PRICING DONE if one or more claim lines are denied
Description:		Claim takes more time from INITIAL to PRICING DONE if one or more claim lines are denied
Resolution:		When claim lines are denied, claim line rule coverages that are created initially are removed later on, which was causing OptimisticLockingException. This resulted in the entire claim flow to be processed twice. This is optimized now.
Backports:		4.23.1.0.4, 4.23.2.0.1, 3.22.2.0.18
36284999	3-35695968321	NXT-28721	Dynamic field value is getting wiped off and not holding the data upon save and also title is not displayed
Description:		When a dynamic field is of string type, converted to Lov field and attached to Dynamic record and used as a detail page, the value selected is not retained on the page, also, when that field is used to display title of the page, the title is not displayed.
Resolution:		The selected value from LOV is retained and page is saved, also the selected value is displayed in title of the page
Backports:		4.23.1.0.4, 4.23.2.0.1
36925022		NXT-29957	Unable to close a Deeplink drawer in search object pages
Description:		When a Deeplink is configured in a search page, the corresponding drawer opens but the user is unable to close the drawer using the close icon. The page also throws an error.
Resolution:		The user can configure a Deeplink drawer in a search page, opening and closing the drawer works as expected using the buttons provided.
36315309	3-35684326321	NXT-28797	Gathering statistics on technical table for every extract activity is inefficient
Description:		Gathering statistics on technical table for every extract activity is inefficient as it was enabled by default for all cases and because of parallel extracts performance was degraded.
Resolution:		A check is added which will ensure statistics are gathered only in certain cases. Hence, improving the efficiency of extract activity.
Backports:		4.23.1.0.5, 4.23.2.0.1, 3.22.2.0.18
36406047	3-35993367661	NXT-28983	Currency issue in jet page when creating a parameter for a product benefit specification
Description:		Currency is sent as "USD" in request payload irrespective of currency sent in "type" column in UI , while creating a limit parameter for a Product Benefit Specification. Hence when any user who doesn’t have USD currency, error is showing as "Currency code USD is unknown"
Resolution:		Currency is sent as it is seen in "type" column in UI , while creating a limit parameter for a Product Benefit Specification and no error is seen while saving
Backports:		4.23.2.0.1, 4.23.1.0.6
36337333	3-37140647951	NXT-26067	Retrieval access restrictions Brand/Payer
Description:		Retrieval access restrictions for Brand/Payer are not present in API, when the brand/payer is restricted, you can get the claim with the API
Resolution:		We have added brand and payer access restriction on retrieval of a claim and its related entities such as claimLine, claimMesssage, claimLineMessage, etc. Now these records will not be accessible through API without proper access roles granted to the user.
36500097		NXT-29162	The claim lines are not sorted based on sequence similar to ADF
Description:		IN ADF, the claim lines are sorted based on sequence which is of number datatype, whereas in JET, the default sorting is on Code which gets a copy of value in sequence when left empty, and as this is a string field, so not working similar to ADF.
Resolution:		Claim lines are sorted now based on 'Sequence' by default
36150504		NXT-28391	Individual providers - Unable to edit service address configured as deeplink in rendering address tab
Description:		It is not possible to edit resources which are configured as Deeplinks. For example in Individual providers, it is not possible to edit service address in rendering address tab. On click of edit button in service address drawer, its directly navigating back to individual providers page and not possible to edit/save
Resolution:		Edit works fine in Deeplink drawers now and also the values are saved properly on the resource configured as deeplink
Backports:		4.23.2.0.1
36150775		NXT-28395	Add auto select feature to a field when only one result is available for LOV
Description:		Auto select of single result lov value only works when the lov has fetched that value and then you tab out else if the response has not yet come, the lov goes blank as soon as you tab out.
Resolution:		Auto selection of value for a lov field works fine when doing a tab out and single result is available
Backports:		4.23.2.0.2
36127587	3-35023479031	NXT-28314	Custom lov on existing resource is throwing an error in payers page
Description:		Create a new LOV with page name other than resource name. Try to refer the new LOV from a new page. Add a new record. Error is thrown
Resolution:		Add new record shows the page correctly without any error when a custom lov is configured
35722669		NXT-27518	Generate baseviews fails intermittently with CacheCreationException
Description:		Generate baseviews fails intermittently with CacheCreationException: Name of the cache entityNamePropertyCache already exists.
Resolution:		Generation of base views works fine without any intermittent exceptions.
Backports:		4.23.1.0.4, 4.23.2.0.1
36446587	3-36208346711	NXT-29068	Query to fetch errorred tasks of a claim runs very slow
Description:		Query to fetch errorred tasks of a claim runs very slow after upgrading to 4.23.1.0.4/4.23.1.0.5 patch
Resolution:		The statistics were associated for ohi_return_collection and now the query to fetch errored tasks runs faster
36515122	3-36366863461	NXT-29187	Evaluate condition not working on dynamic records in create mode
Description:		The evaluate condition is not working on dynamic records during create mode, but it works in view and edit mode.
Resolution:		Evaluate condition can be configured on dynamic records as well and it works fine in create and view-edit mode
Backports:		4.23.1.0.8, 4.23.2.0.2
36555032	3-36476824771	NXT-29253	Non-matched fields are not cleaning up once a match has been made.
Description:		Non matched field "Service Entity Code" is not cleared up when a matching Service Member is added to the claim.
Resolution:		Non-matched fields 'Service Entity Code' and Type are cleaned up once a matching Service Member is added to the claim
Backports:		4.23.2.0.2
36168202		NXT-28439	Payment Status callout property defaults to true
Description:		Payment Status callout property defaults to true in Training environment.
Resolution:		Payment Status callout property (ohi.ws.paymentstatusresponse.request.enabled) now defaults to false. If needed it should be enabled by setting the property value to true.
36377364		NXT-28945	Save and cancel shortcuts aren’t working for create Hierarchical Recursive pages
Description:		The save and cancel shortcuts did not work for the create Hierarchical Recursive pages
Resolution:		The save and cancel shortcuts now work for the create Hierarchical Recursive pages
Backports:		4.23.2.0.1
36270903		NXT-28688	If a mandatory multivalue field is present after editing a claim and selecting value in one of the field in 'Additional fields, not able to save claim
Description:		When a page has MVNTV field present and also filled in, moment we navigate to additional fields drawer and fill value in any of the field, after coming back to claim details page, save is not working and throwing error "At least one record is required for JET_MVNTV_CHAR_01" though the value is already present.
Resolution:		There is no error thrown when modifying values in Additional Fields section which contains mandatory multivalue field
36440067		NXT-28278	Lot of whitespace is observed when an error message appears on the page
Description:		Lot of whitespace is observed when an error message appears on the page
Resolution:		Fixed error message white space issue
36740443	3-37077371621	NXT-29600	Unable to add usages under the external claims data floor plan
Description:		Unable to add usages under the External Claims Data floor plan when Auto Include Extensibility is not set.
Resolution:		Users can add usages under the External Claims Data floor plan when Auto Include Extensibility is not set to true
Backports:		4.23.2.0.2
36715694	3-36973417771	NXT-29547	Custom property in rule parameters tab of product benefit specification is not working
Description:		Go to 'Product Benefit Specification' → Click on 'Rule Parameters'. Add values for all fields, you will observe that the field 'Type' is not editable
Resolution:		Type field in Product Benefit Specifications page is editable and the dropdown displays values % and currency which can be selected.
Backports:		4.23.2.0.2
36654248	3-36452370811	NXT-29424	Advanced search lov’s for dynamic fields are not loading in referencesheetlines
Description:		Not able to search using the LOV’s in the reference sheet lines page. When clicking in the LOV field an error occurs on the api/generic/flexcodes/search.
Resolution:		Proper results are displayed in the LOV for flexcodes based on diagnosis, procedures and providers, displays
Backports:		4.23.1.0.8, 4.23.2.0.2
36747685	3-36980756861	NXT-29612	Parameter name is not working as a variable in Links Component
Description:		Configure links component with parameter in any View Edit Hierarchical recursive floorplan The parameters configured are not getting substituted, its expecting the parameters to be (params0,prams1,params2 etc)
Resolution:		External Links can be configured in JET and parameters can be used in the URL in any format. Also URL can be mentioned in the floorplan or as a system property. It works now in both the ways
36823193		NXT-29757	Integer field values are shown with separator (12,345 instead of 12345)
Description:		Enter '12345' in integer fields like "house number" or state and country code" in Persons page, it is getting displayed as 12,345
Resolution:		Integer field values are shown without separators now
36824156		NXT-29764	WLS managed node doesn’t start on time and hangs occasionally during startup
Description:		When the WebLogic nodes are restarted, one of the nodes hangs occasionally (not always the case) as the threads associated with activity processing are not initialized because the property caching was not completed.
Resolution:		When the Auto wiring does not happen properly in the class ConfigurableTheadPoolProcessor, the thread count cannot be set during the initialization of the class. Now thread count is set after the class is initialized, ensuring the server does not get stuck in the starting state.
Backports:		3.22.2.0.20
36651700	3-36632413411	NXT-29413	Validation for claim line message isn’t working while trying to add multiple claim lines.
Description:		Validation for claim line message isn’t working while trying to add more claim lines. UI allows user to save a claim line without message attached.
Resolution:		Validation gets triggered for claim line message while trying to add claim line
36675508	3-36864108701	NXT-29483	Issue with display of flexcodes in piechart for widget
Description:		Create a piechart widget with grouping criteria set on flex codes. Piechart doesn’t show flexcode names instead shows FlexCodeDomain(..)
Resolution:		PieChart widgets shows flexcode names properly when set as grouping criteria
Backports:		4.23.2.0.2
36794968		NXT-29636	Page doesn’t reload after adding a record in Insurable Entity Type page.
Description:		Navigate to insurable entity type page and add a record. Save the record without clicking on check icon. Save successful message is displayed but page doesn’t reload, with the new record still in editable mode
Resolution:		Newly added rows are saved and page reloads in view mode
Backports:		4.23.2.0.2
36371005	3-36983961191	NXT-28921	No base views are generated for Insurable entity and Insurable person tables
Description:		Base view generation for OHI_INSURABLE_ENTITIES and OHI_INSURABLE_PERSONS tables was disabled.
Resolution:		Base view generation for OHI_INSURABLE_ENTITIES and OHI_INSURABLE_PERSONS tables has been enabled.
36444934		NXT-29066	Clicking on view all notes link opens multiple tabs
Description:		Clicking on view all notes link opens multiple tabs
Resolution:		Clicking on view all notes link doesn’t open multiple tabs.
36908576	3-37579890441	NXT-30038	Manual benefits page does not show the coverage labels and amounts
Description:		Manual benefits page does not show the coverage label, amount and numberOfUnits fields while opening the ManualBenefits dialog for every claimline.
Resolution:		Values for coverage label, amount and numberOfUnits fields are shown in Manual Benefits dialog.
36900075	3-37458376621	NXT-30013	Selection dropdown is not showing certain fields even though added in the LOV
Description:		Selection dropdown is not showing certain fields even though added in the LOV floorplan for Primitive types
Resolution:		Selection dropdown displays all the fields added in the LOV floorplan for Primitive types.
36902947	3-37458376637	NXT-30024	Conditional filter on LOV for primitive types is not getting picked up
Description:		The conditional filter on LOV for Primitive Types is not getting picked up. Direct filters for LOVforPrimtiveTypes works fine but conditional filter is not working
Resolution:		The conditional filter on LOV for Primitive Types is implemented now
36926778	3-37575252321	NXT-30083	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:		Should generate financial message without any error. DB type ohi_id_code_rec_tp ID column definition changed to number (19,0).
36962594		NXT-30094	Nothing is showing up on click of summary button in claim line
Description:		Navigate to claims page and fetch any of the claim which has claim lines. Open any of the claim line and click on summary button. nothing is showing up on click of summary button
Resolution:		Claimline summary drawer opens on click of summary button in details page
36482408	3-35917534861	NXT-29134	Claimline sequence should be added for new row based on the maximum sequence available
Description:		ClaimLine sequence for newly added row must be set based on max sequence existing and incrementing it by one. When a claim has 5 claimlines and claimline 4 is deleted and a new one is added, JET shows error message that Claimline-5 already exists since JET calculates the sequence based on number of rows present.
Resolution:		Claimline sequence for a newly added row is calculated based on the maximum sequence available and incrementing by 1 for every new row.
Backports:		4.23.2.0.2, 4.23.1.0.6
36300118	3-35684326321	NXT-28747	Data from technical table is not cleaned up if an extract activity fails which leads to data accumulation
Description:		Data from technical tables were only getting cleaned for activities in 'CO' status. Which was causing accumulation of huge data.
Resolution:		Along with status 'CO' all other statuses except 'IN', 'IP' and 'QD' are now included as part of cleaning process. This ensures a more cleaner technical table, hence overcoming the issue of data accumulation
Backports:		4.23.1.0.8, 4.23.2.0.2
35721329		NXT-27515	Checkbox is not getting checked by default in UI using conditional display in table pages
Description:		In Financial Holds page, the checkbox 'Release?' should stay checked once it is checked. We can release the hold by selecting it once, but it doesn’t keep it showing as selected.
Resolution:		Release checkbox shows as selected in Financial Holds page and can release the hold
36243825		NXT-28623	SQL execution plan to delete high volume selected financial transactions is inefficient
Description:		SQL execution plan to delete high volume selected financial transactions (at the end of generate financial messages activity) is inefficient
Resolution:		The SQL is optimized
36376099	3-35829843481	NXT-28942	Attach and next button is not working for providers and payer page
Description:		create custom page/tab from Individual/Organization provider page and from payer. The "Attach and Next" functionality is not working from both the pages. When we add multiple records using attach and Next, only first record is getting saved. Other record is replacing with first record for Payer and getting errored and blanked out for IND/ORG provider
Resolution:		Attach and next button works as expected for providers and payer page
36504269	3-36403867421,3-36474555451	NXT-29166	Number fields in dynamic records are parsed incorrectly, when the accept language is passed.
Description:		The individual number field is interpreted correctly (as an english formatted number), but the number fields in the dynamic record are interpreted according to the language setting.
Resolution:		Number field in the dynamic record should not be parsed according to the language setting.
Backports:		4.23.1.0.7, 4.23.2.0.2
36154603	3-35164428231	NXT-28408	Fee Schedule Procedures requests are encountering - GEN-PROC-ERR
Description:		When the number of fee schedule lines exceeds 1000 for a specific fee schedule and procedure, the update of fee schedule lines using feescheduleprocedures IP gives the below error: 'ORA-01795: maximum number of expressions in a list is 1000'
Resolution:		In the during the processing of IP call a select query is called which used to have all associated feeScheduleLines ids in where in clause, which would throw error if they were more than 1000. Now the query runs with 1000 items at a time, thus avoiding the database exception.
Backports:		4.23.1.0.2, 4.23.2.0.0
36443543		NXT-27497	New row doesn’t get into editable state in Financial holds page
Description:		The new row doesn’t get into an editable state on object navigation link table pages, the user has to double-click on the element or click on the edit icon to do so. Due to that add button is enabled all the time and user can add multiple rows without adding mandatory data into the previously added row.
Resolution:		New row is added in editable state in Financial holds object navigation link in claims page
36463104		NXT-29099	Flexcodes API returns value of ID as number instead of String
Description:		Flexcodes API returns the value of id as a number instead of String but the definition defined the type of ID as string
Resolution:		The Flexcodes API now returns value of Id, created by and last updated by as Strings as defined in the definition
Backports:		4.23.2.0.1, 4.23.1.0.6
36210563	3-35499768621	NXT-28559	Length of OHI_ID_ARRAY database type is still 14 after upgrading to 4.23.1 release
Description:		Length of OHI_ID_ARRAY database type is still 14 after upgrading to 4.23.1 release
Resolution:		The length of OHI_ID_ARRAY database type is updated to 19
Backports:		4.23.1.0.4, 4.23.2.0.0
36491994	3-36178158771	NXT-29144	PII data is not correctly populated when setting corresponding property
Description:		PII data is filled in as NULL when setting property "ohi.baseview.exclude.pii" to false, even though they are not null. This is only the case for entities where certain attributes are PII if the entity is of a certain subtype, e.g. for Relation of subtype 'PERS', the code column is seen as PII. When the "ohi.baseview.exclude.pii" property is set to false, this data should be seen.
Resolution:		PII data is now correctly populated when setting property "ohi.baseview.exclude.pii" to false.
Backports:		4.23.1.0.8, 4.23.2.0.2
36593623		NXT-29325	Remove the usage of utl_tcp DBMS package in extract functionality
Description:		Using utl_tcp DBMS package requires explicit grant in SaaS environments. This has operational challenges as the grants that are explicitly granted are periodically revoked by DBA as part of a scheduled process
Resolution:		Removed the usage of utl_tcp DBMS package in extract functionality and replaced it with a standard DB function
Backports:		4.23.1.0.8, 4.23.2.0.2
36382342		NXT-28952	Additional Fields at tab level is not retrieving the data.
Description:		The data of extensible fields under the more action drawer in a tab table is not showing up even after save.
Resolution:		The data of extensible fields under the more action drawer in a tab table is displayed properly after the save operation is performed.
Backports:		4.23.2.0.1
35742644	3-33777769061	NXT-27552	If a Claim Line hits a Daily Limit, OHI publishes the message associated with the authorization limit instead of the Daily Limit
Description:		This issue is in both ADF and JET. First, create an Adjudication Limit, then Create a Reservation and create a claim; repeat this step. You will see a message associated with the authorization limit instead of the Daily Limit.
Resolution:		The system throws a message per limit, by design, however the message did not mention the limit at all. Now, we have added an additional placeholder value to the reservation regime messages, that mentions the description of the limit. The description of the limit The associated changes have been made to the documentation.
35878047	3-34410216941	NXT-27808	Non-selective criteria in reference objects cause OHI to load too many objects in memory.
Description:		Non-selective criteria in reference objects cause OHI to load too many objects in memory.
Resolution:		Non-selective criteria in reference objects now only load two objects in the memory, which will not cause the memory protector to kick in.
Backports:		4.23.1.0.4, 4.23.2.0.2, 3.22.2.0.17
36189017		NXT-28464	ReferenceSheetLine generic API may return incorrect root element in the response for XML type
Description:		ReferenceSheetLine generic API may return incorrect root element in the response (if Accept header is set to application/xml) if the resource name of more than one reference sheet starts with the same value
Resolution:		Instead of checking only partial resource name, now the system checks for exact reference sheet resource name
36181513		NXT-28458	When a claim page is configured with 5 sets, the fields are moved to different sets and only 2 sets are displayed
Description:		Create a Custom Claims floorplan to display fields in one of the section with 5 sets. Load the Claims Page. 5 sets are not displayed, rather fields are merged into different sets and only 2 sets are displayed.
Resolution:		When a page is configured with 5 sets, the fields are not moved to different sets and displayed properly in 5 sets
36433068	3-36176430291	NXT-29049	Dynamic records ID should be returned as string in the API response
Description:		The ID of dynamic records of resources are returned as number (Long) in the API response, they should be returned as String.
Resolution:		The Dynamic records ID was transformed from Long to String in the API response
Backports:		4.23.2.0.1, 4.23.1.0.6
36579265	3-34451198321,3-36261018021	NXT-29310	Dynamic logic cache is not invalidated when importing reusable logic
Description:		After importing the modified reusable logic, the dynamic logic cache is not invalidated and changes in reusable logic are not auto considered by dynamic logic that imports it.
Resolution:		After updating the reusable code, invoke 'invalidateall ' IP before executing the operation. Fix is documentation update.
36817118	3-37284209921	NXT-29752	Fields missing in claim line limit
Description:		The system floorplan for claim line limits is missing the following fields: coverWithholdCategory , reachedAction and aggregationLevel
Resolution:		New fields added for claim line Limits(Cover With hold Category , Reached Action and Aggregation Level )
36398435	3-36004628854	NXT-28980	Edit field is present in referencesheet headers even after making the fields non editable in the floorplan
Description:		Edit field is present in REFERENCESHEET headers even after making the fields non editable in the floorplan. Enable the custom floorplan for REFERENCESHEET page and remove edit action from action component. The edit option is still there.
Resolution:		Edit button will not appear if edit action is removed from the floorplan in Reference sheets page
Backports:		4.23.2.0.1, 4.23.1.0.6
36498406	3-36339863591	NXT-29155	Cover Withhold amount with value 0 is not displayed
Description:		Multivalue having number fields set to 0 doesn’t display and CWC amount with value 0 is not displayed
Resolution:		Multivalues having number fields set to 0 displays and CWC amount with value 0 is displayed
Backports:		4.23.2.0.2, 4.23.1.0.6
36870711	3-37458989331	NXT-29944	Flex code fields are not displaying as columns in the search table of procedure lookup
Description:		When flex code fields are added to the procedure lov floorplan, it should be visible in search criteria as well as in the search results table of the procedure lov lookup window. It is not displayed as columns now.
Resolution:		Flex code fields appear in the search results table as well
36934010	3-37502780451	NXT-30098	In claims financials screen, payment details are not displayed
Description:		Users are not able to see/ edit the following in Claims JET UI: 1. Payment section 2. Edit due date under fields 3. Edit bulking group in the invoice section
Resolution:		Payment Information Sections displays data now, edit is possible for due date and bulking group in invoice section Note : Refresh action is added in Overview page to see updated information
36172449		NXT-28443	JWT bearer grant type is not working
Description:		OHI supports both client_credentials and urn:ietf:params:oauth:grant-type:jwt-bearer (shortly referred as JWT bearer) grant types in OAuth, however JWT bearer grant type is not working as expected.
Resolution:		Fixed logical issues in code to make it working
Backports:		4.23.2.0.1
36195580		NXT-28419	Incorrect result shown in Boilerplates Table
Description:		The boilerplate table shows incorrect results after performing the 'ADD' and then 'CANCEL' actions simultaneously. This behavior is generic to other table-based pages.
Resolution:		Correct results are shown after performing the 'ADD' and then 'CANCEL' actions simultaneously in table-based pages
36614536		NXT-29369	Translations not working in few pages
Description:		Following pages/buttons are not translatable: Persons page Actions dropdown, MenuItem for BookMarks GroupClients page - Set Status to Change Dialog text
Resolution:		Persons page Actions dropdown, MenuItem for BookMarks, GroupClients page - Set Status to Change Dialog text are translatable now
35814675	3-33232690791	NXT-27730	Applied benefits are not visible against claimlines
Description:		In the Enrollment response, if there is more than one product(previous product), the claim line is approved with 0 covered amount, and applied benefits are not shown against claimlines.
Resolution:		Issue occurred since regime specification had a previous product (past/expired one). Hence now the condition has been added to check if regime specification product id is same as existing product Id.
Backports:		4.23.1.0.4, 4.23.2.0.1, 3.22.2.0.18
36158083		NXT-28420	Init Condition - Default property is not working for LOV fields
Description:		Default value configured in floorplan for LOV fields is not applied ( displayed in UI) when used with init conditions
Resolution:		Default value configured in floorplan for LOV fields and dynamic records gets displayed in UI with init conditions
Backports:		4.23.2.0.2
36158118		NXT-28410	False condition for init condition on multivalue nontimevalid DYN record is not working for custom tabs if sequence is not set to 1
Description:		Configured persons floorplan to add additional custom tab in which init condition is defined. When the page has all the existing tabs along with this new custom tab, init condition is not working, but when only custom tab is kept, init condition is working fine
Resolution:		Init condition on multivalue nontimevalid DYN record works fine for custom tabs irrespective of tab sequence when condition evaluates to False
36423175		NXT-27849	Provider pricing clauses can be saved without start date
Description:		Provider pricing clauses can be saved without start date
Resolution:		Start date is now mandatory for Provider pricing clauses. Business rule PRI-DPPC-026 has been deprecated.
36457889		NXT-29091	QD status activities are not set to TE during system startup
Description:		Activities that were not processed and in 'QD' status before system down, are not setting up to status 'TE'
Resolution:		During system startup, activities which are in status 'QD' will be set to status 'TE'
Backports:		4.23.2.0.2
36614578	3-36759433791	NXT-29370	Conditional evaluation is not working on primitive type LOV fields
Description:		Conditional evaluation is not working on primitive-type LOV fields while referencing any of the properties of lov selected.
Resolution:		Conditional evaluation is working on primitive type LOV fields.To enable field1 to have the entire context of the selected LOV value, we add a new attribute to the entity (context of the parent resource). This new attribute will be named 'name_of_FieldObj'. For the example above, it will be 'field1Obj', which will contain the entire context of the selected LOV value. This allows us to conditionally evaluate various scenarios by accessing context.field1Obj.code, and other similar fields.
Backports:		4.23.1.0.8, 4.23.2.0.2
36506837		NXT-29180	Unable to update the provider limits amount using the UI
Description:		When user updates the provider limit rule using the UI, the amount is not being saved resulting in the UI error: "PRI-PLHE-001: The provider limit height must specify a maximum & Amount"
Resolution:		No errors while updating the provider limits amount using the UI
Backports:		4.23.2.0.2
36372050		NXT-27498	Alignment issue in LOVs with Enums
Description:		Alignment issues are seen in LOVs where there are nested values.
Resolution:		Alignment issues are corrected in Nested LOVs. LOVs show the correct alignment with 1 or more nested properties
36841537		NXT-29406	Values under pricing and benefit sections are not displayed under Claim Line Summary drawer for both working copy and CTR version
Description:		Values under pricing and benefit sections are not displayed under Claim Line Summary drawer. Also, navigate to claim line detail page and check the summary, the values are not displayed when we select any CTR version , but displayed in case of working copy
Resolution:		Fix added to show Pricing and Benefits section under claimline summary that opens on clicking more link
36441584		NXT-27653	Benefits section is not showing data when only reservation applies
Description:		When only a reservation benefit specification is applied to the claim line, user cannot get to the Applied Benefits. The claim line summary shows No Benefits Data Available, and no Show more link is available to go to the Applied Benefits
Resolution:		Show More link is renamed as Other Details link under claim line summary Pricing and Benefits section, which is visible under benefits section when there are reservation details or there are benefits applied.
36841243		NXT-29401	Messages don’t return the variable details
Description:		Messages don’t return the variable details in claim header summary and drawer, even though they are being returned by API
Resolution:		Messages display the variable details in claim header summary and claimline summary drawer
36844295	3-37314698941	NXT-29898	Unable to add claim subline on a claim line
Description:		For a claim, unable to add claim sub line under a claim line.
Resolution:		User can now add claim sub line from UI and API.
36611305		NXT-29363	No base view is generated for OHI_INTERFACED_MESSAGES in claims
Description:		In claims, there is no base view OHI_INTERFACED_MESSAGES_BV created for OHI_INTERFACED_MESSAGES.
Resolution:		Base view OHI_INTERFACED_MESSAGES_BV is created for OHI_INTERFACED_MESSAGES table.
36464225		NXT-29102	Shortcuts don’t work for configuration migration sets pages
Description:		Shortcuts don’t work for configuration migration sets pages.
Resolution:		Fix provided to support Keyboard Shortcut Actions for Configuration Migration Sets page
36739512	3-36913840401	NXT-29596	Extract requests can have a limited number of characters in the condition
Description:		Extract request with a large query fails with activity message "ORA-06502: PL/SQL: numeric or value error ORA-06512: at line 1". This is because the selection is stored in a variable with a maximum of 32000 characters.
Resolution:		Selection is now stored as a clob of which the maximum size depends on environment settings: (4 GB - 1) * DB_BLOCK_SIZE initialization parameter (8 TB to 128 TB). Contact database administrator for more details if needed. This change allows for a more extensive query in the extract request and a lesser chance of running into the ORA-06502 error.
34857101		NXT-25929	Additional fields drawer: Apply button not responding and Client side error not shown for mandatory fields
Description:		In Claims page after clicking on drawer of additional fields. Fill few fields and try to apply but is not responding. This issue has come up because we have a mandatory field to be filled in Additional Fields and the user is not notified with this, by scrolling down to fill in those fields.
Resolution:		Client side validation is highlighted in Additional Fields drawer
36448721		NXT-29074	In Product benefit specification page, rule parameters type should be lov
Description:		Select and view any product benefit specification, Add new to Rule parameters tab. Field type should be LOV but is shown as text field.
Resolution:		Field 'type' in Product benefit specification page, rule parameters tab is shown as lov dropdown
Backports:		4.23.2.0.2
36908487	3-37567131801	NXT-30036	NoClassDefFoundError error is returned when creating a new dynamic logic with trace logging enabled for the logger ohi.dynamiclogic
Description:		A NoClassDefFoundError occurs when attempting to create a new dynamic logic with trace logging enabled for the ohi.dynamiclogic logger, instead of successfully creating the dynamic logic.
Resolution:		After adding the missing third-party dependency, dynamic logic can now be successfully created with trace logging enabled for the ohi.dynamiclogic logger.
36945747	3-37403675211	NXT-30133	Accessing reference sheet lines via the post search operation requires more than just retrieve access to the Reference Sheet Lines API.
Description:		Accessing reference sheet lines via the POST search operation requires both retrieve and create permissions on the Reference Sheet Lines API. Simply having retrieve access is insufficient to perform this operation.
Resolution:		Accessing reference sheet lines using the POST search operation now only requires retrieve access.
36423153		NXT-25302	Unable to display address of a person in create mode.
Description:		When address is configured as a sub-property for a person, the address of the selected person is not shown in create mode.
Resolution:		When address is configured as a sub-property for a person, the address of the selected person is displayed under the person.
36337375		NXT-24714	Properties under claim form type definition is not present when accessed through location type groups
Description:		Properties under claim form type definition is not present when accessed through location type groups
Resolution:		Location Type Groups are now api expandable and claim form type definition can be accessed through location type groups
36189587		NXT-28467	Execute datafile incident scavenging job should be only done on the oldest node of cluster
Description:		The datafile set scavenging/cleanup job is scheduled to clean up application incidents (trace files). This spring scheduling job is executed on all the nodes, which is an unwanted use of resources, it is it would be efficient to run this only once
Resolution:		The datafile set scavenging/cleanup job is now done on only the oldest node of cluster.
35258896	3-34815761621	NXT-26737	Duplicate records are getting created when click on Attach and Next Button
Description:		Create a Claim with one claim line. Now, add another claim line with different info and click on Attach and Next Button. When we go back to claim line tab of claims page, the records of claim lines display duplicate records.
Resolution:		Attach and Next Button works as expected in detail pages and no duplicate records are created
35170337	3-32373573471	NXT-26619	Benefit counter units are not getting uploaded into OHI using write consumption
Description:		A null pointer exception is thrown when processing write consumption.
Resolution:		The request payload had an incorrect attribute currencyCode due to an error in the documentation. We have corrected the request body in the documentation, and also fixed the NPE coming when the currency is not specified.
Backports:		3.22.2.0.18

Issues that were backported in previous Release / Patch

BugDB	Internal	Summary	Backport	BugDB	SR
34008782	NXT-24457	Enrollment callouts throw a null pointer error on the read timeout	4.23.1.0.4	36251071	3-28606893871,3-35610906861
34008782	NXT-24457	Enrollment callouts throw a null pointer error on the read timeout	4.23.2.0.1	36251082	3-28606893871,3-35610906861
35170337	NXT-26619	Benefit counter units are not getting uploaded into OHI using write consumption	3.22.2.0.18	35201244	3-32373573471
35722669	NXT-27518	Generate baseviews fails intermittently with CacheCreationException	4.23.1.0.4	35722678
35722669	NXT-27518	Generate baseviews fails intermittently with CacheCreationException	4.23.2.0.1	36272194
35814675	NXT-27730	Applied benefits are not visible against claimlines	4.23.1.0.4	35825929	3-33232690791
35814675	NXT-27730	Applied benefits are not visible against claimlines	4.23.2.0.1	35826004	3-33232690791
35814675	NXT-27730	Applied benefits are not visible against claimlines	3.22.2.0.18	36320357
35878047	NXT-27808	Non-selective criteria in reference objects cause OHI to load too many objects in memory.	4.23.1.0.4	35878081	3-34410216941
35878047	NXT-27808	Non-selective criteria in reference objects cause OHI to load too many objects in memory.	4.23.2.0.2	36274923
35878047	NXT-27808	Non-selective criteria in reference objects cause OHI to load too many objects in memory.	3.22.2.0.17	35878079	3-34410216941
36413749	NXT-28073	Claim Callout History details are not displayed on Claim History Panel when toggle button 'Display Claim Callout History' is on	4.23.2.0.2	36704576
36083975	NXT-28226	External consumption on sublimit does not create counter period for its composite limit	3.22.2.0.19	36079080	3-35014512371
36083975	NXT-28226	External consumption on sublimit does not create counter period for its composite limit	4.23.1.0.8	36079076	3-35014512371
36083975	NXT-28226	External consumption on sublimit does not create counter period for its composite limit	4.23.2.0.2	36079071	3-35014512371
36150504	NXT-28391	Individual providers - Unable to edit service address configured as deeplink in rendering address tab	4.23.2.0.1	36150559
36150775	NXT-28395	Add auto select feature to a field when only one result is available for LOV	4.23.2.0.2	36150783
36194649	NXT-28399	Add new row is shown at the last in table pages	4.23.2.0.2	36194650
36154603	NXT-28408	Fee Schedule Procedures requests are encountering - GEN-PROC-ERR	4.23.1.0.2	36125708	3-35164428231
36154603	NXT-28408	Fee Schedule Procedures requests are encountering - GEN-PROC-ERR	4.23.2.0.0	36125696	3-35164428231
36158083	NXT-28420	Init Condition - Default property is not working for LOV fields	4.23.2.0.2	36158149
36172449	NXT-28443	JWT bearer grant type is not working	4.23.2.0.1	36307912
36195686	NXT-28518	All records are not shown in downloaded file, only 10 records are shown even after scrolling in table page	4.23.2.0.2	36195771
36203926	NXT-28539	Dynamic logic byte code is not loaded during server startup on non master nodes after invalidateall IP is invoked	4.23.1.0.4	36203944	3-34786906091
36203926	NXT-28539	Dynamic logic byte code is not loaded during server startup on non master nodes after invalidateall IP is invoked	4.23.2.0.1	36203938	3-34786906091
36203926	NXT-28539	Dynamic logic byte code is not loaded during server startup on non master nodes after invalidateall IP is invoked	3.22.2.0.17	36203955	3-34786906091
36210563	NXT-28559	Length of OHI_ID_ARRAY database type is still 14 after upgrading to 4.23.1 release	4.23.1.0.4	36210574	3-35499768621
36210563	NXT-28559	Length of OHI_ID_ARRAY database type is still 14 after upgrading to 4.23.1 release	4.23.2.0.0	36210577	3-35499768621
36261477	NXT-28666	Changes are not saved for the code and description of an existing CMT Set in Jet UI	4.23.1.0.4	36261010	3-35639469161
36261477	NXT-28666	Changes are not saved for the code and description of an existing CMT Set in Jet UI	4.23.2.0.1	36261004	3-35639469161
36261246	NXT-28669	Resolve Pend reason is not working from Claim Line level when the claim line is configured as Tab in Claims floorplan	4.23.2.0.1	36262726
36284999	NXT-28721	Dynamic field value is getting wiped off and not holding the data upon save and also title is not displayed	4.23.1.0.4	36285017	3-35695968321
36284999	NXT-28721	Dynamic field value is getting wiped off and not holding the data upon save and also title is not displayed	4.23.2.0.1	36285031	3-35695968321
36289743	NXT-28727	OAuth parameters should be configurable	4.23.2.0.1	36304156	3-34612052061
36300118	NXT-28747	Data from technical table is not cleaned up if an extract activity fails which leads to data accumulation	4.23.1.0.8	36393319	3-35684326321
36300118	NXT-28747	Data from technical table is not cleaned up if an extract activity fails which leads to data accumulation	4.23.2.0.2	36393308	3-35684326321
36300635	NXT-28748	Claim takes more time from INITIAL to PRICING DONE if one or more claim lines are denied	4.23.1.0.4	36300654	3-34786906091
36300635	NXT-28748	Claim takes more time from INITIAL to PRICING DONE if one or more claim lines are denied	4.23.2.0.1	36300644	3-34786906091
36300635	NXT-28748	Claim takes more time from INITIAL to PRICING DONE if one or more claim lines are denied	3.22.2.0.18	36300668	3-34786906091
36315309	NXT-28797	Gathering statistics on technical table for every extract activity is inefficient	4.23.1.0.5	36427800	3-35684326321
36315309	NXT-28797	Gathering statistics on technical table for every extract activity is inefficient	4.23.2.0.1	36427788	3-35684326321
36315309	NXT-28797	Gathering statistics on technical table for every extract activity is inefficient	3.22.2.0.18	36427802	3-35684326321
36377364	NXT-28945	Save and cancel shortcuts aren’t working for create Hierarchical Recursive pages	4.23.2.0.1	36377374
36382342	NXT-28952	Additional Fields at tab level is not retrieving the data.	4.23.2.0.1	36382380
36398435	NXT-28980	Edit field is present in referencesheet headers even after making the fields non editable in the floorplan	4.23.2.0.1	36445738	3-36004628854
36398435	NXT-28980	Edit field is present in referencesheet headers even after making the fields non editable in the floorplan	4.23.1.0.6	36399520	3-36004628854
36406047	NXT-28983	Currency issue in jet page when creating a parameter for a product benefit specification	4.23.2.0.1	36406065	3-35993367661
36406047	NXT-28983	Currency issue in jet page when creating a parameter for a product benefit specification	4.23.1.0.6	36406084	3-35993367661
36433068	NXT-29049	Dynamic records ID should be returned as string in the API response	4.23.2.0.1	36433071	3-36176430291
36433068	NXT-29049	Dynamic records ID should be returned as string in the API response	4.23.1.0.6	36433078	3-36176430291
36448721	NXT-29074	In Product benefit specification page, rule parameters type should be lov	4.23.2.0.2	36448741
36456415	NXT-29088	NEQ query operator & boilerplate issue in claims search page	4.23.1.0.8	36718881	3-36247582081,3-36912613781
36456415	NXT-29088	NEQ query operator & boilerplate issue in claims search page	4.23.2.0.2	36456432	3-36247582081
36457889	NXT-29091	QD status activities are not set to TE during system startup	4.23.2.0.2	36662916
36463104	NXT-29099	Flexcodes API returns value of ID as number instead of String	4.23.2.0.1	36463125
36463104	NXT-29099	Flexcodes API returns value of ID as number instead of String	4.23.1.0.6	36463130
36482408	NXT-29134	Claimline sequence should be added for new row based on the maximum sequence available	4.23.2.0.2	36482471	3-35917534861
36482408	NXT-29134	Claimline sequence should be added for new row based on the maximum sequence available	4.23.1.0.6	36482478	3-35917534861
36491994	NXT-29144	PII data is not correctly populated when setting corresponding property	4.23.1.0.8	36492014	3-36178158771
36491994	NXT-29144	PII data is not correctly populated when setting corresponding property	4.23.2.0.2	36492013	3-36178158771
36498406	NXT-29155	Cover Withhold amount with value 0 is not displayed	4.23.2.0.2	36498472	3-36339863591
36498406	NXT-29155	Cover Withhold amount with value 0 is not displayed	4.23.1.0.6	36498474	3-36339863591
36504269	NXT-29166	Number fields in dynamic records are parsed incorrectly, when the accept language is passed.	4.23.1.0.7	36568116	3-36403867421,3-36474555451
36504269	NXT-29166	Number fields in dynamic records are parsed incorrectly, when the accept language is passed.	4.23.2.0.2	36504475	3-36403867421,3-36474555451
36506837	NXT-29180	Unable to update the provider limits amount using the UI	4.23.2.0.2	36506848
36515122	NXT-29187	Evaluate condition not working on dynamic records in create mode	4.23.1.0.8	36515179	3-36366863461
36515122	NXT-29187	Evaluate condition not working on dynamic records in create mode	4.23.2.0.2	36515166	3-36366863461
36547166	NXT-29240	Invoking exchange with filename containing diacritics corrupts created datafile name	4.23.1.0.8	36562893	3-34871101921
36547166	NXT-29240	Invoking exchange with filename containing diacritics corrupts created datafile name	4.23.2.0.2	36562892	3-34871101921
36555032	NXT-29253	Non-matched fields are not cleaning up once a match has been made.	4.23.2.0.2	36557433	3-36476824771
36593623	NXT-29325	Remove the usage of utl_tcp DBMS package in extract functionality	4.23.1.0.8	36593627
36593623	NXT-29325	Remove the usage of utl_tcp DBMS package in extract functionality	4.23.2.0.2	36593624
36614578	NXT-29370	Conditional evaluation is not working on primitive type LOV fields	4.23.1.0.8	36619054	3-36759433791
36614578	NXT-29370	Conditional evaluation is not working on primitive type LOV fields	4.23.2.0.2	36618950
36654248	NXT-29424	Advanced search lov’s for dynamic fields are not loading in referencesheetlines	4.23.1.0.8	36654284	3-36452370811
36654248	NXT-29424	Advanced search lov’s for dynamic fields are not loading in referencesheetlines	4.23.2.0.2	36654270	3-36452370811
36675508	NXT-29483	Issue with display of flexcodes in piechart for widget	4.23.2.0.2	36675538	3-36864108701
36715694	NXT-29547	Custom property in rule parameters tab of product benefit specification is not working	4.23.2.0.2	36715702	3-36973417771
36740443	NXT-29600	Unable to add usages under the external claims data floor plan	4.23.2.0.2	36740454	3-37077371621
36794968	NXT-29636	Page doesn’t reload after adding a record in Insurable Entity Type page.	4.23.2.0.2	36794974
36824156	NXT-29764	WLS managed node doesn’t start on time and hangs occasionally during startup	3.22.2.0.20	36824302	3-35678279851

Known Issues

BugDB	SR	Internal	Summary
-		NXT-15947	Uppercase code not implemented in HTTP API
Description:		In cases were a code is always uppercase, the UI automatically transforms lowercase values to uppercase. The transformation to uppercase is not done in HTTP API. This is inconsistent and should be fixed.
32477460		NXT-22010	No base view generated for reference sheet lines
Description:		Reference sheet line(s) use a different storage structure (JSON) for the dynamic fields. The base view generator does not support that yet. So, the reference sheet line columns can’t be queried using base views.
-		NXT-22220	Introduce copy constructors for Financial Transaction Detail and its Process Data
Description:		It is observed that at the customer, there are many situations, where a financial transaction detail and its process data is created in the financial transaction logic. These details are often 90% copies of existing details. Today, they are all handcrafted with set<>(get<>) methods.
32945627		NXT-22704	The SetRecalculateBenefits function fails intermittently
Description:		While trying to set the amount on claimLineRuleCoverage using setAmountManually method, the amount is set to the desired amount on claimLineRuleCoverage. However, after recalculating benefits, the amount (cover label) on claimLineCoverages is not set to the desired amount. This issue is occurring intermittently.
33078317		NXT-22935	Duplicate cases get created when there is a past case date
Description:		There are a few scenarios of duplicate case creation when there is a past case date.
33430793		NXT-23460	Usages - Add to floorplan - When same usage is associated in all the sets of a floorplan, the values are not rendered properly on the entity’s page
Description:		When an 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. So there needs to be a reconfiguration check in place to handle this situation.
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
33654812		NXT-23946	Tasks for a claim stays in PENDING status on node failure or switchover
Description:		Tasks for a claim stay in PENDING status on node failure or switchover. The corresponding claims are stuck in Initial status.
33698723		NXT-24018	Mismatch in Dynamic Records not failing with an error
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	Filter with claimPendReasonList and claimLinePendReasonList is not working when added with or condition
Description:		The query "claimPendReasonList.pendReason.code.eq('MEDICAL').or.claimLineList.claimLinePendReasonList.pendReason.code.eq('MEDICAL') " doesn’t consider the claims in a result, which has pend reasons either at the claims level or claim line level. Claims that have pend reasons at both levels (claim & claim line) are included in the result.
34164741		NXT-24723	Outbound Exchange: Values are not getting updated after building a data set
Description:		When trying to build a data set, exactVersionMatch and disableDeleteByOmission are not getting updated. Also, If we try to update the inclusionDate by passing an empty value, it is not getting updated.
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.
34231559		NXT-24849	Reversal of a financial transaction that is sent out and marked mandatory gets the bulking group of that sent out transaction
Description:		Reversal of a 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.
34270456		NXT-24879	Claim’s start and end dates should be set based on claim line start and end dates when a claim is created or updated
Description:		Claim start and end dates are not populated based on the claim line’s start and end dates.
34401051	3-29621579461	NXT-25116	The CMT recovery process fails with a null pointer exception
Description:		During restart, the data set processes for CMT are cleaned up. As a result, the CMT recovery process fails with a null pointer exception.
34445139	3-30161147631	NXT-25161	In the test unit signature under dylo, we are unable to set values for a few objects.
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	Mandatory Record Fields are not tagged with mandatory or required tag in definition of respective resources.
Description:		A record definition is created with two mandatory fields. A record is created in the Persons resource with this record definition. In the API response, the metadata does not indicate that the two fields are mandatory as configured in the Record Definition.
34579024		NXT-25362	GEN_FIN_MSG_XML_BLK activity causes memory issues if there are more transactions with the same bulking group
Description:		The generate financial message activity creates one child GEN_FIN_MSG_XML_BLK activity for each distinct bulking group. Created child activity fetches the financial transactions, which has a bulking group and creates one financial message. If the bulking group is not set/not distinctive enough, this might cause performance (memory related) issues.
34875997		NXT-25987	Include claim line with null episode identifier and multiple episodes gets added to existing episode.
Description:		When an include claim line comes with null episode identifier and multiple time-overlapping episodes exists for the member, it gets added to an existing episode.
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, API has aliases with alias d for claimDiagnosis.diagnosis along with b for the brand; the brand code is not returned. However, if the diagnosis alias is removed or is not d, then the response is correct.
34938152	3-31591920981	NXT-26092	Provider entity fields of level greater than 1 cannot be fetched by claims resource
Description:		Fetching provider entity fields greater than 1 level deep from claims resource is not possible.
34967121		NXT-26155	On adding a new member through the 'add new?' link, the module doesn’t show all mandatory fields
Description:		Open create a claim. Click on 'Add new?'. Populate all fields that are shown as mandatory. Upon saving, we get an error to enter data into additional fields that weren’t mandatory, like name format, etc.
35000725	3-31898611651	NXT-26257	The multi-value flexcode for feeschedule is not being updated
Description:		When a multi-value flexcode is added to the feeScheduleLine via feeSchedule IP, f_eeSchedule_ is not being updated.
35018330	3-31969350441	NXT-26277	Query API cannot handle optional fields with flex code definition requesting combination with null
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	When the code and description of the Pricing worksheet is updated, error is thrown
Description:		In api, the error is thrown when we try to update the code - along with description or code alone. In ui, the error is thrown only when both code and description are changed. The logged error is same in both cases.
35056041		NXT-26369	NPE, when enrollment response, returns a product that does not belong to the claim brand.
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 logic not allowing to match between fee schedule line dynamic field and claim line dynamic field
Description:		FeeScheduleline dynamic fields are currently not accepted by fee schedule line condition dynamic logic.
36173196		NXT-26446	The deselection of claim lines is not working
Description:		Using option Select All, under claim lines tab, we can select all lines, but if we click this button again, the claim lines are not getting deselected. This is true for both list view and table view of claimlines
35242524		NXT-26709	Input passed to Episode Start Date dynamic logic works as triggering or include line
Description:		triggeringClaimLine in Episode Start Date dynamic logic works as triggering or include line.
35262820		NXT-26745	Counter period does not always created for calendar year external limit consumptions
Description:		Counter period does not always created for calendar year external limit consumptions.
35263469		NXT-26749	A carry-over counter period is not created for insurance limits that count per product per provider
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	Certain 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.
35350138	3-32828784691	NXT-26868	Dynamic record definition does not appear in reference sheet search result/advanced search
Description:		The Dynamic Record Definition field is not showing up in the reference sheet search result (Reference Sheet Search Page), and also, the user cannot search/Advance Search using it in JET UI (Despite adding it to the floorplan).
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		NXT-26979	Limit counters search does not return family counters when resource specifies or condition
Description:		Search on limit counters does not fetch 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 are not periodically committed as they are processed
Description:		The actual commit of the events happens 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	When multiple tags are configured in claim and claimline floorplans, claimline is not opening for one of the use case
Description:		when a custom claim floorplan has tag same as custom claimline floorplan which meets the context-based condition similar to ClaimLinesViewOnly, custom claim floorplan should be loaded but as that is already tagged with custom claimline floorplan, the respective claimline floorplan is trying to load, but when View icon of claimline is clicked, it throws error and claimline does not open up.
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".
35686780		NXT-27433	Reset Query Statistics - in Monitor Dynamic Logic Querying
Description:		When we query something in the testunit dynamic logic and then invoke/test another dynamic logic in the same testunit dynamic logic, the value/count for all query parameters displays incorrect
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>
35841806		NXT-27763	Claims entry page - benefits external checkbox returns error
Description:		The application returns a technical error, when checking the 'Benefits External?' checkbox in the UI when creating a version 2 of a claim.
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
35948308		NXT-27974	Not all provider limit counts are shown in the pricing pop-up dialog for a claim
Description:		Configure a claim with 2 claim lines, both counting towards the same provider limit. Finalize the claim. Both claim lines have a claim line message attached indicating the limit being applied but the pricing pop-up dialog only indicates that claim line 2 counted towards the limit.
36337417		NXT-28341	User shouldn’t be able to set a custom code for a shortcut
Description:		User shouldn’t be able to set a custom code for a shortcut. The Code has to be one of the seeded one.
36181357		NXT-28456	Alignment is broken when Single value or multi value field is configured in dynamic record with one of the fields having LOV value
Description:		The alignment of dynamic record fields are broken mostly in Edit mode depending upon which set or tile the fields are configured in.
36206119	3-34786906091	NXT-28549	Thread code of CtrClaimEvent task for a high priority claim may be incorrect sometimes
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.
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
36285086	3-34733739021	NXT-28722	Policies abruptly ending in Technical Error are not clearing the technical flag (TEC_IND_SUBMITTED) used for throttling
Description:		The technical flag (TEC_IND_SUBMITTED) used for activity throttling isn’t getting reset when sometimes activities end in a technical error (abruptly). This results in the queuing of new activities, which aren’t processed timely.
36329205	3-35746764831	NXT-28820	Procedure integration point gives a fatal error when updating a procedure
Description:		when a procedure is updated, the status returned is not the expected status
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.
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.
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	Resource auditing for limitconsumptions and providerlimitruleconsumptions APIs should be enabled
Description:		For adjudication counter and provider limit counter related entities, PHI logging needs to be enabled when POST search is performed on them.
36531389	3-36392583761	NXT-29211	Internal system user is used for resolving the claim pends via pend resolution batch IP
Description:		When pend reasons are resolved by the pendresolutionbatch IP, internal system user is used for resolving the claim pends. This is causing the IP to fail when access restricted pend reasons are resolved. Current user should be used to resolve the pends via pend resolution batch IP.
36989174		NXT-29239	AutoFetch is not working in search pages where sort is configured
Description:		AutoFetch is not working when search pages have Sort configured
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
36584465	3-36499732951	NXT-29313	Action of limit is not getting applied for Claim Line Limit for Reservation claim
Description:		Action of limit is not getting applied for Claim Line Limit for Reservation claim when arg3 in predefined method claimLine.setClaimLineLimit is null.
36588981		NXT-29319	Number and Date should not be converted based on Locale in API/IP requests
Description:		Date is being converted based on Locale value in API/IP requests which should not be done.
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 .
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.
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:		When a flex code field is configured with reftype property which has propertySelection = true, lookup option does not appear
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	Data replication of person with restrictetd relation identifiers fails with incomplete message
Description:		f you have a person with a relation identifier and that identifier type has an access restriction in both POL and CLA. But the access restriction is not assigned to the credential in CLA. error is logged
36765095		NXT-29642	Querying for data on a dynamic field with reference property return "id" as null
Description:		For SVNTV dynamic fields id is returned as null in Search Result.
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	BR CLA-FL-FINA-001 should be invoked after the currency conversion
Description:		BR should be invoked after currency conversion.
37003968		NXT-29773	Combination of quick search and advanced search isn’t working
Description:		When you search with some criteria in quick search & then add some 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
36988240		NXT-29776	Usages: Getting Null pointer error on converting SVTV to MVTV
Description:		Usages: Getting Null pointer error on converting SVTV to MVTV
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
36846356	3-37391765051	NXT-29905	CMT: inclusionDate, exactVersionMatch, disableDeleteByOmission are not applied when building CMT sets.
Description:		The parameters inclusionDate, exactVersionMatch, disableDeleteByOmission are not sent in payload while building CMT sets.
36881104		NXT-29962	Super entities - Providers/relations are not expanding dynamicData on search
Description:		Search on super entities - Providers/relations are not expanding dynamicData with the expand option in the request
36901735	OHISD-3644	NXT-30020	Widgets - Unable to update description for system specific entry
Description:		Widgets - Unable to update description for system specific entry
36902074	3-37468227341	NXT-30022	Few columns are not converting to PT language
Description:		Navigate to claims page - click on add card - code and description are not translated to PT language in Add widget. Bookmarks is not translated to PT in the menu Alias & Remarks are not translated PT in Bookmark Informative message is not translated to PT language Claim History is not translated to PT in claims Activities should be translated to PT under Operations menu
36906213	3-37140647951	NXT-30029	Retrieval access restrictions Brand/Payer for CtrClaims and related entities.
Description:		Retrieval access restrictions for Brand/Payer are not present in API, when the brand/payer is restricted, you can get the CtrClaim with the API
37004481		NXT-30052	Messages LOV doesn’t show data properly on add message pop-up
Description:		Messages LOV doesn’t show data properly on add message pop-up. Open any claim. Click on add message button for claim line.
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
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.
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.
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. ex: test_flexcode: null
36967740		NXT-30186	Queued activities remain in QD status when memory protector kicks-in
Description:		The queued activities always remain in QD status when application memory is recovered after breaching the critical memory threshold. Expected: The activities must move to IP status when the application recovers from memory failures and there is enough room available to process the activities
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
36977426		NXT-30198	Remove Copy from Global activities details page
Description:		Copy action should not be shown for view only details pages
36982228	3-37672007771	NXT-30202	Multivalue properties when added in nested properties of a reftype field, console error is thrown
Description:		Multi-value properties when added in nested properties of a reftype field such as procedure where we have configured a procedureSettingList : startDate nested property, console error is thrown
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.
37004581		NXT-30243	Submitting a group from the tab resolved the pends automatically
Description:		Submitting a subClaim which has unresolved pend reasons from the groups tab is happening successfully and subClaim is moving into Finalized status and subClaim still has unresolved pend reasons on it, this is not the expected behaviour instead it should be submitted for processing and should throw a business error
37004593		NXT-30251	Linking Relation: A relation link is not deleted when a relation is deleted
Description:		A relation link is not deleted when a relation is deleted., which violates business rule: GEN-RULE-CEV-001 Cascade Delete

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. Reference Document
NXT-25662	3.22.2.0.0	The support to GET operations on Query API calls is deprecated. Reference Document
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. Reference Document