Release Notes for Oracle Health Insurance Claims Adjudication Release 3.21.1.0.0

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

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

NOTE: 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	Description	Included in Patch
NXT-18299	JET: Page Access Functions	For JET pages, menu access is based on the function codes, and explicit resource level access is needed to be able to view/edit data. Example: Granting view access to function code FN0002, will enable menu item for message configuration. Now, for a user to search and view messages, explicit access must be granted to 'get' (view) messages resource. Explicit get (view) access must also be granted to all its sub resources. In the case of 'update' grants, all the linked resources must also have 'get' access for LOVs to work. With this enhancement, access to all the api/ip resources needed to operate the JET UI page will be granted implicitly by the system. This implicit api/ip access grant will follow the authorization level of the function access grant. For example, view only access grant to FN0002, will grant only GET access to generic resource /messages. Access to special operations like submitting a policy or a group client would require explicit authorizations to api/ip. The api/ip access that must be explicitly granted is specified in the user access section of the security guide.
NXT-20012	HTTP Query API response only includes requested fields	Before this release, HTTP API resources allowed for payload content customization through the expand and fields accept header parameter, however still some defaults were always included. This enhancement allows for having total control on the payload content by adding another parameter to the Accept header: defaultoverride=true.
NXT-20013	Allow traversing of more levels for referenced fields for Generic HTTP APIs	Before this release, in HTTP API, only two levels of references from any resource level were allowed. All details were allowed at any level but the references were only allowed up until 2 levels. This restriction was put in place for not having memory pressures. It is seen from customer feedback and JET implementation that it can be restrictive sometimes, example being: claim→person→addressList→countryRegion→country→code. Since person is a reference from claim, it is only possible to go to addressList but not further. Allowing for more levels can still cause memory pressures if done for the entire object graph. The solution is to lift restrictions on certain references: Person Country ClaimForm ServiceAddress RenderingAddress CountryRegion Provider : IndividualProvider and OrganizationProvider
NXT-20411	Configuration Migration: Flex Code Groups	Flex Code Group is now available as a top level item in the configuration migration tool.
NXT-20417	Retrieve Contracted Providers IP	New integration point that retrieves providers contracted to render a particular service. The request supports a combination of procedures as well as user specified filters.	3.20.3.0.2
NXT-20490	Reporting views: Base view generator + specific IP	The base view generator is now included into the OHI applications itself and can be triggered from the Base View Generation IP. This new base view generator is going to replace the existing (script based) view generator which is now deprecated and will be removed in a future release.
NXT-20854	Improvements for Logging to the Database	For logging to the database using the OHI Database Appender, the following capabilities are added: OHI applications automatically remove customer-defined loggers if these are not explicitly marked as durable. Purging log messages: customers can configure the retention period for log event types. Frequently purging log messages helps to limit the amount of log messages stored in the database. It is now possible to bundle log messages in a data file set. An HTTP API resource is made available to define the criteria for selecting the messages that will be bundled.
NXT-20935	Display application version and enviroment tag in JET UI	With this enhancement, the environment tag is added to application title. In addition, environment tag and application version are also added to the about dialog. The system property ohi.environment.identifier needs to be set in order to display the environment name in the application.
NXT-21006	Add alternate user identifier and OAuth2-specific mapping to that user identifier based on OAuth token issuer; JWK Set token validation (RFC 7517) is now using OpenID Connect	Some systems identify a user by a technical unique identifier that is not suitable to be displayed in user interface pages. With this enhancement, it is possible to use the User Provisioning IP to specify an alternate, unique user identifier (alternateUserIdentifier attribute), next to the existing loginName, for uniquely identifying and resolving users. This enhancement also allows configuration to map a specific claim in an OAuth2 access token to the OHI User based on the issuer of the token. Configuration for RFC 7517 token validation is now based on OpenID Connect. The properties for it have changed. The option to specify a local key store containing a set of public key certificates was removed. The easiest way to use JWK Set based token validation is to use the OpenID Discovery URI via system property "ohi.oauth.idp.uri" in combination with system property "ohi.oauth.jwk.set.validation.audience". Alternatively, set the following system properties if OpenID Discovery cannot be used: ohi.oauth.jwk.set.url ohi.oauth.jwk.set.validation.audience ohi.oauth.jwk.set.validation.issuer.url ohi.oauth.jwk.set.validation.jws.signing.algorithm (defaults to value "RS256") For obtaining an Access Token using OpenID Connect, specification of the clientId and secret combination was changed. System property "ohi.oauth.token.introspection.endpoint.client_secret" was removed. For obtaining an Access Token using OpenID Connect use system property "ohi.oauth.openidconnect.accesstoken.credential". Use of the latter has to be accompanied by specifying a matching credential. For example, assuming the value for system property "ohi.oauth.openidconnect.accesstoken.credential" is "openid_token_credential", specify a credential at resource "/API_ROOT/credentials/credential/openid_token_credential" with the clientId as username and the secret as password.
NXT-21016	Claim line limit parameter aggregation level	This enhancement adds the ability to the claim line limits to write the same cover withhold category to the same limit code multiple times but with another aggregation level. And adds the ability to write a different cover withhold category to a different limit code. Implementation Guide: Claim Pages, Claims Flow, Dynamic Logic Integration Guide: Claims Properties File Database changes: new optional attribute aggregation level in claim line limit. Extended the unique key on claim line limit with cover withhold category and aggregation level Scenarios dynamic logic: no change
NXT-21085	New Configuration Pages added	The following pages are added to the Claims JET interface Titles Prefixes Countries Specialties Currencies Boilerplate Texts Floorplan Access Restrictions Access Roles Data Access Groups Messages Message Groups Provider Assignment Types View registration Languages Person Organization Banks Identifier Types Lines of Business
NXT-21113	CMT : Floorplan	Entity floorplan and floorplan tag details are added to the list of entities that are part of configuration migration.
NXT-21120	Additional Dynamic Fields for OHI Messages table	The number of dynamic fields available on the OHI Messages table was too small. With this enhancement, the number of dynamic fields on OHI Messages table are extended to support the requirements.	3.20.2.0.6, 3.20.3.0.0
NXT-21203	Provider Identifiers	This enhancement focuses on extending the ability to store one or multiple identifiers on a provider. These are used to identify the provider when processing claims and enrollment.	3.20.3.0.2
NXT-21302	Introduce separate property for URL creation for deeplinking in workflows	Property ohi.claims.application.baseurl is used for two purposes. 1) For UI deeplinking for workflow messages 2) For creating links in the notification as a callback to get back data. It is possible that the two usecases require different urls as they both can be exposed on different ports. Hence, with this enhancement, a separate property is introduced to manage the deeplinking for workflows, the new property is ohi.claims.deeplink.url. Implementation Guide: no change Integration Guide: Claims Properties File Database changes: no change Scenarios dynamic logic: no change
NXT-21306	Introduce the possibility to have aliases in fields/expand list	With this enhancement, it is possible to use aliases in fields/expand section in Generic HTTP APIs. Integration Guide: Influence Resource Representation
NXT-21384	Prevent CMT migration between different major versions	Preventing Configuration Migration between a source and target environment that are not on the same major release.
NXT-21397	Ability to confirm JET UI configuration before handover	When a user with access to following API/IPs, logs in to JET UI, he ends up in the landing page without any menus (only the application banner & Sign Out are shown) to indicate successful login. API/IP access * User Information IP * Current Properties IP
NXT-21469	Post Benefit Callout	The End Benefit Callout enhancement NXT-20813 was completed in 3.20.3. However the precise timing of the callout needs to be one step earlier within the claims flow. One should be able to do the callout after the Benefits but before Adjudication. As part of this enhancement, check/performing of End Benfits Callout Rules is moved, from just before Finalization to immediately after setting the status to Benefits Done.	3.20.3.0.5
NXT-21528	Long Running Operation Resource(s) Status Code	When long running operation was designed, it returned 202 with the payload of the newly created long running operation resource depicting that the operation is accepted and the links in the payload can be parsed and used to track progress. With OIG becoming a client for these resources, it was quickly found that the payload itself is not handy to track the progress as it needs to be parsed to get the link to keep track of progress(for timeout situations). What comes in handy is the location header for the just created resources in the response. Now 202 with location header does not make sense, as that is usually used with temporary resources, which is not the case here. With this in mind it is decided to change the implementation to not return 202 with payload, instead return 201 with location header for the created resource. With this enhancement, following long running operation resources need to be changed to return 201 with location header instead of 202 with payload. 1) Read Consumption Batch 2) Write Consumption Batch 3) Extracts 4) Purge in OIG
NXT-21582	Retired SOAP Callout Integration Point	This integration point has been replaced by a RESTful counterpart in a previous release so SOAP integration point has now been removed.
NXT-21583	Retired SOAP Fee Schedule Integration Point	This integration point has been replaced by a RESTful counterpart in a previous release so SOAP integration point has now been removed.
NXT-21584	Retired SOAP Draft Provider Pricing Clause Integration Point	This integration point has been replaced by a RESTful counterpart in a previous release so SOAP integration point has now been removed.
NXT-21585	Retired SOAP Workflow Integration Point	This integration point has been replaced by a RESTful counterpart in a previous release so SOAP integration point has now been removed.
NXT-21586	Retired SOAP Claim Event Integration Point	This integration point has been replaced by a RESTful counterpart in a previous release so SOAP integration point has now been removed.
NXT-21587	Retired SOAP CTR Event Integration Point	This integration point has been replaced by a RESTful counterpart in a previous release so SOAP integration point has now been removed.
NXT-21609	UI page to configure and manage Relation Identifier Types	Pages to configure and maintain relation identifiers are added to Claims, Policies, and CPN JET UI.
NXT-21831	CMT: Order of dynamic logic import	Before this release, in CMT, the dynamic logic were imported in a random order (because they all have the same execution rank). With the introduction of two new signatures "Extension" and "Reusable Code", it is important and also possible that the dynamic logic are imported in an order to prevent look up failures while importing. With this enhancement, dynamic logic will now be imported in the following order of signatures: 1) Reusable Code 2) All the other dynamic logic except "Extension" 3) Extension
OIG-1366	Dynamic Logic Hooks/Extensions	This enhancement make it possible to extend dynamic logic delivered as part of configuration by customers to provide their specific changes/extensions. This is enabled by introducing a new signature 'Extension' for all such extensions with a reference to the base dynamic logic that it is extending. At runtime, the application finds out all the extensions and invokes them.	3.20.3.0.5
OIG-1369	Switching Off Delete by Omission for country packs	This feature switches off the Delete by Omission functionality and allows to import the parent without deleting children in the Target Environment when importing CMT from Source Environment. This is done to support situations where the configuration is delivered and it only contains parent records, and the corresponding children are customer specific.
OIG-1434	Dynamic Logic Framework should allow to use package statement in the logic	Before this release the dynamic logic framework assumes all scripts to be written in a default package ohi.dynamiclogic. This is done to apply the security restrictions and to allow for logging only in scripts defined in the aforementioned package. This causes problems with reusability, as every logic that requires to use the reusable code, needs to append ohi.dynamiclogic before importing it. This makes it difficult to manage and test these groovy logic in isolation. On top of that, dynamic logic framework does not play well, if the package statement is explicitly included as ohi.dynamiclogic, as it appends another ohi.dynamiclogic in front of it. With this enhancement, it is possible to declare packages in the script and the framework will work with the package defined. It is however important, that the packages defined should start with ohi.dynamiclogic, otherwise security restrictions will be enforced.	3.20.3.0.3
OIG-1445	Create Rest Service to generate objects and download them as zip	Introduction of the Objects Integration Point to download the objects as a zip. This Objects Integration Point also introduces the capability to generate dynamic fields and records as just a plain key-value pair, to avoid having to regenerate these after every introduction of dynamic data.
OIG-1446	Generate Signatures for Dynamic Logic as part of meta object creation	This enhancement adds the generation of skeleton dynamic logic groovy files along with generation of objects to assist in groovy coding. These signatures are generated as part of 'Generate Objects' feature in the View Objects page(ADF) and as part of the Objects Integration Point.
OIG-419	Conditional Display of property - Single/Multivalue	This enhancement adds the following possibilities using floorplans Show/hide properties based on another property value Alter characteristics of a property based on another property value, including the possibility to add a filter condition to LOV. Show/hide tabs and tiles based on another property value Support for altering properties for fields in the context of a row within a table
OIG-746	Build CMT Selective Migration Capabilities	This enhancement allows for creating selective migration sets for CMT. With this enhancement, a new IP is introduced to create a selective payload and will also be utilised by JET UI to build the selective migration capabilities. However, this release does not contain JET UI screens
POL-5081	Configurable Address Types	This enhancements makes the address type a configurable domain for relations.
POL-6006	Preparation for upgrade to JET 9.0.0	JET Audit should be done and the critical/major issues needs to be fixed. Migration from knockout ojModule bindings to <oj-Module> JET custom component
POL-6794	Configurable Gender Types	This enhancement creates the possibility to capture a person’s gender identity. Gender identity is a separate configurable entity.
POL-6797	Dynamic Logic Framework should allow for reusable groovy classes to be created and used	With this enhancement, dynamic logic framework allows for coding reusable classes to be reused as structures in other groovy scripts. This enhancement also introduces a new signature name for coding such reusable classes/scripts. The name of the signature is "Reusable Code" and does not have any specific bindings.	3.20.3.0.3

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.

To create a new read-only user that has access to the new Base Views run the following SQL script as a DBA user

grant connect, create synonym to ohi_claims_bvg_vws_user identified by &give_users_password;

Install the database patch for "Bug 30806757 - ORA-8103 when inserting into a new partition with is json constraint in place (Doc ID 30806757.8)". If that is not done and the "logging to the database" feature is enabled then this results in the following error: "Problem appending events for Log Type application|dylo java.sql.BatchUpdateException: ORA-08103: object no longer exists".

Configuration Properties

Ref	Action	Subject	Description
NXT-20490	Added	ohi.baseview.generation.worker.count	The number of worker threads to start for a base view generation process
NXT-20854	Modified	ohi.incident.target	The property ohi.incidents.target is renamed to ohi.incident.target
NXT-20854	Modified	ohi.incident.datafileset.retentionperiod	The property ohi.incidents.datafileset.retentionperiod is renamed to ohi.incident.datafileset.retentionperiod
NXT-21006	Added	ohi.oauth.token.issuer.{0}.user.claim	Issuer-specific user claim
NXT-21006	Added	ohi.oauth.openidconnect.accesstoken.validation.clockskew	Defines the maximum acceptable clock skew (in seconds) for validating timestamps of ID tokens that are issued by an OpenID Provider.
NXT-21006	Added	ohi.oauth.openidconnect.accesstoken.client_id	Client ID of the OpenID Connect client that has to be present to acquire an access token.
NXT-21006	Added	ohi.oauth.openidconnect.accesstoken.credential	Credential associated with the OpenID Connect client that has to be present to acquire an access token.
NXT-21006	Added	ohi.oauth.jwk.set.validation.jws.signing.algorithm	Signing algorithm used by the Authorization Server.
NXT-21006	Added	ohi.oauth.jwk.set.validation.issuer	Issuer for token validation.
NXT-21006	Added	ohi.oauth.jwk.set.validation.audience	Client Id or audience claim for token validation.
NXT-21006	Added	ohi.oauth.token.issuer.{0}	Specific issuer identifier
NXT-21006	Added	ohi.oauth.token.issuers	Comma-separated string of possible token issuers
NXT-21006	Removed	ohi.oauth.jwk.keystore.name
NXT-21006	Removed	ohi.oauth.jws.verification.key.selection.key_id
NXT-21006	Removed	ohi.oauth.jwk.publickey.keyid.source
NXT-21006	Removed	ohi.oauth.token.introspection.endpoint.client_secret
NXT-21006	Removed	ohi.oauth.jws.verification.key.selection.signing_keys_only
NXT-21006	Removed	ohi.oauth.jws.verification.key.selection.jws_algorithm
NXT-21006	Removed	ohi.oauth.jws.verification.key.selection.public_keys_only
NXT-21046	Added	ohi.logging.phi.min.retentionperiod	Minimal number of days for retaining PHI log events.
NXT-21046	Added	ohi.logging.fileset.max.timespan	Maximum time in days between start and end time for bundling log events in a file set.
NXT-21302		ohi.claims.deeplink.url	The base URL of an application used only in ADF deep linking URL formation. It includes the machine or load balancer, the domain and a port number. This is mandatory to set to have correct link in deep linking URL.
NXT-22178	Added	ohi.instrumentation.resourceclienttimer.segment.prefixes	Comma-separated list of known segment prefixes

Web Services

Ref	Action	Subject	Description
NXT-20417	Added	Retrieve Contracted Providers Integration Point	New integration point that retrieves providers contracted to render a particular service.
NXT-20490	Added	Base View Generation Integration Point	New Integration Point
NXT-21006	Modified	Provisioning Integration Point	Added alternateUserIdentifier: an alternate identifier, next to the loginName, for uniquely identifying a user
NXT-21203	Modified	Provider Integration Point, Claims Integration Point & Policy Integration Point	This enhancement focuses on extending the ability to store one or multiple provider identifiers on a provider.
NXT-21582	Removed	SOAP Callout Integration Point	This integration point is removed
NXT-21583	Removed	SOAP Fee Schedule Integration Point	This integration point is removed
NXT-21584	Removed	SOAP Draft Provider Pricing Clause Integration Point	This integration point is removed
NXT-21585	Removed	SOAP Workflow Integration Point	This integration point is removed
NXT-21586	Removed	SOAP Claim Event Integration Point	This integration point is removed
NXT-21587	Removed	SOAP CTR Event Integration Point	This integration point is removed
OIG-1445	Added	Objects Integration Point	New Integration Point
OIG-746	Added	Configuration Migration Integration Point	New Integration Point (part of Dataexchange)
POL-5081	Modified	Relation IP and API	Added new attribute addressTypeCode
POL-6794	Modified	Relations IP and API	new attribute genderIdentityCode

Data Conversion

Ref	Action	Subject	Description
POL-5081		Table change event rule fields updated	Change event rules on address that are using field 'type' are updated to 'addressType'. This is applicable for Policies application only.

Dynamic Logic

Ref	Action	Subject	Description
OIG-1366	Added	Dynamic Logic Signature	Introduced a new signature with name "Extension"
POL-5081	Modified	Dynamic logic using address.type	'type' attribute of Address is replaced by 'addressType'. Accessing type attribute on address is deprecated and will not be supported in a future release.
POL-6797	Added	Dynamic Logic Signature	Introduced a new signature with name "Reusable Code"

UI Changes

Ref	Action	Subject	Description
NXT-20490	Added	Record Definitions page	New indicator PII?
NXT-20490	Added	Tables page	New indicator PII?
NXT-21085	Added	Added Titles,Prefixes,Countries,Specialties,Currencies	Added Titles,Prefixes,Countries,Specialties,Currencies pages
NXT-21085	Added	Added Access Restrictions, Access Roles, Data Access Groups	Added Access Restrictions, Access Roles, Data Access Groups pages
NXT-21085	Added	Added View Registrations, Languages	Added View Registrations, Languages pages
NXT-21085	Added	Added Persons, Organizations, banks, Identifier Types, Line of Business	Added Persons, Organizations, banks, Identifier Types, Line of Business pages
NXT-21085	Added	Added Boilerplate Texts,Floorplan, Insurable Entity Types	Added Boilerplate Texts,Floorplan, Insurable Entity Types pages
NXT-21085	Added	Added Messages, Message Groups, Provider Assignment Types	Added Messages, Message Groups, Provider Assignment Types pages
NXT-21113	Modified	Config Migration Sets (ADF)	Added option to select floorplan while creating a migration set
NXT-21113	Modified	Floorplans page	Added floorplantagdetails tab
NXT-21192	Modified	footer	Application Version Number and Enviorment Tag added
OIG-1366	Modified	Dynamic Logic Page	Added Base dynamic logic. This is done for both UI (ADF and Jet) where applicable.
OIG-419	Added	Dynamic Logic Page	Added Dynamic Logic Page in CPN and NXT
POL-6794	Added	Gender Identities, Address Types	Added Gender Identities, Address Types
POL-6794	Modified	Persons, Organizations	Added Gender Identities and address types lovs in persons and organizations page

Deprecated items (to be removed in future release)

Ref	Action	Subject	Description
NXT-20490		Reporting Views	The reporting views as generated by the runnable jar are now deprecated.
NXT-21582		system property ohi.callout.protocol	This system property is no longer used and will be removed in a future release
POL-5081		Dynamic logic using address.type and generic API on address	'type' attribute of Address is replaced by 'addressType'

Breaking Changes

Ref	Action	Subject	Description
NXT-20854	Modified	ohi.incident.target	The property ohi.incidents.target is renamed to ohi.incident.target
NXT-20854	Modified	ohi.incident.datafileset.retentionperiod	The property ohi.incidents.datafileset.retentionperiod is renamed to ohi.incident.datafileset.retentionperiod
NXT-21302	Modified	Introduce separate property for URL creation for deeplinking in workflows	Deeplinking URL property for workflows is changed from ohi.claims.application.baseurl to ohi.claims.deeplink.url
NXT-21384	Removed	Migration behaviour	Migration between different major versions wont be possible anymore.
NXT-21528	Modified	Purge (oig)	The resource will return status 201 with location header instead of 202 with entity
NXT-21528	Modified	Write Consumption Batch (claims)	The resource will return status 201 with location header instead of 202 with entity
NXT-21528	Modified	Read Consumption Batch (claims)	The resource will return status 201 with location header instead of 202 with entity
NXT-21528	Modified	Extracts	The resource will return status 201 with location header instead of 202 with entity
NXT-21582	Removed	SOAP Callout Integration Point	This integration point is removed
NXT-21583	Removed	SOAP Fee Schedule Integration Point	This integration point is removed
NXT-21584	Removed	SOAP Draft Provider Pricing Clause Integration Point	This integration point is removed
NXT-21585	Modified	ClaimsDataTypes.xsd	The version of this xsd is increased to 5.0
NXT-21585	Removed	SOAP Workflow Integration Point	This integration point is removed
NXT-21586	Removed	SOAP Claim Event Integration Point	This integration point is removed
NXT-21587	Removed	SOAP CTR Event Integration Point	This integration point is removed
POL-5081	Modified	Generic API search on address.type	This should be replaced by address.addressType.code

Bug Fixes

BugDB	SR	Internal	BP	Summary
25316921		NXT-15674		Definition does not show list of values for providers in reference sheet
Description:		Definition does not show the list of values for providers in reference sheet.
Resolution:		Definition now shows the list of values for providers in reference sheet.
31025569	3-22535876581	NXT-20300		Large WriteConsumptionBatch Encounters ORA-00054: Resource busy and acquire with NOWAIT
Description:		For WriteConsumptionBatch, we see several requests failing with error 'ORA-00054: resource busy and acquire with NOWAIT'. This happens frequently due to locking conflicts between multiple execution threads.
Resolution:		Redesign the WRITECONSUMPTIONBATCH IP to avoid locking conflicts between different threads. The import will be based on the grouping of the service member and the limit code. All the consumption of the same counter will import from a single activity. To achieve this new database table is introduced - ALI$WRITE_CONSUMPTIONS.
32019892		NXT-20577		Post Benefit Callouts : Tab shows count but no details in claims details page.
Description:		JET UI Tabs shows count but no details in it. User will be able to view and access the contents under the tabs like benefits, messages, pricing, pend reasons, financial holds and un-finalize reasons in the claim details page. Steps to recreate : 1. Open any claim. 2. Click on messages in the claims details page. Expected - Claim and Claim line messages should show the related details.
Resolution:		Now the user will be able to view and access the contents under the tabs benefits, messages, pricing, pend reasons, financial holds and un-finalize reasons in the claim details page.
31837529	3-23894002141	NXT-21056		Migration set exclusions are not retained on save action
Description:		When for the migration set Exclusions are checked and the set is saved, when re-opening the set, the exclusions are not checked. Re-checking the exclusions and saving the set could solve this issue.
Resolution:		Checked exclusions are now retained when the Migration Set is saved.
31924651		NXT-21157		Not able to access the actions from Procedures search results when the field attached to a column is too big.
Description:		User is not able to access the actions from Procedures search results, when the field value attached to a column is too big.
Resolution:		Now user is able to access the actions when they configure the Fields with large data to displayType as composite or textarea and can be used as the column field in the search table or in the overflow region of the search table or In the region component.
31934727	3-23876699351	NXT-21177		Claim Submit API leads to unintended pend resolution
Description:		The claim submit API (meant to support the submit button in the JET Claim page) exhibits different behavior from the submit button in the ADF Claim page. Pend reasons that are not resolved should not be auto-resolved through submitting a claim.
Resolution:		The Claim Submit API no longer automatically resolves reasons in the same transaction. Pend reasons have to be resolved explicitly prior to submitting. This ensures that a user always takes notice of potential issues with a claim.
31945436	3-24072465081	NXT-21204		Prevent Plan Year Override for non-year limits
Description:		The functionality to override plan year periods (meant for plan anniversary changes) is overriding not only the actual year limits but also daily and monthly limits. This feature kick’s in when the enrollment response contains a value for the contract end date. The current system behavior is that - during calculation - any limit that uses the reference 'plan year' automatically applies a counter period based on the contract start and end date extracted from the response. The fix is to add an additional condition to this feature that checks the configured renewal period length on a limit, so that only limits with (1) AND a reference date equal to the plan anniversary day (this condition is already implemented) (2) AND with a single year as the renewal period length (this is the new condition) are overridden with contract end date as limit counter period end date.
Resolution:		Plan Year limits are only overridden now: 1. when the subscription has an enddate (existing condition) 2. AND the renewal length is 1 Year. (new condition) Note: renewal length of 12 months are not overridden.
31953024		NXT-21211		Generic JET UI bug: unable to specify a logout URL
Description:		User is not able to specify the logout URL for JET UI.
Resolution:		Now two new properties, "ohi.ui.logout.url" and "ohi.ui.webgate.logout.url" have been introduced. If "ohi.ui.logout.url" is set then its value will be used by default. Otherwise depending on the authentication method either "ohi.security.oauth.logout" or "ohi.ui.webgate.logout.url" will be used. The former will be used if its either "OAuth" or "OpenId", whereas the latter will be used if its "WebGate".
31989244		NXT-21261		Issues with the Inbound Data Sets Page
Description:		Following issues have been observed on the Inbound Data Sets page after the newly added BENEFITS_HTTP and PRODUCTS_HTTP definitions : 1. File Upload Option is currently not supported. 2. The result messages are no longer shown for the newly added definitions due to the different technical implementation. Consequently the user now has to navigate to the activity messages in order to see how the product file processed. These message dialogs should show the activity messages for the appropriate activity.
Resolution:		File Upload option is now available for the new HTTP type definitions (BENEFITS_HTTP and PRODUCTS_HTTP). The Status column shows the status of the import along with the number of result messages. For the HTTP type definitions, clicking on the status link with the number of messages > 0, a dialog which contains the Activity Messages is shown.
32006819	3-23723613251	NXT-21289		Reference Sheet import element datatype is not registered in all the nodes of the cluster
Description:		Reference sheet Import element datatype is not registered in all the nodes of cluster. This issue is reproducible only in multi-nodes cluster setup. The following steps might help to reproduce. 1. Create a new reference sheet 2. Configure the property ohi.referencesheetimport.filereader.chunk.size to 2 (default is 5000) using properties API 3. Create a data file containing ~10 reference sheet lines and import using REFSHEETLINE_IMPORT activity.
Resolution:		Reference sheet lines are now imported successfully in multi-nodes cluster setup
32020047		NXT-21297		CorrelationID missing in writeConsumptionBatch IP notification response
Description:		CorrelationId is missing in writeConsmptionBatch IP which is required if the data need to be referred in other applications.
Resolution:		The following are the changes: 1) Response Code is changed from 202(ACCEPTED) to 201(CREATED) 2) Created WriteConsumptionBatch path will be available as the part of location in the Response Header. 3) Notification will consist of the Correlation Id.
32027833		NXT-21313		Unable to navigate to Menu tabs when viewing a claim
Description:		Unable to navigate to Menu tabs when viewing a claim. Steps to recreate: 1) Search for claims 2) Open any claim 3) Click on configuration tab Expected: User should be able to navigate Actual: User is not able to navigate
Resolution:		User is now able to navigate from claims view-edit page to other pages on different menu.
32029725	3-24571978961	NXT-21318		LOV not displayed for certain flexcodes for Dynamic records.
Description:		In the Dynamic Records popup, LOV is not displayed for flex codes field.
Resolution:		Fixed the refresh issue. Now user can launch and select value from LOV for flex code field.
32042253	3-24073189880	NXT-21331		No response received for WriteConsumption Batch request
Description:		For the write consumption batch requested, there are few instances of no response coming back. Ideally, all activities should complete and no activity should be in IP state.
Resolution:		Fixed SQL query. Changed the default value of property ohi.consumptionimport.filereader.chunk.size to 1000. These changes resolve the underlying problem causing no response from write consumption batch request.
32073577	3-24368499541	NXT-21370		Dynamic Logic exception: Restricted method invocation
Description:		When accessing the object returned by the JSON slurper, the application raises an exception, e.g.: Error occurred in dynamic logic "DYLO_NAME" on line "xxx": "java.lang.SecurityException: Restricted method invocation."
Resolution:		The new version of Groovy packaged with the application returns a Lazymap object from the JSON slurper. Access from Dynamic Logic to objects of this type was not permitted, this has now been changed.
32075112	3-23875773991	NXT-21375		Limits not applied on overriding benefit specifications
Description:		If an overriding benefit specification is used on a claim line, the line applies the correct coverage regime with the correct parameters. However, any limit parameters specified on the product for the benefit specification are ignored and no limits are consumed. The expectation for the system is to count the limits specified on the product benefit specification.
Resolution:		Limits of the combination of product and overriding coverage specification will now be applied to the claims.
32079965	3-24351459541	NXT-21383		Doc: OHI SaaS doc corrrection for timezone
Description:		The documentation lacks clarity on environment configuration required when users are in different timezone than database.
Resolution:		The documentation was updated with additional environment configuration that needs to be put in place when users are in a different time zone than the database. See the Installation Guide.
32105131	3-24368753141	NXT-21411		Limit Consumption Activity does not stop when invoked from UI
Description:		CONSUMPTION_IMPORT activity should not be triggered from UI.
Resolution:		CONSUMPTION_IMPORT activity should not be triggered from UI so removing it from the Activity Type LOV in the Create Activity Screen.
32107757	3-24068646251	NXT-21414		Business validation error not handled correctly in UI leading to unexpected exception
Description:		When business validation added to the corresponding UI data row, exception throws and it is not handled in UI. So it navigates to the standard error page.
Resolution:		Handled the error where save logic is written. Now it will be shown in the corresponding page as the expected error. Message 'The server is unable to respond' does not show anymore when saving in the application.
32142731		NXT-21459		Null pointer exception in View Technical Error page
Description:		In many cases, clicking the "Details" button in the "View Technical Errors" page results in an incident being created for an NPE.
Resolution:		Clicking on Details in view technical error page no longer displays ' Server unable to respond' error or create stack trace. It opens the details dialog.
32150173	3-24500949741	NXT-21465		Exception occurred when user selects value to the column level multivalue flex code.
Description:		When the user selects a value from the LOV for a multivalued flex code column, null pointer exception is thrown and error page displayed.
Resolution:		A value can now be selected from the LOV for a multivalued flex code column without any error.
32173041		NXT-21505		Unable to navigate to view page after performing edit operation
Description:		Confirmation message was not appearing after edit operation and then being redirected to view page.
Resolution:		When Edit action is performed on any HRR page and the changes are saved, the page displays the Confirmation message and gets re-directed to View mode again
32192408		NXT-21545		Error is visible even after clicking on procedures link
Description:		When there is a error in Search results page, if the user navigate back the error message is displayed in new screen.
Resolution:		Now if there is a error in Search results page, if the user navigate back clears the error message and not displayed in new screen.
32192456		NXT-21546		Overflow region fields in the search table is not loading for the first time in Procedures search page.
Description:		In Procedures search page, overflow region fields are not getting displayed to search results for the first time.
Resolution:		Now all the overflow region fields are displayed in the search results of procedures search page.
32204317		NXT-21594		SELECT_REPROCESSCLAIMS activity completes successfully, but the notification received on the data file notification end point has status as "Failure"
Description:		Even though the "SELECT_REPROCESSCLAIMS" activity completes successfully, the notification received on data file notification end point has "Failure" status.
Resolution:		When the activity "SELECT_REPROCESSCLAIMS" completes, the status in the data file notification now correctly reflects the status of the activity. With this bug fix, the order of the links in the data file notification has changed.
32217263		NXT-21649		Get on Extracts IP activity link not returning file path
Description:		When extracts activity is invoked, the file that is created by the activity is expected to be placed in a datafileset and the link to it, returned in the activity response. But the link was missing in the response
Resolution:		The file link is now returned by the extacts IP activity response
32222943	3-24619495251	NXT-21660		Missing Person code generation signature - this is documentation error
Description:		The person code generation is only available in POL and CAP by design since Claims is never the system of record for membership and we did not expect a scenario where Claims would assign codes / create new members claims. So looking at the Dynamic Logic guides; the claims guide omits it (as expected) and the policies guide includes it (as expected). If the claims integration guide does mention it, then that is a documentation error.
Resolution:		The relations IP documentation mentioned the 'Person Code Generation' and 'Organization Code Generation' signatures. Those signatures are only available in OHI Applications that are the system or record for relations data. A note has been added to the documentation to clarify this.
32226457		NXT-21661		Nested property should be shown under separate columns next to the LOV
Description:		Nested properties should be shown under a separate column next to the LOV as read-only
Resolution:		Added extra conditions so that nested properties can be shown in separate columns next to the LOV as read-only.
32243470	3-24626119191	NXT-21685		An error is coming when user tries to save the LOV value without selecting from the search results
Description:		The error is coming when user try to save the LOV value without selecting from the search results. If the user doesn’t select any value, the value does not get saved.
Resolution:		If the user wants to select a value from an LOV, then they must enter the complete value of the LOV and press Enter key. This will pick the first value from the search results of LOV.
32250695	3-23723613251	NXT-21712		Descriptor is not found while unmarshalling reference sheet lines in multi node cluster setup
Description:		When dynamic field usage and reference sheets are created using API in a cluster setup and reference sheet line import activity is started on the node (not on which the dynamic field usage and reference sheets are created ), descriptor for reference sheet line is not found while unmarshalling.
Resolution:		Reference sheet lines are now imported successfully in multi node cluster setup and descriptor is present while unmarshalling reference sheet lines.
32254363	3-24661985451	NXT-21723		Asterisk mark not appearing for mandatory time valid dynamic fields
Description:		Asterisk mark doesn’t show for mandatory start or end date fields when dynamic field is configured as a time valid field
Resolution:		Asterisk mark is shown with the mandatory dynamic fields when it is configured in a table
32284837	3-24518747031	NXT-21755		Prevent: Claims Status out of Sync with claim status history after unfinalize claim
Description:		There are few instances of a situation that a claim was unfinalized, but claim status remained at Finalized. This situation needed a data repair script to continue.
Resolution:		The issue of claim status being out of sync is addressed in 2 ways: 1. An additional business CLA-CLAI-047 prevents the data corruption from happening. 2. Additional logging is added to diagnose the issue further. Logging setting they may be helpful: Logs UI actions so that the flow of a claim through UI can be followed: <logger name="com.oracle.healthinsurance.claims.interaction" level="debug"/> Logs when from a UI action, the status moves to Finalize: <logger name="com.oracle.healthinsurance.claims.domain.internal.entities.ClaimDomain" level="debug"/> If this setting results in log being written, further diagnosis is needed, as the UI typically does not set the status to Finalized. This is done by background processing. The logger above does show the complete stack trace, so is helpful to find out which code path is involved. Logs all status changes triggered by UI code: <logger name="com.oracle.healthinsurance.claims.domain.internal.entities.ClaimDomain" level="debug"/> The logger above does show the complete stack trace.
32300968	3-24611017191	NXT-21774		Dynamic Records are not rendered in the UI when they are configured as tab resource.
Description:		Dynamic records are not rendered in the UI when Dynamic fields are configured in the region and Dynamic record as tab resource.
Resolution:		Changes were made in the request header of the API call to show Dynamic Records.
32334675	3-24738743651	NXT-21802		Dynamic records not displayed in exported excel
Description:		Dynamic column value at column level not displayed in exported excel
Resolution:		Dynamic record columns will now be listed in excel.
32352970	3-24806375171	NXT-21818		Claims IP to fetch procedures for procedure groups not working correctly
Description:		Claims IP to fetch procedures for procedure groups not working correctly when procedure group code has leading zero. Steps to reproduce are: 1.Setup a Procedure 2.Setup a Procedure GROUP (code should have leading zero, ex: 054) 3.Add the procedure (created in step 1) to the procedure group (created in step 2) 4.Run the procedure group details IP. The one with leading zero always returns '204 - No Content', though there is associated procedure/s in the system.
Resolution:		Claims IP to fetch procedures for given procedure groups (with leading zero) now work correctly
32374109	3-24807818401	NXT-21846		Contracted Providers IP not working correctly
Description:		The correct OhiContext (and hence correct Locale) is not used in the contracted providers IP which leads to the default language being 'en' instead of 'es'. This is a coding bug and needs to be fixed.
Resolution:		The OhiContext is now using the default locale that is set in ohi_laguages.
32401904	3-24829680111	NXT-21886		Client side validation is not working properly when it’s used in tab-table component.
Description:		Client side validation is not working when it’s used in Tab-Table component. It only works when first we add a value in the mandatory field and then remove it.
Resolution:		Client side validation works properly now in tabs while adding new rows in table.
32403282	3-24944743701	NXT-21890		ElementID missing in WriteConsumptionBatch error messages
Description:		ElementId is missing from error messages that are logged in ResultDataFileSet for writeConsumptionBatch.
Resolution:		ElementID is now added for all business errors.
32436430		NXT-21945		Full Configuration migration set does not contain all top level items
Description:		The full migration set created with /dataexchange/createandexport for CLAIMS_CONFIGURATION does not contain all top level items. Several items are missing, e.g. baskets, currencies, exchange rates.
Resolution:		The missing top level Items basket, currency, exchange rate, floorplan, insurable entity type, line of business and provider assignment type are added. Also the exclude option on claim event rule is corrected from Message to Message Group.
32438798		NXT-21951		Use application context root changed at deployment time.
Description:		Application have not picked the context root name which is changed at deployment time.
Resolution:		Now, application design capable of picking up the context root which is changed at deployment time.
32468954		NXT-21985		Task is stuck in 'PROCESSING' status if the node leaves the cluster
Description:		When the node processing a task leaves the cluster or if the node is stopped while the task is being processed, then the status of the task remains in 'PROCESSING' status. The other nodes in the cluster should have recovered/requeued that task.
Resolution:		When a node leaves the cluster, then the tasks that are currently being processed by that node are now recovered by the other node(s) in the cluster.
32477329		NXT-22009		CMT process hangs if interrupted and does not allow running any new CMT process
Description:		When CMT fails the job can be stuck within the database which prevents the user from running another CMT. Steps to reproduce : 1. Start CMT Import, when the import has started, stop the server. 2. Restart the node(s). 3. Start another import process. 4. The process does not start, and fails.
Resolution:		The resolution was mostly done on transactional grounds of the cleanup services. Post the resolution, if CMT process is interrupted due to any reason, it can be started again. Steps to verify are : 1. Start CMT Import, when the import has started, stop the server. 2. Restart the node(s). 3. Check the status of the CMT process after restart, it should be marked as F. 4. Start the import process again, it should be possible to successfully start the process.
32506336		NXT-22048		Unable to query claims on servicedMember.relationIdentifierList.identifier
Description:		Generic HTTP API search on <child>.relation(+)relationIdentifierList.identifier.like("123”) gave error: An error occurred in processing the request; for more information about the error search the logging for occurrences of ;relationIdentifierList, is not a (dynamic) field for class <child> For example on claims: api/generic/claims?q=servicedMember.relationIdentifierList.identifier.like("123”)
Resolution:		When a search is done on a relation child, like claims, addresses, using relationIdentifierList, this search is now properly executed.
32567118		NXT-22178		Resource for resource_client_timer in metrics not specific enough
Description:		For gathering metrics, the resource for resource_client_timer seems not specific enough. If multiple callouts are done to the same environment the actual resource is not visible, as it shows the loadbalancer
Resolution:		A new property ohi.instrumentation.resourceclienttimer.segment.prefixes is introduced to specify known path segment prefixes to ignore.

Issues that were backported in previous Release / Patch

BugDB	Internal	Summary	Backport	BugDB	SR
31025569	NXT-20300	Large WriteConsumptionBatch Encounters ORA-00054: Resource busy and acquire with NOWAIT	3.20.2.0.6	31025620	3-22535876581
32019892	NXT-20577	Post Benefit Callouts : Tab shows count but no details in claims details page.	3.20.3.0.2	32038887
31837529	NXT-21056	Migration set exclusions are not retained on save action	3.20.2.0.7	31837538	3-23894002141
31934727	NXT-21177	Claim Submit API leads to unintended pend resolution	3.20.3.0.1	31973848	3-23876699351
31945436	NXT-21204	Prevent Plan Year Override for non-year limits	3.20.3.0.1	32032749	3-24072465081
31945436	NXT-21204	Prevent Plan Year Override for non-year limits	3.20.2.0.7	31966202	3-24072465081
31953024	NXT-21211	Generic JET UI bug: unable to specify a logout URL	3.20.2.0.5	31953112
32006819	NXT-21289	Reference Sheet import element datatype is not registered in all the nodes of the cluster	3.20.3.0.1	32006838	3-23723613251
32006819	NXT-21289	Reference Sheet import element datatype is not registered in all the nodes of the cluster	3.20.2.0.6	32006854	3-23723613251
32029725	NXT-21318	LOV not displayed for certain flexcodes for Dynamic records.	3.20.3.0.5	32029774	3-24571978961
32042253	NXT-21331	No response received for WriteConsumption Batch request	3.20.2.0.7	32048804	3-24073189880
32042253	NXT-21331	No response received for WriteConsumption Batch request	3.20.3.0.3	32048801	3-24073189880
32073577	NXT-21370	Dynamic Logic exception: Restricted method invocation	3.20.3.0.1	32073589	3-24368499541
32075112	NXT-21375	Limits not applied on overriding benefit specifications	3.20.3.0.1	32075162	3-23875773991
32075112	NXT-21375	Limits not applied on overriding benefit specifications	3.20.2.0.7	32075148	3-23875773991
32107757	NXT-21414	Business validation error not handled correctly in UI leading to unexpected exception	3.20.2.0.7	32113589	3-24068646251
32107757	NXT-21414	Business validation error not handled correctly in UI leading to unexpected exception	3.20.3.0.1	32113578	3-24068646251
32150173	NXT-21465	Exception occurred when user selects value to the column level multivalue flex code.	3.20.3.0.1	32150183	3-24500949741
32150173	NXT-21465	Exception occurred when user selects value to the column level multivalue flex code.	3.20.2.0.7	32150194	3-24500949741
32173041	NXT-21505	Unable to navigate to view page after performing edit operation	3.20.3.0.1	32173051
32204317	NXT-21594	SELECT_REPROCESSCLAIMS activity completes successfully, but the notification received on the data file notification end point has status as "Failure"	3.20.3.0.4	32204315
32243470	NXT-21685	An error is coming when user tries to save the LOV value without selecting from the search results	3.20.3.0.4	32243540	3-24626119191
32250695	NXT-21712	Descriptor is not found while unmarshalling reference sheet lines in multi node cluster setup	3.20.3.0.5	32300941	3-23723613251
32300968	NXT-21774	Dynamic Records are not rendered in the UI when they are configured as tab resource.	3.20.3.0.4	32383996	3-24611017191
32352970	NXT-21818	Claims IP to fetch procedures for procedure groups not working correctly	3.20.3.0.4	32353024	3-24806375171
32403282	NXT-21890	ElementID missing in WriteConsumptionBatch error messages	3.20.2.0.8	32404960	3-24944743701
32403282	NXT-21890	ElementID missing in WriteConsumptionBatch error messages	3.20.3.0.5	32404965	3-24944743701
32468954	NXT-21985	Task is stuck in 'PROCESSING' status if the node leaves the cluster	3.20.3.0.5	32468968
32468954	NXT-21985	Task is stuck in 'PROCESSING' status if the node leaves the cluster	3.20.2.0.8	32470774
32506336	NXT-22048	Unable to query claims on servicedMember.relationIdentifierList.identifier	3.20.3.0.5	32506351

Known Issues

BugDB	SR	Internal	Summary
31545595		NXT-13750	GEN-DYNA-001 not raised when sending in multiple lines with the same value
Description:		GEN-DYNA-001 not raised when sending in multiple lines with the same value for a dynamic field that is setup to be unique.
21085259	3-10126085901	NXT-13816	Some classifications are being appended twice when duplicating rows of PPCS
Description:		Some classification fields are being appended twice when duplicating Partial Provider Pricing Clauses in a Pricing Option. These duplicate values are separated by a semi-colon. This is the case for the following fields: Classification scheme Claim classifications Claim line classifications
21683071	3-11209658944	NXT-14134	Removal of skip tagged messages at CLAIM level does not work correctly
Description:		Removal of skip tagged messages at claim level does not work correctly. After clicking on button 'Undo Claim Line Replacements', the message at claim level that has a skip tag in the tables is not removed. The message still shows in the UI when you see 'GEN-UINT-016: The replaced claim lines have been restored, press save to commit the changes'. After clicking on Save the message is removed. Messages on claim line level with a skip tag are removed directly after you click on the button to undo. Both claim level and claim line level messages should be removed in a consistent way.
25244244		NXT-15022	Access- RM0016 - On the persons and Organizations page The expand overflow button is not accessible by keyboard
Description:		While doing keyboard testing the objective is that via keyboard a person can access the whole application. But on Persons and Organizations page the cursor focus does not move to the expand overflow icon.
25244411		NXT-15247	Access - CMN - Value and Type Focus is lost after Value field
Description:		In Value and Type field Focus is lost after Value field and user could not access type field automatically.
25244539		NXT-15572	Access - Oghag tool - links - Empty values for Servicing provider some how gets detected as links and hence error displayed
Description:		On View Authorization page for blank value on Servicing provider link is getting detected which throws the error when the link tool on the OGHAG toolbar is used.
25222260		NXT-15588	Access - Documentation - Lang attribute missing for HTML element
Description:		When used structure tool of OGHAG toolbar 1 error is constantly appearing for all the pages of documents. i.e. Error - No lang attribute found on HTML element in document. The same issue is observed for Integration guide.
25228067		NXT-15592	Access - Focus should first come left hand side first menu
Description:		Keyboard Testing Steps to reproduce 1. Login to OHI Claims. 2. On the home page Click tab from the Url. Expected result - The focus should shift to the the left hand side top menu of the application. Actual result - As of now from the browser if user clicks tab it goes to preferences instead.
25228223		NXT-15593	Access - CTRL+INS+I: List items does not work in the application
Description:		Pre-requisites 1. Screen reader mode must be ON 2. JAWS must be ON 3. Open application in IE browser Steps to reproduce: 1. Navigate to Claims→Claims Search 2. Search such that multiple Claims are displayed 3. Press INS+CTRL+I Expected result : List items in the page must be displayed Current result: Open the browser favorites
25228451		NXT-15594	Access - Error messages are not read in SR mode
Description:		Pre requisites - Screen reader mode ON, Jaws, use <TAB> to navigate Steps to reproduce: 1. Navigate to Configuration → Process Rules → External Intervention rule. 2. Click on Add row with entering any more details click on Save. 3. Read the page by JAWS. Expected: The error message must be read while using JAWS to let the blind user know that he has encountered an error. Actual: The error message is not read.
25238148		NXT-15600	Accessibility - When 200% ZOOM is applied on NO vertical scroll is available
Description:		Steps to reproduce : 1> Navigate to Draft Provider Pricing Clauses(DPPC) page. 2> Set the browser zoom of FF to 200%. 3> Verify the page. Observations : No vertical scroll is found. When the main section is displayed the child section is not displayed. When main panel is closed the child section is some what displayed but again as vertical scroll is not there so not possible to find the records.
25238284		NXT-15602	Access - Close Tab 'X' icon is not accessible while doing keyboard testing
Description:		Keyboard Testing Steps to Reproduce: 1. Open Claims application. 2. Open any page (such as Medical Cases) 3. Using tab only try to access the 'x' icon of any opened page. Expected Result - It should be accessible by tabbing so that through keyboard testing user can be able to close the page. Actual Result - It is not accessible via keyboard by tabbing. Work around is Close All icon. This is accessible via keyboard.
25238564		NXT-15603	Access - "ITEM:" is missing for all the non-context tables in the parent
Description:		Steps to reproduce: 1. Navigate to Member Limit Counters. 2. Navigate to Enter Claim. 3. Using tab key navigate to the titles of each tab. Expected result: "Item:" must be available for JAWS to read when the focus is on Enter Claims(focused) page. Actual Result: Item is not available and hence the listener will not able to understand that the focus is shifted to a new tab.
25239039		NXT-15605	Access - Jump to line functionality of JAWS does not work on our application
Description:		Jump to line functionality of JAWS enables user to navigate to specific line/attribute based on it unique number. Pre-requisite : Screen reader mode must be ON Steps to reproduce: 1. Navigate to Configuration→Flex Code Definitions 2. Using tab navigate to Configuration root menu panel. 3. Make the commands for jaws active. ( just make sure they are some times you have to restart JAWs for this) 4. Press J 5. Increment the number by 1 6. Click on OK Expected result : Focus must be next element (any other element based on number provided) Current result: Focus remains in same position before and after performing the jump operation.
25239527		NXT-15609	Access - Document Testing - Graphic images are not detected by Jaws
Description:		Open JAWS, Screen Reader on. - Navigate to the document - Move to page with graphic image - Press CTRL+INS+G - Verify with OGHAG toolbar with Image tool. Expected result : labels of the graphic images are displayed Actual result : JAWS doesn’t identify the images.
25239595		NXT-15611	Access - Document Testing - The page address link is read as page title
Description:		JAWS reads page address link as Page Title. Steps to recreate are - Open JAWS; Navigate to document ; Press INS + T and Verify JAWS audio Expected result: 'OHI Claims Adjudication' should be read as title Actual result: Address link of the page is read as page title and this is not.
31371930		NXT-17112	Reference Sheet Override dialog changes cannot be canceled
Description:		The Cancel button in the Ref Sheet Override dialog has been hidden because the button didn’t work: when user make changes in the ref sheet overrides, and click Cancel, the changes are still present when reopening the dialog.
27174341		NXT-17645	Accessibility - Documentation - No summary defined for data table
Description:		Steps to reproduce Publish the updated Installation guide for OHI Claims Adjudication in HTML format. 3> Run keyboard testing, OAG toolbar testing and Jaws on the pages. Observation - No Summary Defined for Data table (wcag2 1.3.1) (Table tool)
28334716		NXT-18265	Accessibility - Investigate how to implement and apply High contrast mode
Description:		This task is to enable high contrast mode for JET UI’s .
28357739		NXT-18626	Accessibility - No documentation to define accessibility and compatibility features
Description:		As, JET provides info that should be included in the accessibility chapter of any product built with it, there should be documentation to define Accessibility and Compatibility Features.
31173021	3-20362370061	NXT-20395	ORA-01555 Errors for sqlid gc0udub5tk6vd
Description:		The database alert log shows intermittent ORA-01555 errors for sqlid gc0udub5tk6vd. This seems to happen when dequeueing messages from AQ. This alert does not impact OHI functionality.
31528485		NXT-20720	Accessibility - Application is not supporting PORTRAIT mode
Description:		The application needs to support portrait mode as well as landscape mode.
31528563		NXT-20721	Accessibility - Not able to acces menu items with 300% zoom
Description:		With 300% zoom user is not able to access the menu items which is a loss of information/ functionality. Also the dropdown with user name is not visible with 400% zoom.
31528989		NXT-20722	Accessibility - Not able to access gear icon with LOV using keyboard on create group client page
Description:		The issue can be reproduced by accessing any LOV through keyboard.
31528927		NXT-20723	Accessibility - Additional information which comes from hovering over links is not accessible.
Description:		Additional information which comes from hovering over links is not accessible.
31529019		NXT-20724	Accessibility - Advanced Search Box is not accessible in Firefox browser.
Description:		Advanced Search Box is not accessible in Firefox browser. It works fine in Chrome Browser. This issue is applicable for JET screens.
31529141		NXT-20725	Accessibility - Save status messages are not conveyed through screen reader
Description:		Assistive technology does not covey the information of the status messages. Prerequisite JAWS application should be running. Steps: 1. Save any data in the application. 2. JAWS doesn’t convey any message for the saved data. Expected Result - JAWS should covey the message for the status messages.
31628710		NXT-20881	UI - the horizontal scroll bar retraces once on claim line section
Description:		On claim line section, the horizontal scroll bar retraces back once user tries to check details on right of the claim lines. Although it happens only once and in later instances it works as expected.
31634226		NXT-20888	UI - User is unable to navigate on detail dialogs while moving to next set of records.
Description:		Preconditions: Set the ohi.ui.maxrowstoretrieve property to a minimum value (eg. 5) Steps: (Pend reason dd) On pend reason dialog try to add more than 5 records so that the option to navigate to Next/ Previous sets are available. User tries to navigate on next set using "Next" button, but thrown out of the system with an exception.
31636129		NXT-20889	UI - Horizontal scroll bar on claim line area repositions at center after opening two claimline simultaneously.
Description:		Preconditions: A Claim with multiple claim lines & user tries to open multiple claim line overflow area. Once user tries to perform close to open and vice versa on claim line overflow area, the horizontal scroll bar repositions to the center.
31925285		NXT-21161	Filter Component: Not working when configured with Date fields
Description:		Steps to Reproduce: 1) Create the custom floorplan configured with the filter component with Date field. 2) Navigate to Reference Data→ Procedures. 3) Render the custom floorplan created with Filter component. 4) Enter the date range in the filter. Expected Results: Search results should be displayed based upon the selected date range. Actual Results: No action is getting performed and an error message is displayed in the console.
31931061	3-24111363781	NXT-21171	Flexcode field not saving on claim save
Description:		While updating flexcode (yes/no) on claimline, in certain scenario’s the new value of the field is not being saved. This happens typically when multiple claims lines are updated.
32018463		NXT-21301	CALLOUTSEND process gives exception intermittently
Description:		Callout send process is failing intermittently
32139431	3-24383895551	NXT-21456	CMT Dataset containing Flex codes sytsems and Flex codes take more time than 3.2
Description:		Whenever any extensibility entity (field, flex code system, flex code field usage, dynamic field usage and flex code) is inserted/updated/deleted, the non-entity (distributed) cache is invalidated. Until 3.20.2.0.0, the API NearCache#clear was used for this purpose. From 3.20.2.0.1, this has been changed to NearCache#truncate to fix the bug 31677002. The truncate operation on NearCache seems to be more 'blocking' than clear and is causing performance issues.
32192848		NXT-21548	Textarea as the column in the search table is not rendering correctly
Description:		Steps to Reproduce: 1) Create custom floorplan with Dynamic field in column as Textarea. 2) Search for the procedure which has the large value in the dynamic field. Expected Results: Search results should display along with the textarea in the column. Actual Results: Serach results didn’t display the field column as text area.
32219860	3-24628242821	NXT-21650	Applied provider pricing clause on claim line does not change when product category is changed
Description:		Changing the associated Product with the Product Category does not reflect a change in the applied provider pricing clause on the claim line.
32288599	3-24626202211	NXT-21757	All the records are not shown for Flexcodes LOV
Description:		When a Flex Code LOV is opened on Enter Claims page, all the records are not shown. All the records are shown only when we select any row in the LOV. This issue is seen only on Chrome and not on Firefox.
32477023		NXT-22007	With clicking Next button dialog button not refreshed
Description:		In Popup dialogs, Next and previous button doesn’t work due to refresh issue.
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.
32578470		NXT-22037	User is able to update the enabled atribute of an identifier even after not having the update access
Description:		For both provider and relation identifiers it is not possible to update the identifier itself when a user is not having update access, however it is possible to update other attributes, like enabled. User is able to update the enabled atribute of an identifier even after not having the update access
32501857	3-25047894481	NXT-22044	Claims Reprocess Integration Point should mark the existing pend reasons as resolved
Description:		Claims Reprocess Integration Point should mark the existing pend reasons as resolved using the information from the user context.
32525568		NXT-22093	Usage namges with a reserved SQL word results in view generation failure
Description:		A usage name like "level" (which is a SQL reserved word) results in a failure in the view generator for the table where this usage is used.
32530815		NXT-22103	ACTIVITY CONSUMPTION_IMPORT should not be triggered from IP
Description:		Invoking the activity consumption import process through activity through IP is not allowed from UI and it should not be allowed from IP as well.
32550583		NXT-22152	Baseview generation sometimes might result in error: ORA-01461
Description:		Occasionally baseview generation results in error: ORA-01461. In the event that this happens, typically resubmitting the generation process resolves the problem.
32554859	3-25162308611	NXT-22158	Duplicating a claim line which has a value for an Overriding Claim Line parameter gives error
Description:		Duplicating a claim line which has a value for an Overriding Claim Line parameter gives the below error : GEN-ORA-00001: THIS "CLAIM LINE OVERRIDE" ALREADY EXISTS Expectation is that no error message should be shown and claim line should be added without any errors.
32574117		NXT-22182	Some logfilesetspecifications stay on specified status
Description:		If no log messages are applicable for the specified logfilesetspecification, the logfilesetspecification stays on S(pecified), and no error is present. Also specifications with status S are not cleaned. The required fields of logfilesetspecifications generic resource metadata show following not required fields: errorMessage, fileSetStatus and dataFileSet The fileSetStatus x-oi-meaning shows "null" instead of "Specified", Processed", "Errored" The x-oi-meaning for logLevel and logType shows "null"
32577959	3-24972262511	NXT-22185	Claim line dynamic field not updated in correct step of claims flow
Description:		When claim Line dynamic field is updated via derivation rule in pre-pricing step, it gets updated after pre-benefits step only.
32590339		NXT-22209	JET: Issues with Reference sheet page
Description:		Reference Sheets JET-UI page has fields missing and does not allow creation, updation etc so the page is not usable.