Release Notes for Oracle Insurance Gateway Release 3.21.1.0.0

This document contains the release notes for Oracle Insurance Gateway Release 3.21.1.0.0.

NOTE: Version compatibility: Oracle Insurance Gateway 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-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-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.
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-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-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.4
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-1513	Introduce holding the integration processing after a delivery step	Several delivery steps trigger a process in another application, like FUSION_SUBMIT. It is sometimes desired for these processes/delivery steps to finish processing before moving forward with the integration steps. This enhancement allows for the 'waiting for notification' capability to resume the exchange after a delivery step. This functionality also brings the possibility to timeout the exchange, if the notification is not received after a stipulated time. Notifications are received at the notification endpoint. Support for download messages or download data is not included, as that is intended for OHI related jobs and is covered through Process and Activity Step	3.20.3.0.3
OIG-1587	Workflow events will always contain an exception binding for the creation of workflow payload	Whenever a workflow payload needs to be created, an exception binding as part of the dynamic logic context, from now on will always be provided. This means that in dynamic logic there is no need any longer to check whether such a binding is present.	3.20.3.0.4
OIG-403	JET: User Sequence page	The new page to set up user sequence is added to Oracle Insurance Gateway user interface.
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
OIG-777	Destination Configuration: Fusion (JET)	JET User Interface pages to configure the following Fusion Destinations: Fusion Submit Job Fusion Load Import Data Fusion Run Report
OIG-928	JET: Boilerplate and messages page	Pages to maintain boilerplates and messages have been added to the Oracle Insurance Gateway application user interface.
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-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

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-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-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.

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-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-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.4

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-1513

Introduce holding the integration processing after a delivery step

Several delivery steps trigger a process in another application, like FUSION_SUBMIT. It is sometimes desired for these processes/delivery steps to finish processing before moving forward with the integration steps. This enhancement allows for the 'waiting for notification' capability to resume the exchange after a delivery step.

This functionality also brings the possibility to timeout the exchange, if the notification is not received after a stipulated time. Notifications are received at the notification endpoint. Support for download messages or download data is not included, as that is intended for OHI related jobs and is covered through Process and Activity Step

3.20.3.0.3

OIG-1587

Workflow events will always contain an exception binding for the creation of workflow payload

Whenever a workflow payload needs to be created, an exception binding as part of the dynamic logic context, from now on will always be provided. This means that in dynamic logic there is no need any longer to check whether such a binding is present.

3.20.3.0.4

OIG-403

JET: User Sequence page

The new page to set up user sequence is added to Oracle Insurance Gateway user interface.

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

OIG-777

Destination Configuration: Fusion (JET)

JET User Interface pages to configure the following Fusion Destinations:

Fusion Submit Job
Fusion Load Import Data
Fusion Run Report

OIG-928

JET: Boilerplate and messages page

Pages to maintain boilerplates and messages have been added to the Oracle Insurance Gateway application user interface.

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-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

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.jwk.set.validation.jws.signing.algorithm	Signing algorithm used by the Authorization Server.
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.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.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.token.issuers	Comma-separated string of possible token issuers
NXT-21006	Added	ohi.oauth.token.issuer.{0}	Specific issuer identifier
NXT-21006	Added	ohi.oauth.token.issuer.{0}.user.claim	Issuer-specific user claim
NXT-21006	Added	ohi.oauth.jwk.set.validation.audience	Client Id or audience claim for token validation.
NXT-21006	Added	ohi.oauth.jwk.set.validation.issuer	Issuer for token validation.
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.jwk.keystore.name
NXT-21006	Removed	ohi.oauth.jws.verification.key.selection.signing_keys_only
NXT-21006	Removed	ohi.oauth.jws.verification.key.selection.public_keys_only
NXT-21006	Removed	ohi.oauth.token.introspection.endpoint.client_secret
NXT-21006	Removed	ohi.oauth.jws.verification.key.selection.jws_algorithm
OIG-1633	Removed	SFTP Destination type configuration serverAliveCountMax	SFTP Destination type configuration serverAliveCountMax was removed
OIG-1633	Removed	SFTP Destination type configuration authenticationMethods	SFTP Destination type configuration authenticationMethods was removed

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.jwk.set.validation.jws.signing.algorithm

Signing algorithm used by the Authorization Server.

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.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.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.token.issuers

Comma-separated string of possible token issuers

NXT-21006

Added

ohi.oauth.token.issuer.{0}

Specific issuer identifier

NXT-21006

Added

ohi.oauth.token.issuer.{0}.user.claim

Issuer-specific user claim

NXT-21006

Added

ohi.oauth.jwk.set.validation.audience

Client Id or audience claim for token validation.

NXT-21006

Added

ohi.oauth.jwk.set.validation.issuer

Issuer for token validation.

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.jwk.keystore.name

NXT-21006

Removed

ohi.oauth.jws.verification.key.selection.signing_keys_only

NXT-21006

Removed

ohi.oauth.jws.verification.key.selection.public_keys_only

NXT-21006

Removed

ohi.oauth.token.introspection.endpoint.client_secret

NXT-21006

Removed

ohi.oauth.jws.verification.key.selection.jws_algorithm

OIG-1633

Removed

SFTP Destination type configuration serverAliveCountMax

SFTP Destination type configuration serverAliveCountMax was removed

OIG-1633

Removed

SFTP Destination type configuration authenticationMethods

SFTP Destination type configuration authenticationMethods was removed

Web Services

Ref	Action	Subject	Description
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
OIG-1445	Added	Objects Integration Point	New Integration Point
OIG-746	Added	Configuration Migration Integration Point	New Integration Point (part of Dataexchange)

Ref

Action

Subject

Description

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

OIG-1445

Added

Objects Integration Point

New Integration Point

OIG-746

Added

Configuration Migration Integration Point

New Integration Point (part of Dataexchange)

Data Conversion

This section intentionally left blank.

Dynamic Logic

Ref	Action	Subject	Description
OIG-1366	Added	Dynamic Logic Signature	Introduced a new signature with name "Extension"
OIG-1477	Added	AS2805_B specific dynamic logic	The AS2805_B request/response object now also exposes a synthesized property 'serviceProvider' in addition to the already existing 'providerType' property.
OIG-1491	Modified	AS2805 specific dynamic logic	The amount charged on the line items, when accessed will now strip leading zeros.
OIG-1587	Modified		Dynamic logic that constructs payload for workflow, can assume that the 'exception' binding always holds a value.
POL-6797	Added	Dynamic Logic Signature	Introduced a new signature with name "Reusable Code"

Ref

Action

Subject

Description

OIG-1366

Added

Dynamic Logic Signature

Introduced a new signature with name "Extension"

OIG-1477

Added

AS2805_B specific dynamic logic

The AS2805_B request/response object now also exposes a synthesized property 'serviceProvider' in addition to the already existing 'providerType' property.

OIG-1491

Modified

AS2805 specific dynamic logic

The amount charged on the line items, when accessed will now strip leading zeros.

OIG-1587

Modified

Dynamic logic that constructs payload for workflow, can assume that the 'exception' binding always holds a value.

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-21113	Modified	Config Migration Sets (ADF)	Added option to select floorplan while creating a migration set
NXT-21113	Modified	Floorplans page	Added floorplantagdetails tab
OIG-1366	Modified	Dynamic Logic Page	Added Base dynamic logic. This is done for both UI (ADF and Jet) where applicable.
OIG-1513	Added	IG0003	The following attributes are added to deliver step indicatorExpectNotification typeConfig Display Type: Region Region Properties: timeAllowed
OIG-403	Added	User Sequence	Added User Sequence Page
OIG-419	Added	Dynamic Logic Page	Added Dynamic Logic Page in CPN and NXT
OIG-777	Added	Fusion Submit Job, Fusion Load Import Data , Fusion Run Report Destinations	Added 3 new destination pages for fusion

Ref

Action

Subject

Description

NXT-20490

Added

Record Definitions page

New indicator PII?

NXT-20490

Added

Tables page

New indicator PII?

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

OIG-1366

Modified

Dynamic Logic Page

Added Base dynamic logic. This is done for both UI (ADF and Jet) where applicable.

OIG-1513

Added

IG0003

The following attributes are added to deliver step

indicatorExpectNotification
typeConfig
    Display Type: Region
    Region Properties:
        timeAllowed

OIG-403

Added

User Sequence

Added User Sequence Page

OIG-419

Added

Dynamic Logic Page

Added Dynamic Logic Page in CPN and NXT

OIG-777

Added

Fusion Submit Job, Fusion Load Import Data , Fusion Run Report Destinations

Added 3 new destination pages for fusion

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.

Ref

Action

Subject

Description

NXT-20490

Reporting Views

The reporting views as generated by the runnable jar are now deprecated.

Breaking Changes

Ref	Action	Subject	Description
NXT-20854	Modified	ohi.incident.datafileset.retentionperiod	The property ohi.incidents.datafileset.retentionperiod is renamed to ohi.incident.datafileset.retentionperiod
NXT-20854	Modified	ohi.incident.target	The property ohi.incidents.target is renamed to ohi.incident.target
NXT-21384	Removed	Migration behaviour	Migration between different major versions wont be possible anymore.
NXT-21528	Modified	Write Consumption Batch (claims)	The resource will return status 201 with location header instead of 202 with entity
NXT-21528	Modified	Purge (oig)	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-21528	Modified	Read Consumption Batch (claims)	The resource will return status 201 with location header instead of 202 with entity
OIG-1117			For running the OHI Agent specify at least a name for the cluster by using the Java command line property "-Dtangosol.coherence.cluster=ohi-agent". That is also required when running a single instance of the OHI Agent.
OIG-1652		HTTP Headers	The following HTTP Header names: ohi.exchange.allowed.time.ms; ohi.exchange.execute.immediately; ohi.exchange.execute.blocking; ohi.exchange.description; ohi.integration.validation.allowed.time.seconds must be changed into respectively: ohi-exchange-allowed-time-ms; ohi-exchange-execute-immediately; ohi-exchange-execute-blocking; ohi-exchange-description; ohi-integration-validation-allowed-time-seconds

Ref

Action

Subject

Description

NXT-20854

Modified

ohi.incident.datafileset.retentionperiod

The property ohi.incidents.datafileset.retentionperiod is renamed to ohi.incident.datafileset.retentionperiod

NXT-20854

Modified

ohi.incident.target

The property ohi.incidents.target is renamed to ohi.incident.target

NXT-21384

Removed

Migration behaviour

Migration between different major versions wont be possible anymore.

NXT-21528

Modified

Write Consumption Batch (claims)

The resource will return status 201 with location header instead of 202 with entity

NXT-21528

Modified

Purge (oig)

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-21528

Modified

Read Consumption Batch (claims)

The resource will return status 201 with location header instead of 202 with entity

OIG-1117

For running the OHI Agent specify at least a name for the cluster by using the Java command line property "-Dtangosol.coherence.cluster=ohi-agent". That is also required when running a single instance of the OHI Agent.

OIG-1652

HTTP Headers

The following HTTP Header names: ohi.exchange.allowed.time.ms; ohi.exchange.execute.immediately; ohi.exchange.execute.blocking; ohi.exchange.description; ohi.integration.validation.allowed.time.seconds must be changed into respectively: ohi-exchange-allowed-time-ms; ohi-exchange-execute-immediately; ohi-exchange-execute-blocking; ohi-exchange-description; ohi-integration-validation-allowed-time-seconds

Bug Fixes

BugDB	SR	Internal	Summary
31613557		OIG-1016	"Recover" button is not working, when user navigate to view log lines page and come back to exchange details page.
Description:	Recover button is not working when user click on it after navigating back to the exchange details page from view log lines page.
Resolution:	Now confirmation message is displayed to user, when user click on recover button in exchange details page after navigating to the view log lines page and come back to exchange details page.
31919956	3-24083438201	OIG-1280	Agent retrieves up to 50 configurations from OIG
Description:	The agent only retrieved the first 50 configurations.
Resolution:	Agent now retrieves all configurations.
31937755	3-24132371461	OIG-1295	HICAPS Cancellation transaction failing with unmatched cancel response code 81
Description:	On non-default context-roots, e.g. /wls-api/ instead of /api/ for OHI Claims, OIG will construct wrong URLs for cancellation, and as a result HICAPS cancellation won’t be issued to OHI Claims.
Resolution:	With this change the Location header that is returned from the original HICAPS Claims operation is properly dissected into its constituting parts, and will then subsequently be used to construct HICAPS cancellation requests URLs appropriately.
-		OIG-1306	Integration validation will result in NPE when debugging is enabled.
Description:	When debugging is enabled for OIG globally or on the namespace 'com.oracle.healthinsurance.integration.gateway.impl.endpoints' a NullPointerException (NPE) will be thrown, causing the exchange not to be triggered.
Resolution:	The specific logging statement has been made null safe.
31959541		OIG-1309	Generic JET UI bug: unable to specify a logout URL
Description:	There is no property to define the logoutURL for the JET UI. This is especially problematic in an SSO environment where the SSO setup needs to trigger logout based on a specific URL.
Resolution:	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".
31964795	3-24170040331	OIG-1321	Element Id shows as null when messages are collected
Description:	ElementId is missing in the messages notificationCollectMessages. This is a crucial piece of info for premium calc run since the elementId contains the group client code.
Resolution:	Messages collected in OIG also collect Element Id along with the message if it exists in the messages.
32007562		OIG-1336	"AS2805_A Agent Configuration" and " AS2805_B Agent Configurations" page headers are not displaying as per the requirement.
Description:	Steps to Reproduce: 1) Navigate to configuration tab. 2) Click on "System" sub menu and select "AS2805_A Agent Configuration" link. Expected Results: page header should be displayed as "Agent Configuration AS2805_A" Actual Results: page header is displayed as "Agent Configuration AS 2805 _ AS" Same behavior is observed in "AS2805_B Agent Configurations" page as well.
Resolution:	AS2805_A Agent Configuration and AS2805_B Agent Configurations page show proper header
32007605		OIG-1337	Create page displays the boilerplate text for "AS2805_A Agent Configuration" and " AS2805_B Agent Configurations" pages.
Description:	Create page displays the boilerplate text for "AS2805_A Agent Configuration" and " AS2805_B Agent Configurations" pages.
Resolution:	Create page in AS2805_A and AS2805_B Agent Configuration pages load and display all the boilerplate text.
32006654		OIG-1362	HICAPS Claim authorization transactions having invalid response code(4 bytes instead of 2 bytes)
Description:	The HICAPS response code uses 4 bytes, instead of 2 bytes. This results in wrong/garbled results on the HICAPS terminal.
Resolution:	2 bytes are used for the HICAPS response code, making the HICAPS terminal receipt meaningful again.
32019204		OIG-1374	Access Restrictions not working in Credentials page
Description:	Access Restrictions not working in Credentials page, all users are able to access the page and perform all operations neglecting access restrictions.
Resolution:	Now users can perform only those CRUD actions for which they have access in Credentials page
32019141		OIG-1375	Access Restrictions are not working as expected for submenu pages
Description:	Access Restrictions are not working as expected for submenu pages. Pages are not getting displayed as per the assigned access restrictions for the role.
Resolution:	Now users can perform only those CRUD actions for which they have access for submenu pages in the application.
32070282	3-24344763491	OIG-1394	Purge Exchanges does not purge the exchange steps that refer to the exchanges to be purged
Description:	Purge exchanges Integration Point could lead an error (OIG_EXCHANGE_FK3) when exchanges with multiple levels (subflows) where to be deleted
Resolution:	When purging exchanges with subflows, all levels of the exchange are purged. The purge conditions are applied to the main exchange and all steps and exchanges originating from that main exchange will be purged as well. The rows purged indicates the amount of main exchanges deleted.
32073639		OIG-1397	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.
32113666	3-24409319631	OIG-1443	XMLWRITERS should not be flushed or closed if they are already in closed state
Description:	XMLWRITERS were being closed once from the framework and once by the dynamic logic coder. As a result the second closure giving null pointer exception.
Resolution:	The explicit flush operation was removed as it was a null unsafe operation of jdk. However the close operation of jdk is inplicitly calling flush, which makes it both a null safe and a useful operation. Hence explicit flush was no longer needed.
32139386	3-24383223221	OIG-1465	SFTP Destinations do not require address or authentication checks for validation
Description:	In the present scenario, SFTP destinations are validated with address key and authentication checks. As a result we are getting specific message errors, in the validation context of the same
Resolution:	For SFTP destinations, only credential key validation is kept, and address key and authentication checks are removed. An integration test is added to verify the functionality.
32150472		OIG-1469	OIG Agent does not relay Claim Quote messages to the OIG Gateway
Description:	It was observed that a 'Claim Quote' (0200-171000) originating from the HICAPS switch was not relayed by the OIG Agent to the OIG Gateway. This resulted in a timeout on the HICAPS terminal. There was nothing in the OIG Gateway logs that indicated that a 'Claim Quote' was actually received, nor in the OIG Agent logs that a 'Claim Quote' was (functionality) handled.
Resolution:	The AS2805_A Message Handler in the OIG Agent missed a condition to accept 'Claim Quote' messages coming down the wire. The result of this was that those messages were dropped. We have now fixed that situation, so 'Claim Quote' messages are now picked up and actually relayed to the OIG Gateway.
32173023		OIG-1484	Unable to redirect to View mode after performing edit operation
Description:	User is not able to redirect to view mode after performing edit operations for all HRR pages.
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
32174016		OIG-1487	Credentials Page - Back functionality is not working as expected
Description:	Steps to reproduce: Provide required data for credentials and click on Save. Expected: Page should stay on Credentials view-edit page Actual: Page navigated to Configurations primary menu landing page.
Resolution:	Now page correctly navigates to credentials search result page when clicked on save or cancel.
32179986		OIG-1492	Enabled and Active check boxes are not checked by default on create page
Description:	On integrations create page the Enabled? checkbox should be checked by default. On messages create page the Active checkbox should be checked by default.
Resolution:	Enabled? in create Integration page and Active in create Messages page is checked as default.
32179560	3-24514949761	OIG-1494	Multiple issues in Config Migration when trying to import DataSets through API
Description:	The following issues with configuration migration import process via api (dataexchanges) occur 1. An exception is shown in the logfile when at the end of an import the temporary file needs to be deleted 2. When a createandexport request is posted only with code (and no description), this caused later import processes to fail.
Resolution:	The createandexport for dataexchange will use the code of the set as description when a description is not provided. The error message about deleting temporary is not present anymore
32180011		OIG-1495	Integrations Page - Enabled? label color is not displaying as expected in search results
Description:	When a search is done on integrations, disabled integrations show with Disabled label in red color instead of grey
Resolution:	Disabled integrations label color is grey.
32193160		OIG-1507	Error message does not go away on cancel in invoke exchange page
Description:	1) Invoke an exchange with an error message to be displayed. 2) Click on "Cancel" button. 3) Click on "Ok" button in the cancel confirmation popup. Expected Results: Exchanges landing page should be displayed. Actual Results: Exchanges landing page along with the error message is displayed.
Resolution:	Now error message is not displayed in the UI, when user click on the back to navigation link or click on "OK" button in the cancel confirmation popup after getting any error message in the page.
32200189	3-24598189581	OIG-1515	Member identifier missing on AS2805_A Claim responses when transaction/quote fails
Description:	For AS2805_A claim quote/transaction interchanges a duplicated transaction detected by the Gateway, resulted in the member identifier not being present as part of the AS2805_A response message (field #48, additional data private). This manifested itself on the receipt printed at the terminal where the repeated elements (claim line) were wrongly offset on the print-out leading to meaningless data.
Resolution:	The Australian/AS2805 localization now exposes a dynamic logic setter property, with which the customer can inject the member identifier into the exchange properties as part of the incoming request message (for OHI Claims). This can and should be used in favor of a similar property on the (transformation) dynamic logic for the outgoing response message (for OIG Agent/AS2805_A switch), as that (transformation) dynamic logic will not be invoked whenever the system detects a duplicate. In case this setter property is not used and a duplicate is detected, the system will fall-back to using '00000000' as member identifier for the AS2805_A claim transaction/quote response message.
32233293		OIG-1558	Member identifier missing on AS2805_B Claim responses when transaction fails
Description:	For AS2805_B claim transaction interchanges that run into an unforeseen issue result in the member identifier not being present as part of the AS2805_B response message (field #48, additional data private). This manifests itself on the receipt printed at the terminal where the repeated elements (claim line) are wrongly offset on the print-out leading to meaningless data.
Resolution:	The Australian/AS2805 localization now exposes a dynamic logic setter property, with which the customer can inject the member identifier into the exchange properties as part of the incoming request message (for OHI Claims). This can and should be used in favor of a similar property on the (transformation) dynamic logic for the outgoing response message (for OIG Agent/AS2805_B front end processor), as that (transformation) dynamic logic will not be invoked whenever the system runs into an issue. In case this setter property is not used and an unforeseen issue arises, the system will fall-back to using '0000000000' as member identifier for the AS2805_B claim transaction response message.
32462461		OIG-1570	An error is coming when user tries to save the LOV value without selecting from the search results
Description:	An error is coming when user tries 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.
32363922	3-24886233961	OIG-1621	Extracts do not work with subflows
Description:	Incremental extracts with subflows do not return any results as the previous exchanges are not correctly fetched.
Resolution:	Incremental extracts now work with subflows. The previous parent exchanges are correctly fetched.
32417952	3-25003397991	OIG-1652	Replace dots ( . ) in headers with dashes ( - ) to follow networking conventions
Description:	HTTP Headers using dot-notation ran the risk of being removed from an HTTP request by components like gateways or loadbalancers.
Resolution:	Dots ( . ) in HTTP headers are replaced by dashes ( - ) to follow networking (infrastructure) conventions. This should prevent these HTTP Headers from being removed from requests by components like gateways or loadbalancers.
32421199	3-24598189581	OIG-1654	Member Identifier missing on as2805 claim responses when transaction/quote fails.
Description:	The information of the private data field (field #48) of the claim transaction/quote response includes the member identifier but is missing the approved amount and item response code. This results in the receipt printed at the terminal to contain garbled data. It turns out that the original fix (listed as bug: 32200189, OIG-1515) is not complete.
Resolution:	The implementation was corrected to properly include the approved amount and item response code per line item present.
32421493		OIG-1656	Member Identifier and line items missing on as2805 cancellation responses
Description:	The information of the private data field (field #48) of the claim cancellation response includes the member identifier but is missing the 'canceled amount' and item response code. This results in the receipt printed at the terminal to contain garbled data. It turns out that the original fix (listed as bug: 32257926, OIG-1585) is not complete.
Resolution:	The implementation is corrected to properly include the 'canceled amount' and item response code per line item present.
32433633		OIG-1672	DataExchange Notifications are not sent
Description:	With the properties for dataexchange notification set, no notifications arrive at the endpoint (ohi.datasetoperations.notification.endpoint.import/export)
Resolution:	Notifications will be send for DataExchangeImport/DataExchangeExport to the endpoint configured in ohi.datasetoperations.notification.endpoint.import/export.
32438878		OIG-1679	OIG Access Restriction 'IG0004' is missing in 3.20.3.0.x release
Description:	IG0004 is removed in 3.20.3 release and deprecated. IG0004 should be removed through liquibase so that customers won’t get error while migrating
Resolution:	A liquibase script is provided to remove ACCESS RESTRICTION 'IG0004' since it is not used anymore from 3.20.3 release
32446318		OIG-1683	CMT - Error while importing HICAPS/HEALTHPOINT Integrations
Description:	Integrations in OIG have a unique key on type, code and version. Config Migration Import was not taking care of the composite unique key and hence the bug.
Resolution:	Config Migration Import is changed to take the composite unique key in account while importing.
32467075	3-25061602621	OIG-1691	Boilerplates are missing from seeddata in 3.20.2.0.0 release
Description:	In release 3.20.2.0.0 the below listed boilerplates are deleted from seed data. DOMAIN_DESTINATIONTYPEGATEWAY_REST, DOMAIN_INTEGRATIONSUBSTEP_PUBLISHDOCUMAKERDOCUMENT, DOMAIN_TOKENVALIDATIONMETHOD_OAM_ENDPOINT, DOMAIN_TOKENVALIDATIONMETHOD_OAUTH2_ENDPOINT, DOMAIN_TOKENVALIDATIONMETHOD_JWKSET, DOMAIN_DESTINATIONTYPEGATEWAY_FILEUPLOAD, OIG_GATEWAYAGENTCONFIGURATIONINTEGRATION_TITLE_SINGULAR, DOMAIN_DESTINATIONTYPE_SOAP, DOMAIN_INTEGRATIONSUBSTEP_SUBMITIMPORTJOB, DOMAIN_INTEGRATIONSUBSTEP_SUBMITLOADJOB, DOMAIN_INTEGRATIONSUBSTEP_UPLOADTOUCM, DOMAIN_DESTINATIONTYPEGATEWAY_SFTP, DOMAIN_DESTINATIONTYPEGATEWAY_AGENT, DOMAIN_INTEGRATIONSUBSTEP_SUBFLOWSTEPFINISH, DOMAIN_AGENTCONFIGTYPE_OUT-FOLDER, DOMAIN_AGENTCONFIGTYPE_IN-FOLDER, OIG_GATEWAYAGENTCONFIGURATIONINTEGRATION_TITLE_PLURAL, CUSTOM_EXCHANGE_FIELD_PAYLOAD, DOMAIN_DESTINATIONTYPEGATEWAY_SOAP, DOMAIN_INTEGRATIONSUBSTEP_SUBFLOWSTEPSTART, DOMAIN_INTEGRATIONSUBSTEP_CHECKJOBSTATUS
Resolution:	The following boilerplates are added back in 3.20.3.0.3 patch since they are still used in OHI. DOMAIN_INTEGRATIONSUBSTEP_CHECKJOBSTATUS DOMAIN_INTEGRATIONSUBSTEP_PUBLISHDOCUMAKERDOCUMENT DOMAIN_INTEGRATIONSUBSTEP_SUBMITIMPORTJOB DOMAIN_INTEGRATIONSUBSTEP_SUBMITLOADJOB DOMAIN_INTEGRATIONSUBSTEP_UPLOADTOUCM
32468679		OIG-1694	Task is stuck in 'PROCESSING' status if the node leaves the cluster
Description:	Currently if a node fails, its tasks are not failover-ed to other nodes, they remain in status Processing.
Resolution:	In case a node fails, all its tasks will be failover-ed correctly to the other nodes with this fix.
32477436		OIG-1699	CMT process hangs if interrupted and does not allow running any new CMT process
Description:	CMT process hangs if interrupted and does not allow running any new CMT process. Steps to reproduce are: 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 interrupted CMT process ends in a failed status after restart of the node(s), and a new CMT process can be started again.
32560815	3-25110446171	OIG-1786	Resource name is incorrectly extracted from x-oi-reference-link properties
Description:	While parsing the metadata for destinations , the addressKey and credentialKey properties are encountered which have an x-oi-reference-link that provides a link to query values for these properties. Since the resource definition url is not available, the resource name has to be extracted from the x-oi-reference-link url. This was being done by splitting on "/api". Since this is a part of context-url which is configurable and not static, this resulted in an error in the cloud deployment where the context url is "oig-api/" and the page could not be loaded as a result.
Resolution:	The resource name is extracted correctly from the x-oi-reference-link property without hard coding any part of the context url such as "/api".
30758818		OIG-426	Issue with Mutiple Activity Import in the same integration
Description:	In case there are multiple activities in the same integration that are file-import, the implicit parameters for file upload were not filled up correctly.
Resolution:	With this bug fix, implicit parameters are filled up correctly and multiple file import activity work correctly.
31550482		OIG-905	Cosmetic issues in view sub exchanges page.
Description:	1) Sub Exchanges page header is displayed as "Exchanges". 2) Header of the Filter component need to be displayed as "Sub Exchanges Status". 3) "Exchange Status" column of table need to be replaced as "Sub Exchanges Status".
Resolution:	Sub Exchanges page header is correctly displayed as Sub Exchanges. Column names are renamed as "Sub Exchanges" in all sub-exchange pages.
31553442		OIG-959	"View Sub Exchanges" link should be Shown only for "Subflow Step Creator" integration sub step type
Description:	"View Sub Exchanges" link should be Shown only for "Subflow Step Creator" integration sub step type
Resolution:	Have disabled "View Sub Exchanges" for all sub step other than "Subflow Step Creator" integration sub step type

BugDB

Internal

Summary

31613557

OIG-1016

"Recover" button is not working, when user navigate to view log lines page and come back to exchange details page.

Description:

Recover button is not working when user click on it after navigating back to the exchange details page from view log lines page.

Resolution:

Now confirmation message is displayed to user, when user click on recover button in exchange details page after navigating to the view log lines page and come back to exchange details page.

31919956

3-24083438201

OIG-1280

Agent retrieves up to 50 configurations from OIG

Description:

The agent only retrieved the first 50 configurations.

Resolution:

Agent now retrieves all configurations.

31937755

3-24132371461

OIG-1295

HICAPS Cancellation transaction failing with unmatched cancel response code 81

Description:

On non-default context-roots, e.g. /wls-api/ instead of /api/ for OHI Claims, OIG will construct wrong URLs for cancellation, and as a result HICAPS cancellation won’t be issued to OHI Claims.

Resolution:

With this change the Location header that is returned from the original HICAPS Claims operation is properly dissected into its constituting parts, and will then subsequently be used to construct HICAPS cancellation requests URLs appropriately.

OIG-1306

Integration validation will result in NPE when debugging is enabled.

Description:

When debugging is enabled for OIG globally or on the namespace 'com.oracle.healthinsurance.integration.gateway.impl.endpoints' a NullPointerException (NPE) will be thrown, causing the exchange not to be triggered.

Resolution:

The specific logging statement has been made null safe.

31959541

OIG-1309

Generic JET UI bug: unable to specify a logout URL

Description:

There is no property to define the logoutURL for the JET UI. This is especially problematic in an SSO environment where the SSO setup needs to trigger logout based on a specific URL.

Resolution:

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".

31964795

3-24170040331

OIG-1321

Element Id shows as null when messages are collected

Description:

ElementId is missing in the messages notificationCollectMessages. This is a crucial piece of info for premium calc run since the elementId contains the group client code.

Resolution:

Messages collected in OIG also collect Element Id along with the message if it exists in the messages.

32007562

OIG-1336

"AS2805_A Agent Configuration" and " AS2805_B Agent Configurations" page headers are not displaying as per the requirement.

Description:

Steps to Reproduce: 1) Navigate to configuration tab. 2) Click on "System" sub menu and select "AS2805_A Agent Configuration" link. Expected Results: page header should be displayed as "Agent Configuration AS2805_A" Actual Results: page header is displayed as "Agent Configuration AS 2805 _ AS" Same behavior is observed in "AS2805_B Agent Configurations" page as well.

Resolution:

AS2805_A Agent Configuration and AS2805_B Agent Configurations page show proper header

32007605

OIG-1337

Create page displays the boilerplate text for "AS2805_A Agent Configuration" and " AS2805_B Agent Configurations" pages.

Description:

Create page displays the boilerplate text for "AS2805_A Agent Configuration" and " AS2805_B Agent Configurations" pages.

Resolution:

Create page in AS2805_A and AS2805_B Agent Configuration pages load and display all the boilerplate text.

32006654

OIG-1362

HICAPS Claim authorization transactions having invalid response code(4 bytes instead of 2 bytes)

Description:

The HICAPS response code uses 4 bytes, instead of 2 bytes. This results in wrong/garbled results on the HICAPS terminal.

Resolution:

2 bytes are used for the HICAPS response code, making the HICAPS terminal receipt meaningful again.

32019204

OIG-1374

Access Restrictions not working in Credentials page

Description:

Access Restrictions not working in Credentials page, all users are able to access the page and perform all operations neglecting access restrictions.

Resolution:

Now users can perform only those CRUD actions for which they have access in Credentials page

32019141

OIG-1375

Access Restrictions are not working as expected for submenu pages

Description:

Access Restrictions are not working as expected for submenu pages. Pages are not getting displayed as per the assigned access restrictions for the role.

Resolution:

Now users can perform only those CRUD actions for which they have access for submenu pages in the application.

32070282

3-24344763491

OIG-1394

Purge Exchanges does not purge the exchange steps that refer to the exchanges to be purged

Description:

Purge exchanges Integration Point could lead an error (OIG_EXCHANGE_FK3) when exchanges with multiple levels (subflows) where to be deleted

Resolution:

When purging exchanges with subflows, all levels of the exchange are purged. The purge conditions are applied to the main exchange and all steps and exchanges originating from that main exchange will be purged as well. The rows purged indicates the amount of main exchanges deleted.

32073639

OIG-1397

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.

32113666

3-24409319631

OIG-1443

XMLWRITERS should not be flushed or closed if they are already in closed state

Description:

XMLWRITERS were being closed once from the framework and once by the dynamic logic coder. As a result the second closure giving null pointer exception.

Resolution:

The explicit flush operation was removed as it was a null unsafe operation of jdk. However the close operation of jdk is inplicitly calling flush, which makes it both a null safe and a useful operation. Hence explicit flush was no longer needed.

32139386

3-24383223221

OIG-1465

SFTP Destinations do not require address or authentication checks for validation

Description:

In the present scenario, SFTP destinations are validated with address key and authentication checks. As a result we are getting specific message errors, in the validation context of the same

Resolution:

For SFTP destinations, only credential key validation is kept, and address key and authentication checks are removed. An integration test is added to verify the functionality.

32150472

OIG-1469

OIG Agent does not relay Claim Quote messages to the OIG Gateway

Description:

It was observed that a 'Claim Quote' (0200-171000) originating from the HICAPS switch was not relayed by the OIG Agent to the OIG Gateway. This resulted in a timeout on the HICAPS terminal. There was nothing in the OIG Gateway logs that indicated that a 'Claim Quote' was actually received, nor in the OIG Agent logs that a 'Claim Quote' was (functionality) handled.

Resolution:

The AS2805_A Message Handler in the OIG Agent missed a condition to accept 'Claim Quote' messages coming down the wire. The result of this was that those messages were dropped. We have now fixed that situation, so 'Claim Quote' messages are now picked up and actually relayed to the OIG Gateway.

32173023

OIG-1484

Unable to redirect to View mode after performing edit operation

Description:

User is not able to redirect to view mode after performing edit operations for all HRR pages.

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

32174016

OIG-1487

Credentials Page - Back functionality is not working as expected

Description:

Steps to reproduce: Provide required data for credentials and click on Save. Expected: Page should stay on Credentials view-edit page Actual: Page navigated to Configurations primary menu landing page.

Resolution:

Now page correctly navigates to credentials search result page when clicked on save or cancel.

32179986

OIG-1492

Enabled and Active check boxes are not checked by default on create page

Description:

On integrations create page the Enabled? checkbox should be checked by default. On messages create page the Active checkbox should be checked by default.

Resolution:

Enabled? in create Integration page and Active in create Messages page is checked as default.

32179560

3-24514949761

OIG-1494

Multiple issues in Config Migration when trying to import DataSets through API

Description:

The following issues with configuration migration import process via api (dataexchanges) occur 1. An exception is shown in the logfile when at the end of an import the temporary file needs to be deleted 2. When a createandexport request is posted only with code (and no description), this caused later import processes to fail.

Resolution:

The createandexport for dataexchange will use the code of the set as description when a description is not provided. The error message about deleting temporary is not present anymore

32180011

OIG-1495

Integrations Page - Enabled? label color is not displaying as expected in search results

Description:

When a search is done on integrations, disabled integrations show with Disabled label in red color instead of grey

Resolution:

Disabled integrations label color is grey.

32193160

OIG-1507

Error message does not go away on cancel in invoke exchange page

Description:

1) Invoke an exchange with an error message to be displayed. 2) Click on "Cancel" button. 3) Click on "Ok" button in the cancel confirmation popup. Expected Results: Exchanges landing page should be displayed. Actual Results: Exchanges landing page along with the error message is displayed.

Resolution:

Now error message is not displayed in the UI, when user click on the back to navigation link or click on "OK" button in the cancel confirmation popup after getting any error message in the page.

32200189

3-24598189581

OIG-1515

Member identifier missing on AS2805_A Claim responses when transaction/quote fails

Description:

For AS2805_A claim quote/transaction interchanges a duplicated transaction detected by the Gateway, resulted in the member identifier not being present as part of the AS2805_A response message (field #48, additional data private). This manifested itself on the receipt printed at the terminal where the repeated elements (claim line) were wrongly offset on the print-out leading to meaningless data.

Resolution:

The Australian/AS2805 localization now exposes a dynamic logic setter property, with which the customer can inject the member identifier into the exchange properties as part of the incoming request message (for OHI Claims). This can and should be used in favor of a similar property on the (transformation) dynamic logic for the outgoing response message (for OIG Agent/AS2805_A switch), as that (transformation) dynamic logic will not be invoked whenever the system detects a duplicate. In case this setter property is not used and a duplicate is detected, the system will fall-back to using '00000000' as member identifier for the AS2805_A claim transaction/quote response message.

32233293

OIG-1558

Member identifier missing on AS2805_B Claim responses when transaction fails

Description:

For AS2805_B claim transaction interchanges that run into an unforeseen issue result in the member identifier not being present as part of the AS2805_B response message (field #48, additional data private). This manifests itself on the receipt printed at the terminal where the repeated elements (claim line) are wrongly offset on the print-out leading to meaningless data.

Resolution:

The Australian/AS2805 localization now exposes a dynamic logic setter property, with which the customer can inject the member identifier into the exchange properties as part of the incoming request message (for OHI Claims). This can and should be used in favor of a similar property on the (transformation) dynamic logic for the outgoing response message (for OIG Agent/AS2805_B front end processor), as that (transformation) dynamic logic will not be invoked whenever the system runs into an issue. In case this setter property is not used and an unforeseen issue arises, the system will fall-back to using '0000000000' as member identifier for the AS2805_B claim transaction response message.

32462461

OIG-1570

An error is coming when user tries to save the LOV value without selecting from the search results

Description:

An error is coming when user tries 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.

32363922

3-24886233961

OIG-1621

Extracts do not work with subflows

Description:

Incremental extracts with subflows do not return any results as the previous exchanges are not correctly fetched.

Resolution:

Incremental extracts now work with subflows. The previous parent exchanges are correctly fetched.

32417952

3-25003397991

OIG-1652

Replace dots ( . ) in headers with dashes ( - ) to follow networking conventions

Description:

HTTP Headers using dot-notation ran the risk of being removed from an HTTP request by components like gateways or loadbalancers.

Resolution:

Dots ( . ) in HTTP headers are replaced by dashes ( - ) to follow networking (infrastructure) conventions. This should prevent these HTTP Headers from being removed from requests by components like gateways or loadbalancers.

32421199

3-24598189581

OIG-1654

Member Identifier missing on as2805 claim responses when transaction/quote fails.

Description:

The information of the private data field (field #48) of the claim transaction/quote response includes the member identifier but is missing the approved amount and item response code. This results in the receipt printed at the terminal to contain garbled data. It turns out that the original fix (listed as bug: 32200189, OIG-1515) is not complete.

Resolution:

The implementation was corrected to properly include the approved amount and item response code per line item present.

32421493

OIG-1656

Member Identifier and line items missing on as2805 cancellation responses

Description:

The information of the private data field (field #48) of the claim cancellation response includes the member identifier but is missing the 'canceled amount' and item response code. This results in the receipt printed at the terminal to contain garbled data. It turns out that the original fix (listed as bug: 32257926, OIG-1585) is not complete.

Resolution:

The implementation is corrected to properly include the 'canceled amount' and item response code per line item present.

32433633

OIG-1672

DataExchange Notifications are not sent

Description:

With the properties for dataexchange notification set, no notifications arrive at the endpoint (ohi.datasetoperations.notification.endpoint.import/export)

Resolution:

Notifications will be send for DataExchangeImport/DataExchangeExport to the endpoint configured in ohi.datasetoperations.notification.endpoint.import/export.

32438878

OIG-1679

OIG Access Restriction 'IG0004' is missing in 3.20.3.0.x release

Description:

IG0004 is removed in 3.20.3 release and deprecated. IG0004 should be removed through liquibase so that customers won’t get error while migrating

Resolution:

A liquibase script is provided to remove ACCESS RESTRICTION 'IG0004' since it is not used anymore from 3.20.3 release

32446318

OIG-1683

CMT - Error while importing HICAPS/HEALTHPOINT Integrations

Description:

Integrations in OIG have a unique key on type, code and version. Config Migration Import was not taking care of the composite unique key and hence the bug.

Resolution:

Config Migration Import is changed to take the composite unique key in account while importing.

32467075

3-25061602621

OIG-1691

Boilerplates are missing from seeddata in 3.20.2.0.0 release

Description:

In release 3.20.2.0.0 the below listed boilerplates are deleted from seed data.

DOMAIN_DESTINATIONTYPEGATEWAY_REST, DOMAIN_INTEGRATIONSUBSTEP_PUBLISHDOCUMAKERDOCUMENT, DOMAIN_TOKENVALIDATIONMETHOD_OAM_ENDPOINT, DOMAIN_TOKENVALIDATIONMETHOD_OAUTH2_ENDPOINT, DOMAIN_TOKENVALIDATIONMETHOD_JWKSET, DOMAIN_DESTINATIONTYPEGATEWAY_FILEUPLOAD, OIG_GATEWAYAGENTCONFIGURATIONINTEGRATION_TITLE_SINGULAR, DOMAIN_DESTINATIONTYPE_SOAP, DOMAIN_INTEGRATIONSUBSTEP_SUBMITIMPORTJOB, DOMAIN_INTEGRATIONSUBSTEP_SUBMITLOADJOB, DOMAIN_INTEGRATIONSUBSTEP_UPLOADTOUCM, DOMAIN_DESTINATIONTYPEGATEWAY_SFTP, DOMAIN_DESTINATIONTYPEGATEWAY_AGENT, DOMAIN_INTEGRATIONSUBSTEP_SUBFLOWSTEPFINISH, DOMAIN_AGENTCONFIGTYPE_OUT-FOLDER, DOMAIN_AGENTCONFIGTYPE_IN-FOLDER, OIG_GATEWAYAGENTCONFIGURATIONINTEGRATION_TITLE_PLURAL, CUSTOM_EXCHANGE_FIELD_PAYLOAD, DOMAIN_DESTINATIONTYPEGATEWAY_SOAP, DOMAIN_INTEGRATIONSUBSTEP_SUBFLOWSTEPSTART, DOMAIN_INTEGRATIONSUBSTEP_CHECKJOBSTATUS

Resolution:

The following boilerplates are added back in 3.20.3.0.3 patch since they are still used in OHI. DOMAIN_INTEGRATIONSUBSTEP_CHECKJOBSTATUS DOMAIN_INTEGRATIONSUBSTEP_PUBLISHDOCUMAKERDOCUMENT DOMAIN_INTEGRATIONSUBSTEP_SUBMITIMPORTJOB DOMAIN_INTEGRATIONSUBSTEP_SUBMITLOADJOB DOMAIN_INTEGRATIONSUBSTEP_UPLOADTOUCM

32468679

OIG-1694

Task is stuck in 'PROCESSING' status if the node leaves the cluster

Description:

Currently if a node fails, its tasks are not failover-ed to other nodes, they remain in status Processing.

Resolution:

In case a node fails, all its tasks will be failover-ed correctly to the other nodes with this fix.

32477436

OIG-1699

CMT process hangs if interrupted and does not allow running any new CMT process

Description:

CMT process hangs if interrupted and does not allow running any new CMT process.

Steps to reproduce are: 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 interrupted CMT process ends in a failed status after restart of the node(s), and a new CMT process can be started again.

32560815

3-25110446171

OIG-1786

Resource name is incorrectly extracted from x-oi-reference-link properties

Description:

While parsing the metadata for destinations , the addressKey and credentialKey properties are encountered which have an x-oi-reference-link that provides a link to query values for these properties. Since the resource definition url is not available, the resource name has to be extracted from the x-oi-reference-link url. This was being done by splitting on "/api". Since this is a part of context-url which is configurable and not static, this resulted in an error in the cloud deployment where the context url is "oig-api/" and the page could not be loaded as a result.

Resolution:

The resource name is extracted correctly from the x-oi-reference-link property without hard coding any part of the context url such as "/api".

30758818

OIG-426

Issue with Mutiple Activity Import in the same integration

Description:

In case there are multiple activities in the same integration that are file-import, the implicit parameters for file upload were not filled up correctly.

Resolution:

With this bug fix, implicit parameters are filled up correctly and multiple file import activity work correctly.

31550482

OIG-905

Cosmetic issues in view sub exchanges page.

Description:

1) Sub Exchanges page header is displayed as "Exchanges". 2) Header of the Filter component need to be displayed as "Sub Exchanges Status". 3) "Exchange Status" column of table need to be replaced as "Sub Exchanges Status".

Resolution:

Sub Exchanges page header is correctly displayed as Sub Exchanges. Column names are renamed as "Sub Exchanges" in all sub-exchange pages.

31553442

OIG-959

"View Sub Exchanges" link should be Shown only for "Subflow Step Creator" integration sub step type

Description:

"View Sub Exchanges" link should be Shown only for "Subflow Step Creator" integration sub step type

Resolution:

Have disabled "View Sub Exchanges" for all sub step other than "Subflow Step Creator" integration sub step type

Issues that were backported in previous Release / Patch

BugDB	Internal	Summary	Backport	BugDB	SR
31919956	OIG-1280	Agent retrieves up to 50 configurations from OIG	3.20.2.0.4	31960308	3-24083438201
31919956	OIG-1280	Agent retrieves up to 50 configurations from OIG	3.20.3.0.0	31920092	3-24083438201
31959541	OIG-1309	Generic JET UI bug: unable to specify a logout URL	3.20.2.0.4	31953187
31964795	OIG-1321	Element Id shows as null when messages are collected	3.20.3.0.0	31964805	3-24170040331
32007562	OIG-1336	"AS2805_A Agent Configuration" and " AS2805_B Agent Configurations" page headers are not displaying as per the requirement.	3.20.3.0.2	32043281
32007605	OIG-1337	Create page displays the boilerplate text for "AS2805_A Agent Configuration" and " AS2805_B Agent Configurations" pages.	3.20.3.0.2	32043288
32006654	OIG-1362	HICAPS Claim authorization transactions having invalid response code(4 bytes instead of 2 bytes)	3.20.3.0.0	32006687	3-24262064101
32019204	OIG-1374	Access Restrictions not working in Credentials page	3.20.3.0.1	32056827
32070282	OIG-1394	Purge Exchanges does not purge the exchange steps that refer to the exchanges to be purged	3.20.3.0.2	32070291	3-24344763491
32073639	OIG-1397	Dynamic Logic exception: Restricted method invocation	3.20.3.0.1	32073644
32150472	OIG-1469	OIG Agent does not relay Claim Quote messages to the OIG Gateway	3.20.3.0.2	32150480	3-24420365681
32173023	OIG-1484	Unable to redirect to View mode after performing edit operation	3.20.3.0.2	32173029
32179560	OIG-1494	Multiple issues in Config Migration when trying to import DataSets through API	3.20.3.0.4	32241331	3-24514949761
32200189	OIG-1515	Member identifier missing on AS2805_A Claim responses when transaction/quote fails	3.20.3.0.2	32203399	3-24598189581
32233293	OIG-1558	Member identifier missing on AS2805_B Claim responses when transaction fails	3.20.3.0.3	32233319
32462461	OIG-1570	An error is coming when user tries to save the LOV value without selecting from the search results	3.20.3.0.4	32251682
32363922	OIG-1621	Extracts do not work with subflows	3.20.3.0.4	32363911	3-24886233961
32417952	OIG-1652	Replace dots ( . ) in headers with dashes ( - ) to follow networking conventions	3.20.3.0.4	32417954	3-25003397991
32421199	OIG-1654	Member Identifier missing on as2805 claim responses when transaction/quote fails.	3.20.3.0.4	32421525
32421493	OIG-1656	Member Identifier and line items missing on as2805 cancellation responses	3.20.3.0.4	32421511
32468679	OIG-1694	Task is stuck in 'PROCESSING' status if the node leaves the cluster	3.20.3.0.5	32468706
31550482	OIG-905	Cosmetic issues in view sub exchanges page.	3.20.3.0.2	32043270
31553442	OIG-959	"View Sub Exchanges" link should be Shown only for "Subflow Step Creator" integration sub step type	3.20.3.0.2	32029776

Known Issues

BugDB	SR	Internal	Summary
31523984		OIG-1284	Search Exchanges: pagination is not working properly
Description:	Search Exchanges: pagination is not working properly. When filtered the search results based on certain conditions. When changed the search results count from the default(10 rows), it is displaying as the text area. After applying the filter conditions, pagination is not displayed.
32477952		OIG-1702	Base view generator does not support dynamic data in JSON format
Description:	OIG_AGENT_CONFIGURATIONS, OIG_DESTINATIONS and OIG_EXCHANGES store dynamic data in JSON format. The base view generation does not support that. So dynamic data for those tables is not exposed as separate fields in base views.
32478350		OIG-1704	Exchange page does not display correct in firefox, functions in chrome
Description:	If you search on all the exchanges invoked in the environment in Firefox, the number of exchanges is displayed (e.g. 7) and the results list expands to match up with that number of exchanges, but stays empty. . Chrome displays the exchanges without issue.
32519567	3-25136475409	OIG-1729	File Upload with multiple files through JET fails
Description:	When invoking an OIG exchange through the JET UI and selecting multiple csv files, the exchange fails. It seems the data file creation is not handling multiple input files correctly. As a result, the dynamic logic, expecting several files, is not able to read the files and fails. This feature is needed to do enrollment product upload where for each type of premium a csv file is created. All files need to be uploaded to OIG for a single exchange.
32542466		OIG-1764	Tab with Table component having auto fetch set to true is not displaying all the search results.
Description:	When a page have tab resource configured with table component and auto fetch of the results is set to true, it is not displaying all the rows of search results until user explicitly click on search icon.
32564689		OIG-1777	View sub exchanges page keep loading when user navigate to it from sub exchange creator step.
Description:	When user try to navigate to sub exchanges page using subexchange creator step, page keep on loading the busy state icon.
32560431		OIG-1785	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.
32567171		OIG-1795	Configure ohi.resource.client.timer Resource Tag construction
Description:	For gathering metrics, it must be possible to control the resource tag for an "ohi.resource.client.timer" to point to the name of the resource (and not be more specific than that).
32574663		OIG-1797	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
-		OIG-350	Filter Component: operators 'in' and 'nin' needs to be implemented for string, integer, date, date time, reference field types
Description:	Operators 'in' and 'nin' needs to be implemented for fields of type string, integer, date, date time, reference types. The values for these fields should be displayed in multivalue rows.
31550459	3-23340260361	OIG-697	Application get hangup when "\\" is included in File Name Pattern field
Description:	In Agent Configuration page, if we add â€œ\\â€ in file name pattern field while creating/editing item, getting 400 error in the API response

BugDB

Internal

Summary

31523984

OIG-1284

Search Exchanges: pagination is not working properly

Description:

Search Exchanges: pagination is not working properly.

When filtered the search results based on certain conditions.
When changed the search results count from the default(10 rows), it is displaying as the text area.
After applying the filter conditions, pagination is not displayed.

32477952

OIG-1702

Base view generator does not support dynamic data in JSON format

Description:

OIG_AGENT_CONFIGURATIONS, OIG_DESTINATIONS and OIG_EXCHANGES store dynamic data in JSON format. The base view generation does not support that. So dynamic data for those tables is not exposed as separate fields in base views.

32478350

OIG-1704

Exchange page does not display correct in firefox, functions in chrome

Description:

If you search on all the exchanges invoked in the environment in Firefox, the number of exchanges is displayed (e.g. 7) and the results list expands to match up with that number of exchanges, but stays empty. . Chrome displays the exchanges without issue.

32519567

3-25136475409

OIG-1729

File Upload with multiple files through JET fails

Description:

When invoking an OIG exchange through the JET UI and selecting multiple csv files, the exchange fails. It seems the data file creation is not handling multiple input files correctly. As a result, the dynamic logic, expecting several files, is not able to read the files and fails. This feature is needed to do enrollment product upload where for each type of premium a csv file is created. All files need to be uploaded to OIG for a single exchange.

32542466

OIG-1764

Tab with Table component having auto fetch set to true is not displaying all the search results.

Description:

When a page have tab resource configured with table component and auto fetch of the results is set to true, it is not displaying all the rows of search results until user explicitly click on search icon.

32564689

OIG-1777

View sub exchanges page keep loading when user navigate to it from sub exchange creator step.

Description:

When user try to navigate to sub exchanges page using subexchange creator step, page keep on loading the busy state icon.

32560431

OIG-1785

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.

32567171

OIG-1795

Configure ohi.resource.client.timer Resource Tag construction

Description:

For gathering metrics, it must be possible to control the resource tag for an "ohi.resource.client.timer" to point to the name of the resource (and not be more specific than that).

32574663

OIG-1797

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

OIG-350

Filter Component: operators 'in' and 'nin' needs to be implemented for string, integer, date, date time, reference field types

Description:

Operators 'in' and 'nin' needs to be implemented for fields of type string, integer, date, date time, reference types. The values for these fields should be displayed in multivalue rows.

31550459

3-23340260361

OIG-697

Application get hangup when "\\" is included in File Name Pattern field

Description:

In Agent Configuration page, if we add â€œ\\â€ in file name pattern field while creating/editing item, getting 400 error in the API response