Release Notes for Oracle Health Insurance Value-Based Payments Release 3.22.2.0.0

This document contains the release notes for Oracle Health Insurance Value-Based Payments Release 3.22.2.0.0.

Version compatibility: Oracle Health Insurance Value-Based Payments Release 3.22.2.x is only compatible with other Oracle Health Insurance applications release version 3.22.2.x unless explicitly stated otherwise.
In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases.

Enhancements

ID Summary Patch

NXT-20170

Purging capabilities are added for financial 'technical' tables.

This enhancement introduces purging capabilities for financial 'technical' tables.

Documentation Links:
Administration Guide - Purging Data from Technical Tables

NXT-22395

Make GridTaskProcessor thread pool size configurable

This enhancement makes configuring the activity processing thread pool size possible (through a system property).

NXT-23106

Export UI data to CSV

This enhancement introduces ability to download UI data to a CSV file.

Documentation Links:
Developer Guide - JET UI Table Component

NXT-23606

Auto generation of provider code in Provider pages

This enhancement removes the need to enter the provider code at the time of creating a new provider.

NXT-23841

Auto include Extensibility in pages

This enhancement introduces capability to access all dynamic fields and records on a page without modifying the page configuration (a.k.a floorplans).

Documentation Links:
Developer Guide - Jet UI Floor Plans (view and edit recursive)
Developer Guide - Jet UI Floor Plans (view and edit list)
Developer Guide - Jet UI Floor Plans (table view)

NXT-24937

Reference Sheet Column Name Length Increased

This enhancement extends the length of the reference sheet usage name, display name, and column display name length from 30 to 50 characters.

NXT-25000

The handling of resource representation parameters in http requests has changed

Before this enhancement, resource representation influencing parameters are passed in the "Accept" header of a HTTP request. When the number of values passed in the header increases and the header size crosses 8K,the server rejects HTTP request.

This enhancement provides an alternative way to pass more than 8K data in resource representation parameters. Instead of passing these parameters in the HTTP request header, now these parameters get passed in the HTTP request body. This capability is available only for "POST /generic/{entity_name}/search" API.

This release supports passing parameters in header as well as body. In future releases the parameters in header support will be removed, hence passing parameters will be only supported via HTTP request body.

The parameter names are the same in body as well as in the header. In the body, these parameters are mentioned under "resourceRepresentation". When the body includes "resourceRepresentation", it completely ignores the header parameters.

Documentation Links:
Configuration Guide - File Upload
Configuration Guide - Synchronous Integration
Configuration Guide - Invoke Activity or Process Step
Developer Guide - Transformation Dynamic Logic
Developer Guide - Sample Process and Apply Registrations to Periods
Developer Guide - Run Example Calculation for a Policy
Developer Guide - Quote Integration Point
Developer Guide - Influence Resource Representation

NXT-25061

Specialty Dynamic Records

This enhancement introduces the ability to configure dynamic records on the specialties entity.

Documentation Links:
Configuration Guide - Configuration Migration Tools - Creating
Configuration Guide - Providers Specialties

NXT-25553

Auto optimization of ohi reference sheet lines and oig exchange text indexes.

This enhancement enables auto optimization of ohi reference sheet lines and oig exchange text indexes, so that a separate scheduler job is not required for optimizing text index, A daily optimization of fragmented tokens and weekly full optimization would be done automatically to sync the text index entries.

NXT-25662

Remove PHI in GET requests (advance notice)

Please see "Deprecated items (to be removed in future release)" section.

OIG-2347

Dynamic Logic Statistics IP

This new IP exposes statistics about dynamic logic execution: execution count and elapsed times.

Documentation Links:
Developer Guide - Dynamic Logic Statistics Integration Point
Developer Guide - Dynamic Logic Statistics

POL-11035

Enhancement in Test Dynamic Logic Integration Point: return log messages

When testing a dynamic logic, the test dynamic logic unit code and the logs messages are being returned in the response of the Test Dynamic Logic IP

Documentation Links:
Developer Guide - Test Dynamic Logic Integration Point

POL-11121

The use of leading or trailing spaces in a user name is prevented

This enhancement prevents the use of leading or trailing spaces in the user’s login name. The provisioning integration point raises a fatal message when leading or trailing spaces are used in the login name. The enhancement supports a conversion script for existing login names with trailing spaces.

Documentation Links:
Developer Guide - Provisioning Integration Point

POL-11122

Optimize the performance of reference sheet lines queries

The performance of querying reference sheet lines from dynamic logic (using SearchBuilder) is optimized by caching the query results (controlled by a system property).

POL-11138

Extend Extract Integration Point

This enhancement extends the extract Integration Point to include dynamic record identifiers.

Documentation Links:
Developer Guide - Extract Integration Point

POL-6850

Ability to update default country in the user interface

This enhancement introduces ability to update default country setting through user interface.

POL-9845

Reference Sheet Line Key Length Increased

This enhancement increases the length of the key attribute on a reference sheet line to 200 characters.

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

  1. Perform any pre-upgrade steps.

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

  3. Perform any pre-undeploy steps.

  4. Undeploy the existing version of the application.

  5. Back up the database.

  6. Perform any post-undeploy steps.

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

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

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

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

  11. Run the Upgrade script:

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

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

  12. Make the required changes to the ohi properties file

  13. Perform any post-upgrade steps

  14. Start WebLogic application server

  15. Deploy the Application

  16. Perform any post-deploy steps

Additional Upgrade Steps for Installation

The following phases are defined:

  1. pre-upgrade: Application is still running

  2. pre-undeploy: Application is stopped, but not undeployed.

  3. post-undeploy: Application is undeployed. Database is backed up

  4. post-upgrade: Released upgrade script has run.

  5. post-deploy: New application is deployed and is up and running.

Stage: post-undeploy

1) Action: Run the following SQL update statement, to replace leading and trailing spaces in login_name with 'X' for all users with trailing spaces.

update ohi_users            -- replace leading spaces
set    login_name            = lpad(ltrim(login_name), length(login_name), 'X')
,      last_updated_date     = current_timestamp
,      last_updated_by       = 10
,      object_version_number = object_version_number + 1
where  login_name != ltrim(login_name);

update ohi_users            -- replace trailing spaces
set    login_name            = rpad(rtrim(login_name), length(login_name), 'X')
,      last_updated_date     = current_timestamp
,      last_updated_by       = 10
,      object_version_number = object_version_number + 1
where  login_name != rtrim(login_name);
commit;

If you run into the "ORA-00001: unique constraint violated" error, this means that there is already a user with the same login_name after replacing spaces with X. In this case, identify the offending login_names with the following query:

select  u1.login_name
from    ohi_users u1, ohi_users u2
where   u1.login_name != rpad(rtrim(u1.login_name), length(u1.login_name), 'X') -- u1: users whose login_name are renamed
and     u2.login_name = rpad(rtrim(u1.login_name), length(u1.login_name), 'X'); -- u2: users whose login name equals the renamed name

And similarly where rpad(rtrim(…​ has been replaced with lpad(ltrim(…​ for errors in login_names with leading spaces.

Manually replace these login_names with extra X’s to avoid the unique key violation, e.g. if user "login_with_space " was found with the previous query, copy it (including the space) and update it with the following statement:

update ohi_users
set    login_name            = 'login_with_spaceXX'      -- add an extra X
,      last_updated_date     = current_timestamp
,      last_updated_by       = 10
,      object_version_number = object_version_number + 1
where  login_name = 'login_with_space '                  -- the offending login_name
commit;

After this, run the first update statement again.

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

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

GRANT EXECUTE ON SYS.DBMS_CRYPTO TO system WITH GRANT OPTION;

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

GRANT EXECUTE ON SYS.DBMS_CRYPTO TO OHI_CAPITATION_OWNER;

Stage: post-upgrade

1) Enabling auto optimize feature for OHI_REF_SHEET_LINE_IDX1 Execute the below command as ohi_capitation_owner

Begin
ohi_reference_sheet_lines_index_maintenance_pkg.create_index(1);
end;

Configuration Properties

Ref Action Description

NXT-22395

Added

ohi.activityprocessing.threadpool.size

Added an optional property to configure the size of the thread pool used for processing the activities. The default value is 8

POL-11122

Added

ohi.referencesheetlines.query.results.cache.enabled

This is an optional property that controls if the reference sheet lines query results should be cached or not. The default value is true.

Web Services

Ref Action Description

OIG-2347

Added

Dynamic Logic Statistics IP

New IP is added

POL-11035

Modified

Test Dynamic Logic IP

When testing a dynamic logic, the test dynamic logic unit code and the logs messages are being returned in the response of the Test Dynamic Logic IP

POL-11138

Modified

Extract Integration Point

The extract Integration Point now exposes the identifiers of the dynamic records.

POL-9845

Modified

Reference Sheet Line Integration Point

Increased length of the 'key' attribute

POL-9845

Modified

Reference Sheet Line API

Increased length of the 'key' attribute

Data Conversion

Ref Action Description

CPN-2164

Modified

Floorplans

Incorrect floorplan ids were fixed.

Dynamic Logic

Ref Action Description

POL-11122

Modified

All

The dynamic logic will be re-compiled when the application starts up the first time after upgrading to this release. So, application startup could take more time than usual. This is an one time operation, so the dynamic logic are not re-compiled in the subsequent startup.

UI Changes

Ref Action Description

CPN-2209

Modified

Capitation Contract Page

While creating a new Capitation Contract record, the console throws id-generator error and resolved by passing prefix and block names in lowercase to id-generator

CPN-2231

Modified

messages create page

In messages create page 'active' checkbox is not getting selected by default and resolved by adding default value as true for 'active' checkbox

NXT-23106

Added

Download button in table pages

User can now download loaded table rows into a CSV on clicking download button in search table, table at tab level and list pages.

NXT-23106

Modified

Pages with Deep Link configured

Links now open in a drawer instead of popup. It is now possible to configure a deeplink in create mode. On selecting a value in the dropdown of a deeplink enabled field, a view link is shown which opens a drawer with information on selected dropdown option in view mode.

NXT-23841

Modified

All JET pages which support extensibility

Dynamic Fields and records are shown on all the table and view edit pages which support extensibility.

NXT-24937

Modified

Reference Sheets, Record Definitions

Reference Sheet’s usage name and display name’s column length updated to 50. In the Record Definitions page, the record field’s column length is extended to 50.

Deprecated items (to be removed in future release)

Ref Action Description

NXT-25000

Deprecated

Remove the support of resource representation parameters in accept header

Resource representation influencing parameters such as response, expand, fields, aliases and defaultoverride won’t be supported in the header of HTTP request in one of the next major releases. Hence, these parameters should be passed as request body.

NXT-25662

Deprecated

Remove the support to GET operations on Query API calls

The support to GET operations on Query API calls is deprecated and will be removed in one of the major releases. The Query API calls shall use POST operation and send the parameters (e.g. q, order by) as part of the request’s body. Below there are some examples of searches comparing the use of GET and POST.

This deprecation affects the Collection Resource API, meaning that a GET call on http://[hostName]:[portNumber]/[api-context-root]/generic/{resource name} is also deprecated and shall be replaced with a POST call.
Table 1. Retrieving a collection resource
With GET With POST

HTTP Method

GET

POST

URI

http://[hostName]:[portNumber]/[api-context-root]/generic/persons

http://[hostName]:[portNumber]/[api-context-root]/generic/persons/search

JSON Body

N/A

 
{
    "resource": {
    }
}
Table 2. Searching for a person using two filters
With GET With POST

HTTP Method

GET

POST

URI

http://[hostName]:[portNumber]/[api-context-root]/generic/persons?q=dateOfBirth.eq('1900-01-01').and.name.eq('Doe')

http://[hostName]:[portNumber]/[api-context-root]/generic/persons/search

JSON Body

N/A

 
{
    "resource": {
        "q": "dateOfBirth.eq('1900-01-01').and.name.eq('Doe')"
    }
}
Table 3. Searching for a person using two filters, specifying an order by criteria, limit and offset for pagination purposes
With GET With POST

HTTP Method

GET

POST

URI

http://[hostName]:[portNumber]/[api-context-root]/generic/persons?q=dateOfBirth.eq('1900-01-01').and.name.eq('Doe')&orderBy=code:desc&limit=10&offset=0

http://[hostName]:[portNumber]/[api-context-root]/generic/persons/search

JSON Body

N/A

 
{
    "resource": {
        "q": "dateOfBirth.eq('1900-01-01').and.name.eq('Doe')",
        "orderBy": "code:desc",
        "limit": 10,
        "offset": 0
    }
}
Table 4. Searching via Dynamic Logic
With GET With POST 
String response = initCallOut(WebTarget.class)
        .path("generic/messages")
        .queryParam("q","code.eq('OHI-DYLO-001')")
        .request("application/json")
        .buildGet()
        .invoke()
        .readEntity(String.class)
 
String response = initCallOut(WebTarget.class)
        .path("generic/messages/search")
        .request()
        .buildPost(Entity.json(jsonPayload))
        .invoke()
        .readEntity(String.class)

Where jsonPayload is a String representing:

{
    "resource": {
        "q": "code.eq('OHI-DYLO-001')"
    }
}

Please note that the Page Links associated to the query response will also have a structure change in a future release: the "searchResource" element will be renamed to "body". See an example below:

Table 5. Change in the Response
Currently In a future release 
"searchResource": {
    "resource": {
        "offset": "50",
        "name": "activities"
    }
}
 
"body": {
    "resource": {
        "offset": "50",
        "name": "activities"
    }
}

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal BP Summary

33245643

CPN-1724

Default values for system and dynvalidation fields are not getting set while creating a dynamic record definition for reference sheets.

Description:

An error is reported while trying to create a dynamic record definition for a reference sheet: { "o:errorDetails": [ { "o:errorCode": "GEN-PROC-ERR", "title": "GEN-PROC-ERR: An error occurred in processing the request; for more information about the error search the logging for occurrences of "java.lang.NullPointerException"", "o:errorPath": "$" } ] }

Resolution:

The NPE exception was thrown when the dynValidation key wasn’t passed in the payload. The dynValidation key must be passed with value as true in order to generate dynamic record.

NPE was handled by treating dynValidation as false when dynValidation key wasn’t passed in the payload, this will not break the code and proceed with BAU flow

33724563

CPN-1933

ACCESS: Links are not accessible through keyboard

Description:

Links are not accessible through keyboard.

Resolution:

Able to access links through keyboard in JET screens now. Navigate to link using tab and press enter.

34174908

CPN-2073

In the Quick Search and Advanced Search components of tab table, the searched text gets cleared off after the display of the results

Description:

In the Quick Search and Advanced Search components of tab table, the searched text gets cleared off after the display of the results.

Resolution:

Search criteria is not cleared now in quick search and advance search of tabs after the results are displayed

34169484

CPN-2071

Testdynamiclogic IP - Incorrect response code 418 in metadata instead of 400.

Description:

Metadata of testdynamiclogic IP doesn’t have correct response code for unsuccessful execution of test unit.

Resolution:

The response code has been updated to 400 bad request.

34594832

CPN-2219

LOV values are not displaying comma separated in Edit mode

Description:

The Title property configured with sequence setting 2 in LOV is not showing up in Edit mode of the page

Resolution:

LOV values are displayed as comma separated in Edit mode when there are more than 1 title properties configured in the LOV floorplan

34594864

CPN-2220

Unable to search for any flex code group record after moving back to search page from view edit page.

Description:

When the user searches for flex code groups and opens a flex code group and navigates back to search page, the user is unable to perform search.

Resolution:

User can perform search in all the scenarios.

34608916

CPN-2226

Reference Property defaults do not work with display type never setting.

Description:

Setting default on a mandatory field like Languages in Persons page with display 'never' setting doesn’t work and on saving the record an error is thrown that Language is mandatory for Person entity

Resolution:

Reference Property defaults work with display type never setting on fixed fields related to an entity.

34593026

CPN-2211

Remove link is present far away from the field for multi value fields

Description:

Create Usages of MultiValue type for any page and them to floorplan of the respective page. Open the page and fill data into the multivalue fields present on the page. The 'Remove' link is far from multivalue field.

Resolution:

Remove link is present next to the multi value fields and not far from the field

34593379

CPN-2213

Cannot save the page when a single value type of record definition is configured

Description:

When a single value record definition is configured which further has some mandatory picklist or flex code fields, while creating and saving a policy, getting error for mandatory field even if value is selected

Resolution:

A single value record definition can be configured with a mandatory picklist or flex code field and it works fine

34687300

3-30823746721

CPN-2250

Extract activity with high volume may cause OutOfMemoryError

Description:

Extract activity with high volume (and if multiple extract activities are processed concurrently) may cause OutOfMemoryError. All the child activities are submitted at once to the coherence grid for processing, causing contention and memory issues in coherence.

Resolution:

Processing of the child activities (PROCESS_EXTRACT_ITEMS) originated from the parent activity (SELECT_EXTRACT_ITEMS) is now throttled. Also, the memory footprint of running the activity PROCESS_EXTRACT_ITEMS is reduced.

34608104

CPN-2222

Default value on a field that has a flexcode is not working

Description:

The default value on a field that has a flexcode is not working

Resolution:

The default value on a field that has a flexcode is working, when the default value is set on keyValue or the descriptor only. Format: { "name": "keyValue","value": "2" }

34574624

CPN-2200

Dynamic Fields added to the floorplan through usages page has wrong refType type added.

Description:

When a dynamic field is added from the Usages page to the floorplan using the 'Add To Floorplan' action, the wrong reference types were added for flex codes of type 'providers' .

Resolution:

When a dynamic field is added from the Usages page to the floorplan using the 'Add To Floorplan' action, proper values are shown for flex codes of type 'providers'

34594796

CPN-2217

Unable to create numeric LOVs using custom floorplans

Description:

Users cannot set a picklist for Numeric fields on a dynamic record. Configuration of custom LOVs on numeric fields is not working

Resolution:

It is possible to create a picklist for numeric fields on a dynamic record in JET, provided users configure key field of flex code same as the numeric values. Also support on custom LOVs on 'Date' field is deprecated

0.0

CPN-2248

Extract activity stays in 'in process' status sometimes waiting on AtomicSafeInitializer

Description:

While initializing ExtractGlobalPlan, sometime extract activity stays in 'In Process' status by waiting on AtomicSafeInitializer and never completes. As a result, if any new extract activities are submitted, it will be also in 'In process' status and if such submission continues, finally the activity processing thread pool is exhausted.

Resolution:

Modified the way of initializing ExtractGlobalPlan. Now ExtractGlobalPlan is initialized immediately after it is created on each node.

34775320

3-30712959201

CPN-2288

SELECT_TRANSACTIONS_IN_SET activity failed with OutOfMemoryError

Description:

SELECT_TRANSACTIONS_IN_SET activity failed with OutOfMemoryError

Resolution:

Processing of the child activities is now throttled

34633778

CPN-2233

Access to Persons via bankaccountnumbers API not always audited

Description:

Doing a GET request on bank account numbers also reveals the relations that these bank account numbers are associated with. If these relations are of type "person", rather than "organization", this access is audited. The problem is that this only happens if the first bank account number has a relation of type person.

Resolution:

Access to persons via the bank account numbers API is now always audited.

34566679

CPN-2199

Code and description of brands are blank in ui after brands are extracted using extract ip

Description:

After extracting brands using extracts IP, when user access brands (could be through UI or API/Integration Point), brand code and description don’t be visible but table holds these data.

Resolution:

This was JPA cache issue. When brands were extracted using IP, all brands were getting cached at L2 cache level but without translation records. Translation records hold brand code and description information as per locale.

Fixed it by avoiding caching of brands when extract IP is invoked.

34851829

3-31111589651

CPN-2331

Not able to search with criteria in case the list of value have more than 50 results

Description:

Only the first 50 results are showing for an advanced search criterion and, because of that, a user is not able to find the required flex code definition to search on providers' pages.

Resolution:

More than 50 results for Flex Code Definitions are shown in LOV in procedures page, diagnosis page

34478338

CPN-2164

Floor Plans Missing After 3.22.1.0.1 Upgrade

Description:

Some customer Floorplans were missing after 3.22.1.0.0 Upgrade. They got overridden by OHI floorplans.

Resolution:

Incorrect floorplan ids were fixed.

34589101

CPN-2209

Create Capitation Contract page opens with Id-generator console errors

Description:

While creating a new Capitation Contract record, the console throws id-generator error

Resolution:

Resolved by passing prefix and block name in lowercase to id-generator

34622245

CPN-2231

While creating a message "active" should be selected by default

Description:

In messages create page 'active' checkbox is not getting selected by default

Resolution:

Updated messages floorplan by giving default value as true

Issues that were backported in previous Release / Patch

No backports.

Known Issues

BugDB SR Internal Summary

32477683

CPN-1431

No base view generated for reference sheet lines

Description:

Reference sheet(line)s use a different storage structure (JSON) for the dynamic fields. The base view generator does not support that yet. So the reference sheet line columns can’t be queried using base views.

33039777

CPN-1652

Action buttons are not accessible for results when in view mode in contracts page

Description:

Hamburger icon is not accessible for results when in view mode in contracts page. This is happening for results and table components both.

33430852

CPN-1811

Usages - Add to Floorplan - When same usage is associated in all the sets of a floorplan, the values are not rendered properly on the entity’s page.

Description:

When an usage is added to Floorplan to display the same dynamic field in multiple sets of the entity page, the respective fields are not rendering the values as expected. So there needs to be a reconfiguration check in place to handle this situation.

34401173

3-29621579461

CPN-2146

CMT recovery process fails with null pointer exception

Description:

During restart, the data set processes for CMT are cleaned up. As a result, CMT recovery process fails with null pointer exception

34588281

CPN-2208

Usage: The search is not retained when navigating back to usage page after making changes to a selected usage record

Description:

Go to Usage page for any entity e.g.: Policies. Search for any specific usage record. Click on View icon to view or edit anything on that particular record. After making changes, click on Apply button, so that user is navigated back to Usage page. Click on Save button. The search box still shows the previously searched value but the table shows all the records

34593809

CPN-2214

Cross reference of fields across floorplan ($context.parent) does not work in filter

Description:

If a floorplan is configured with a condition on a refType property, that modifies the filter to use $context.parent as shown in following snippet, it throws an error. Ex: "filter":"${context.product.code}"

34593858

CPN-2215

Accessing parent’s properties through $context does not work for conditions floor plan component in create mode

Description:

It is not possible to access parent properties through $context in conditions component, configured on the child entity’s floor plan in create mode.

34594236

CPN-2216

Money fields are getting saved without decimal places when 4 decimal places are entered

Description:

When a value with 4 decimal places is entered in a money field ('9999.9999'), on save it automatically rounds off to the next whole number value without any decimal places('10000').

34733146

3-29584669481

CPN-2273

OptimisticLockingException when updating lastlogintimestamp of the user

Description:

Updating lastLoginTimestamp is controlled by a system property ohi.ws.last.login.update.threshold i.e the lastLoginTimestamp is not updated if the user logs-in multiple times with in the same hour.But if there are concurrent requests next second after this hour, both the API/IP requests try to update the same user record, system throws 500 error in this case.

This causes problem in updating the LASTLOGINTIMESTAMP

34866790

CPN-2314

Display never not working for dynamic fields mentioned in floorplan when autoinclude is set to yes

Description:

Created a usages field and update the floorplan as display: Never along with auto include extensibility is checked in. The field is shown in the persons page UI and able to edit it.

34853768

CPN-2334

Dynamiclogicstatistics Reset URL missing in Dynamiclogicstatistics Response Body

Description:

/dynamiclogicstatistics/reset URL is not showing up in /dynamiclogicstatistics response body.

34863770

CPN-2338

'Execution starts' , Result , Execution Completed msgs display twice in logMessages in Test Unit IP Response

Description:

'Execution starts' , Result , Execution Completed msgs display twice in logMessages in Test Unit IP Response

The standard logging is confusing, it seems that the same error message is given twice. This is however not the case. One is for Test Unit dylo and the other for the actual Dylo. The dynamic logic code context is missing in the logging. These messages should be more clear.

34868055

CPN-2345

Additional Fields: Apply and cancel buttons are shown in view mode

Description:

Additional Fields: Apply and cancel buttons should not be shown in view mode

34868579

CPN-2347

Zip files cannot be imported on Mac and Linux

Description:

File cannot be imported using Mac and Linux. This is a common issue observed with file upload component

34871106

CPN-2349

Additional Fields: Cancel button is saving the data.

Description:

Create a new claim and click on additional fields. Save few additional fields. Now edit the additional fields and click on cancel. New changes are getting saved

34871887

CPN-2351

Add to Floorplan - Next button is not responding

Description:

Create a usage Field and click on add to floor plan. Select custom Floor plan and click on next. Select the set and select 'Create new tile'. Now Next button is not responding

34871898

CPN-2353

Reference Sheet lines page is not loading all the results

Description:

Reference Sheet Lines page is not loading more than 50 records even when there are more than 50 records present in the database.

34872151

CPN-2354

Boilerplate not loading for widgets

Description:

Users will always add boilerplate keys in custom widgets. System should support it.

34872229

CPN-2355

Unsaved pop-up message is showing when we click on add button on few pages

Description:

On clicking of add button unsaved pop up showing. Pop-up is also shown while scrolling to fetch more rows. The issue doesn’t occur if we add new rows without doing a blank search