Release Notes for Oracle Health Insurance Product Definition Release 3.22.1.0.0

This document contains the release notes for Oracle Health Insurance Product Definition Release 3.22.1.0.0.

Version compatibility: Oracle Health Insurance Product Definition Release 3.22.1.x is only compatible with other Oracle Health Insurance applications release version 3.22.1.x unless explicitly stated otherwise.

OHI applications expose the technical ID (created by sequence generator) in HTTP API and IP. This might be changed to an alternate technical ID (the data type might not be an integer) in a future release. Hence, it is advised to follow the generated HATEOAS links instead of hard-coding/bookmarking the IDs in the external integrations.

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
AUT-2077	New User Provisioning Features	This enhancement Introduces a new auditing table User Role History Makes it possible to remove a user even after the user has logged in Introduces a new access restriction type 'User Credentials Acl Type(USRCRD)' for accessing user credentials Updates the generic HTTP API and provisioning integration point to provide access to the new auditing information
NXT-20655	Invalidate and re-populate non-entity cache	The application keeps non-entity caches for extensibility configuration. In some scenarios it is possible for the cached content and the database to be out of sync. This situation can be resolved by restarting the server. This enhancement introduces new web service that provides an alternative to restarting the server. Calling this web service clears the non-entity cache.
NXT-21416	Use Vault as alternative secrets store with WebLogic deployments	Next to Fusion Middleware / WebLogic Oracle Platform Security Services (OPSS), OHI applications also support HashiCorp Vault as alternative secrets store. See the Installation Guide for details.
NXT-22299	RestClient Connection Pool	This enhancement introduces a REST client connection pool. Any application invoking REST calls now consume the connections from a shared connection pool, instead of creating a new connection every time. The parameters for using connection pool, e.g. Number of connections, etc, are configurable.
NXT-22658	Overview of External End-Points	This enhancement introduces a new integration point that generates an overview of all defined end-points to which the application sends messages.
NXT-22730	Increase Dynamic Field Length	This enhancement introduces the ability to update the Field on a Flex Code Field Usage. The new Field must have the same datatype and the length value cannot be smaller than the previous Field. For numbers, the number of decimals cannot be smaller than the previous Field.
NXT-23006	The TaskProcessingResource exposes the current AQ queue depth	This allows customers to monitor the backlog of work stored in the queue.
NXT-23199	Update Dynamic Record Definitions	This enhancement introduces the ability to add required fields to dynamic record definitions and flex code definition that are already in use. Changing a field from optional to required will require the user to set a value for that field the very next time when that either the record or flex code is updated, or the extended entity itself is updated. In the scenario that the user adds a new required field to a dynamic record that is linked to configuration, the user must ensure that both source and target environment are aligned in their dynamic record configuration before using the configuration migration tool to migrate the actual dynamic records.
NXT-23455	Generic API Patch Operation	This enhancement extends the existing PATCH operation in the generic API so that resources can be called by their functional key (CODE), rather than their technical ID. This eliminates the need for a query before patching.
NXT-23648	Application Owner Schema Change	The privilege SELECT ON SYS.V_$PARAMETER is no longer required in the application and is removed from the installer. This change impacts only fresh installations.	3.21.3.0.1
NXT-24203	New Integration Point to Retrieve Configuration Migration Sets	This enhancement introduces a new integration point that retrieves the list of available configuration migration sets from a specific source environment. This service enables the UI page that shows inbound data sets to include configuration migration data sets on other environments.
NXT-24489	JSON Re-Indexing Package	This enhancement introduces the package OHI_REFERENCE_SHEET_LINES_INDEX_MAINTENANCE_PKG, that creates an oracle text index OHI_REF_SHEET_LINE_IDX1 on OHI_REFERENCE_SHEET_LINES table in Oracle 19c format with Sync frequency option. This package needs to be executed in the Post-upgrade stage.
NXT-24611	Light Deployment (without ADF, with Vault)	This enhancement introduces an alternative, light deployment EAR file, in addition to the standard EAR. This new light EAR file deploys on Weblogic slim middleware and is placed under the lightApplication directory of the release zip. This deployment do not use Oracle Platform Security Services (OPSS) and does not support ADF pages.
POL-7230	Dynamic Logic Test Integration Point	This enhancement introduces a new integration point that enables dynamic logic unit tests within the application, without having to invoke the entire core process to trigger an invocation of the logic.
POL-9190	Immediate Primary Date Format Changes	This enhancement introduces the ability to change the primary date format on the default country without having to restart the server to effectuate the change.
POL-9775	Enhance Flexcode LOV template to show "additional" fields other than value and descriptor	With this enhancement, it will be possible to show additional flex code fields in addition to the value and descriptor in the JET UI.

Summary

Description

Included in Patch

AUT-2077

New User Provisioning Features

This enhancement

Introduces a new auditing table User Role History
Makes it possible to remove a user even after the user has logged in
Introduces a new access restriction type 'User Credentials Acl Type(USRCRD)' for accessing user credentials
Updates the generic HTTP API and provisioning integration point to provide access to the new auditing information

NXT-20655

Invalidate and re-populate non-entity cache

The application keeps non-entity caches for extensibility configuration. In some scenarios it is possible for the cached content and the database to be out of sync. This situation can be resolved by restarting the server.

This enhancement introduces new web service that provides an alternative to restarting the server. Calling this web service clears the non-entity cache.

NXT-21416

Use Vault as alternative secrets store with WebLogic deployments

Next to Fusion Middleware / WebLogic Oracle Platform Security Services (OPSS), OHI applications also support HashiCorp Vault as alternative secrets store. See the Installation Guide for details.

NXT-22299

RestClient Connection Pool

This enhancement introduces a REST client connection pool. Any application invoking REST calls now consume the connections from a shared connection pool, instead of creating a new connection every time. The parameters for using connection pool, e.g. Number of connections, etc, are configurable.

NXT-22658

Overview of External End-Points

This enhancement introduces a new integration point that generates an overview of all defined end-points to which the application sends messages.

NXT-22730

Increase Dynamic Field Length

This enhancement introduces the ability to update the Field on a Flex Code Field Usage. The new Field must have the same datatype and the length value cannot be smaller than the previous Field. For numbers, the number of decimals cannot be smaller than the previous Field.

NXT-23006

The TaskProcessingResource exposes the current AQ queue depth

This allows customers to monitor the backlog of work stored in the queue.

NXT-23199

Update Dynamic Record Definitions

This enhancement introduces the ability to add required fields to dynamic record definitions and flex code definition that are already in use.

Changing a field from optional to required will require the user to set a value for that field the very next time when that either the record or flex code is updated, or the extended entity itself is updated.

In the scenario that the user adds a new required field to a dynamic record that is linked to configuration, the user must ensure that both source and target environment are aligned in their dynamic record configuration before using the configuration migration tool to migrate the actual dynamic records.

NXT-23455

Generic API Patch Operation

This enhancement extends the existing PATCH operation in the generic API so that resources can be called by their functional key (CODE), rather than their technical ID. This eliminates the need for a query before patching.

NXT-23648

Application Owner Schema Change

The privilege SELECT ON SYS.V_$PARAMETER is no longer required in the application and is removed from the installer. This change impacts only fresh installations.

3.21.3.0.1

NXT-24203

New Integration Point to Retrieve Configuration Migration Sets

This enhancement introduces a new integration point that retrieves the list of available configuration migration sets from a specific source environment. This service enables the UI page that shows inbound data sets to include configuration migration data sets on other environments.

NXT-24489

JSON Re-Indexing Package

This enhancement introduces the package OHI_REFERENCE_SHEET_LINES_INDEX_MAINTENANCE_PKG, that creates an oracle text index OHI_REF_SHEET_LINE_IDX1 on OHI_REFERENCE_SHEET_LINES table in Oracle 19c format with Sync frequency option. This package needs to be executed in the Post-upgrade stage.

NXT-24611

Light Deployment (without ADF, with Vault)

This enhancement introduces an alternative, light deployment EAR file, in addition to the standard EAR. This new light EAR file deploys on Weblogic slim middleware and is placed under the lightApplication directory of the release zip. This deployment do not use Oracle Platform Security Services (OPSS) and does not support ADF pages.

POL-7230

Dynamic Logic Test Integration Point

This enhancement introduces a new integration point that enables dynamic logic unit tests within the application, without having to invoke the entire core process to trigger an invocation of the logic.

POL-9190

Immediate Primary Date Format Changes

This enhancement introduces the ability to change the primary date format on the default country without having to restart the server to effectuate the change.

POL-9775

Enhance Flexcode LOV template to show "additional" fields other than value and descriptor

With this enhancement, it will be possible to show additional flex code fields in addition to the value and descriptor in the JET UI.

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

Perform any pre-upgrade steps.
Stop all the managed nodes running the .existing version of the application.
Perform any pre-undeploy steps.
Undeploy the existing version of the application.
Back up the database.
Perform any post-undeploy steps.
Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.
Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.
Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.
Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)
Run the Upgrade script:
1. Open a command window and browse to <OHI_ROOT>/util/install.
2. Run the upgrade by executing ./ohi-update.sh .
Make the required changes to the ohi properties file
Perform any post-upgrade steps
Start WebLogic application server
Deploy the Application
Perform any post-deploy steps

Additional Upgrade Steps for Installation

The following phases are defined:

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.

Stage: pre-upgrade

Action: execute the following query to find future duplicates

select usrs.login_name
,      dupes.alias
from   ohi_users usrs
,      ohi_user_preferences uspr
,      (select uspr_id
        ,      alias
        from   ohi_bookmarks
        group  by uspr_id
        ,      alias
        having count(*) > 1
       ) dupes
where  uspr.id = dupes.uspr_id
and    usrs.id = uspr.usrs_id

This query lists bookmark aliases per user that have more than one occurrence and will violate the new unique constraint. Update the alias of the violations such that there are no more duplicates

Stage: post-undeploy

Action: Apply mandatory WebLogic patches

The following are the mandatory (minimal required) patches. Please apply them in the order listed below:

33416868: WLS PATCH SET UPDATE 12.2.1.4.210930 (OCT 2021 PSU)
32211968: ECLIPSELINK - ALL VERSIONS - GOES INTO DEAD LOCK DOING OBJECT BUILDING

After applying the above patch(es), if the managed server fails to start due to coherence errors, please follow the solution described in Doc ID 2634266.1

Stage: post-undeploy

The following steps are to be performed before running the upgrade script:

Action: Privilege changes to SYSTEM user, the below commands should be executed as SYSDBA:

GRANT SELECT ON sys.gv_$aq TO system WITH GRANT OPTION;
REVOKE SELECT ON sys.v_$parameter FROM system;
REVOKE EXECUTE ON sys.dbms_system FROM system;

Action: Privilege changes to USER schema, below command should be executed as SYSTEM user

GRANT SELECT ON sys.gv_$aq TO OHI_PRODDEF_USER;

Action: Privilege changes to OWNER schema, below commands should be executed as SYSTEM user

GRANT CREATE TRIGGER TO OHI_PRODDEF_OWNER;

Stage: post-upgrade

A new OHI_REFERENCE_SHEET_LINES_INDEX_MAINTENANCE_PKG has been provided as part of the patch. Post upgrade of the patch login as ohi_<app>_owner and execute the below command to recreate the index.

begin
  ohi_reference_sheet_lines_index_maintenance_pkg.create_index (1);
end;
/

Configuration Properties

Ref	Action	Subject	Description
NXT-21416	Added	ohi.secure.secrets.store	The type of store the OHI application uses for secrets
NXT-21416	Added	ohi.vault.environment.identifier	To distinguish secrets on a per OHI application instance basis
NXT-21416	Added	ohi.vault.clientkeypem.url	Resource URL to Vault Client Key pem
NXT-21416	Added	ohi.vault.kv.secrets.engine	By default, OHI applications assume that Vault’s Key-Value secrets engine is enabled at root path "secret"
NXT-21416	Added	ohi.vault.address	Vault address. Must use HTTPS
NXT-21416	Added	ohi.vault.namespace	OHI specific Vault namespace section, under the path determined by properties ohi.vault.kv.secrets.engine/ohi.vault.namespace to look for secrets
NXT-21416	Added	ohi.vault.clientpem.url	Resource URL to Vault Client pem
NXT-21416	Added	ohi.vault.token	Vault token
NXT-21416	Added	ohi.vault.pem.url	Resource URL to Vault pem
NXT-22299	Added	ohi.service.{0}.client.pool.destination.maxconnections	The maximum number of connections in the pool per destination for client {0}. Effective immediately for non-cached clients.
NXT-22299	Added	ohi.service.client.pool.timeout.connection	The time in milliseconds before the attempt to connect to an outbound service times out. Effective immediately for non-cached clients.
NXT-22299	Added	ohi.service.{0}.client.pool.timeout.addressresolution	The max time, in milliseconds, to resolve the host address. This property is specific to client {0}. Effective immediately for non-cached clients.
NXT-22299	Added	ohi.service.{0}.client.pool.timeout.idle	The max time, in milliseconds, a connection can be idle. This property is specific to client {0}. Effective immediately for non-cached clients.
NXT-22299	Added	ohi.service.{0}.client.pool.timeout.connection	The max time, in milliseconds, a connection can take to connect to destinations. A value of 0 means never timeout. This property is specific to clientId {0}. Effective immediately for non-cached clients.
NXT-22299	Added	ohi.service.{0}.client.pool.destination.maxqueued	The maximum number of connections in the pool allowed to be queued per destination for client {0}. Effective immediately for non-cached clients.
NXT-22299	Added	ohi.service.client.pool.active	Enable or disable to leverage connection pool functionality
NXT-22299	Added	ohi.service.client.pool.destination.maxqueued	The maximum number of connections in the pool allowed to be queued per destination. Effective immediately for non-cached clients.
NXT-22299	Added	ohi.service.client.pool.destination.maxconnections	The maximum number of connections in the pool per destination. Effective immediately for non-cached clients
NXT-22299	Added	ohi.service.client.pool.timeout.addressresolution	The max time, in milliseconds, to resolve the host address. Effective immediately for non-cached clients.
NXT-22299	Added	ohi.service.client.pool.timeout.idle	The max time, in milliseconds, a connection can be idle. Effective immediately for non-cached clients.
NXT-22299	Added	ohi.service.client.response.content.maxsize	Maximum allowed response content size in MegaBytes (MB).
PRD-2573	Added	ohi.service.client.pool.maxperroute	The number of backing connections to keep in the pool per route. Default value is 4
PRD-2573	Added	ohi.service.client.pool.maxsize	The number of backing connections to keep in the pool for the REST client. Default value is 40

Ref

Action

Subject

Description

NXT-21416

Added

ohi.secure.secrets.store

The type of store the OHI application uses for secrets

NXT-21416

Added

ohi.vault.environment.identifier

To distinguish secrets on a per OHI application instance basis

NXT-21416

Added

ohi.vault.clientkeypem.url

Resource URL to Vault Client Key pem

NXT-21416

Added

ohi.vault.kv.secrets.engine

By default, OHI applications assume that Vault’s Key-Value secrets engine is enabled at root path "secret"

NXT-21416

Added

ohi.vault.address

Vault address. Must use HTTPS

NXT-21416

Added

ohi.vault.namespace

OHI specific Vault namespace section, under the path determined by properties ohi.vault.kv.secrets.engine/ohi.vault.namespace to look for secrets

NXT-21416

Added

ohi.vault.clientpem.url

Resource URL to Vault Client pem

NXT-21416

Added

ohi.vault.token

Vault token

NXT-21416

Added

ohi.vault.pem.url

Resource URL to Vault pem

NXT-22299

Added

ohi.service.{0}.client.pool.destination.maxconnections

The maximum number of connections in the pool per destination for client {0}. Effective immediately for non-cached clients.

NXT-22299

Added

ohi.service.client.pool.timeout.connection

The time in milliseconds before the attempt to connect to an outbound service times out. Effective immediately for non-cached clients.

NXT-22299

Added

ohi.service.{0}.client.pool.timeout.addressresolution

The max time, in milliseconds, to resolve the host address. This property is specific to client {0}. Effective immediately for non-cached clients.

NXT-22299

Added

ohi.service.{0}.client.pool.timeout.idle

The max time, in milliseconds, a connection can be idle. This property is specific to client {0}. Effective immediately for non-cached clients.

NXT-22299

Added

ohi.service.{0}.client.pool.timeout.connection

The max time, in milliseconds, a connection can take to connect to destinations. A value of 0 means never timeout. This property is specific to clientId {0}. Effective immediately for non-cached clients.

NXT-22299

Added

ohi.service.{0}.client.pool.destination.maxqueued

The maximum number of connections in the pool allowed to be queued per destination for client {0}. Effective immediately for non-cached clients.

NXT-22299

Added

ohi.service.client.pool.active

Enable or disable to leverage connection pool functionality

NXT-22299

Added

ohi.service.client.pool.destination.maxqueued

The maximum number of connections in the pool allowed to be queued per destination. Effective immediately for non-cached clients.

NXT-22299

Added

ohi.service.client.pool.destination.maxconnections

The maximum number of connections in the pool per destination. Effective immediately for non-cached clients

NXT-22299

Added

ohi.service.client.pool.timeout.addressresolution

The max time, in milliseconds, to resolve the host address. Effective immediately for non-cached clients.

NXT-22299

Added

ohi.service.client.pool.timeout.idle

The max time, in milliseconds, a connection can be idle. Effective immediately for non-cached clients.

NXT-22299

Added

ohi.service.client.response.content.maxsize

Maximum allowed response content size in MegaBytes (MB).

PRD-2573

Added

ohi.service.client.pool.maxperroute

The number of backing connections to keep in the pool per route. Default value is 4

PRD-2573

Added

ohi.service.client.pool.maxsize

The number of backing connections to keep in the pool for the REST client. Default value is 40

Web Services

Ref	Action	Subject	Description
NXT-20655	Added	Non-Entity Cache Integration Point	'/api/nonentitycache/invalidateall' IP invalidates all the non entity caches. It supports POST HTTP request. Successful response returned by this IP is 204.
NXT-22658	Added	Outbound Integration Point	A new IP that shows all the outbound integration points and their endpoints
NXT-23006	Modified	Control Task Processing	The existing status response is extended with information about the number of items in the task processing queue
NXT-24203	Added	Fetch Available Datasets Integration Point	'api/dataexchange/datasets/fetchavailabledatasets/<dataSetDefinitionCode>/<dataSetVersion>' IP fetches all the datasets from the configured source environments. It supports GET HTTP request. Successful response returned by this IP is 200.
POL-7230	Added	Test Dynamic Logic Integration Point	New Integration Point

Ref

Action

Subject

Description

NXT-20655

Added

Non-Entity Cache Integration Point

'/api/nonentitycache/invalidateall' IP invalidates all the non entity caches. It supports POST HTTP request. Successful response returned by this IP is 204.

NXT-22658

Added

Outbound Integration Point

A new IP that shows all the outbound integration points and their endpoints

NXT-23006

Modified

Control Task Processing

The existing status response is extended with information about the number of items in the task processing queue

NXT-24203

Added

Fetch Available Datasets Integration Point

'api/dataexchange/datasets/fetchavailabledatasets/<dataSetDefinitionCode>/<dataSetVersion>' IP fetches all the datasets from the configured source environments. It supports GET HTTP request. Successful response returned by this IP is 200.

POL-7230

Added

Test Dynamic Logic Integration Point

New Integration Point

Data Conversion

This section intentionally left blank.

Dynamic Logic

Ref	Action	Subject	Description
POL-7230	Added	Test Unit	New signature

Ref

Action

Subject

Description

POL-7230

Added

Test Unit

New signature

UI Changes

This section intentionally left blank.

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB	SR	Internal	Summary
33641602	3-27463122071	PRD-2631	Removing column URI from OHI_BOOKMARK_UK1
Description:	In 3.21.3.0.0 unique constraint OHI_BOOKMARK_UK1 was created on the combination of user preferences, alias and URI of the bookmark. The URI column should be removed from the constraint.
Resolution:	The attribute URI is removed from the Unique Key on Bookmarks
33621653		PRD-2629	Query on generic API with a condition on child list and order by nulls first returns an error message
Description:	When making a query on any generic API, when a condition on a child list is made and also an "order by" clause with "nulls first" is added, invalid SQL is formed, so an error is returned, rather than performing the requested query.
Resolution:	The generic API no longer creates invalid SQL and performs the requested query as expected.
33476887		PRD-2599	QueryAPI with EQ operator returning 204 response when value has leading zeros
Description:	QueryAPI with EQ operator returns 204 response when the field value has leading zeros. It works fine with LIKE operator
Resolution:	QueryAPI with EQ operator returns expected response when the field value has leading zeros.
34164927		PRD-2718	Getting a large data file using data file set integration point fails with java.sql.SQLRecoverableException error
Description:	Sending a GET request to the data file set integration point for a large data file (about 1.5 GB) fails with java.sql.SQLRecoverableException
Resolution:	With this bug fix, it is now possible to download a large data file without getting an error

BugDB

Internal

Summary

33641602

3-27463122071

PRD-2631

Removing column URI from OHI_BOOKMARK_UK1

Description:

In 3.21.3.0.0 unique constraint OHI_BOOKMARK_UK1 was created on the combination of user preferences, alias and URI of the bookmark. The URI column should be removed from the constraint.

Resolution:

The attribute URI is removed from the Unique Key on Bookmarks

33621653

PRD-2629

Query on generic API with a condition on child list and order by nulls first returns an error message

Description:

When making a query on any generic API, when a condition on a child list is made and also an "order by" clause with "nulls first" is added, invalid SQL is formed, so an error is returned, rather than performing the requested query.

Resolution:

The generic API no longer creates invalid SQL and performs the requested query as expected.

33476887

PRD-2599

QueryAPI with EQ operator returning 204 response when value has leading zeros

Description:

QueryAPI with EQ operator returns 204 response when the field value has leading zeros. It works fine with LIKE operator

Resolution:

QueryAPI with EQ operator returns expected response when the field value has leading zeros.

34164927

PRD-2718

Getting a large data file using data file set integration point fails with java.sql.SQLRecoverableException error

Description:

Sending a GET request to the data file set integration point for a large data file (about 1.5 GB) fails with java.sql.SQLRecoverableException

Resolution:

With this bug fix, it is now possible to download a large data file without getting an error

Issues that were backported in previous Release / Patch

No backports.

Known Issues

BugDB	SR	Internal	Summary
24716118		PRD-1586	Accessibility - Component is not labeled
Description:	Component is not labeled, either by specifying the label attribute, or by being referred to by the 'for' attribute of a panelLabelAndMessage or outputLabel
31371956		PRD-2261	Specific Network search in view generated product page
Description:	Filter By in quick search for 'View Generated Product' page shows 'Specific Networks' twice- one for provider group and the second for assigned provider group label. But only one is expected.
31060661	3-22654524781	PRD-2288	Moving products from Edit to Review, some stay in Edit with 'valid' status'
Description:	Moving products from Edit to Review, some stay in Edit with 'valid' status'.
32477670		PRD-2488	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.
32560678		PRD-2508	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.
34169495		PRD-2726	TestDynamicLogic IP - Failure response Code is 418 instead of 400
Description:	Testdynamiclogic IP doesn’t have correct response code for unsuccessful execution of test unit. It should be 400 as it is in the implementation, but it is 418.

BugDB

Internal

Summary

24716118

PRD-1586

Accessibility - Component is not labeled

Description:

Component is not labeled, either by specifying the label attribute, or by being referred to by the 'for' attribute of a panelLabelAndMessage or outputLabel

31371956

PRD-2261

Specific Network search in view generated product page

Description:

Filter By in quick search for 'View Generated Product' page shows 'Specific Networks' twice- one for provider group and the second for assigned provider group label. But only one is expected.

31060661

3-22654524781

PRD-2288

Moving products from Edit to Review, some stay in Edit with 'valid' status'

Description:

Moving products from Edit to Review, some stay in Edit with 'valid' status'.

32477670

PRD-2488

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.

32560678

PRD-2508

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.

34169495

PRD-2726

TestDynamicLogic IP - Failure response Code is 418 instead of 400

Description:

Testdynamiclogic IP doesn’t have correct response code for unsuccessful execution of test unit. It should be 400 as it is in the implementation, but it is 418.