Issue With Multi-Fields That Are Configured To Start At 0

(Doc ID 2336504.1)

Last updated on DECEMBER 06, 2017

Applies to:

Oracle Insurance Policy Administration J2EE - Version 11.0.2.4 and later
Information in this document applies to any platform.

Symptoms

On : 11.0.2.4 version, General

ACTUAL BEHAVIOR
---------------
If a Multi Field is configured to start at 0, changing that value, inputting values into the fields and hitting save does not commit the changes to the AsActivityMultiValueField table. This behavior is observed only on the initial save of an activity. If an already existing activity is opened, values inputted and saved again, fields are committed to database. If Multi-Fields are configured to start at 1, issue cannot be reproduced.

EXPECTED BEHAVIOR
-----------------------
If multifields are configured to start at 0 and a user changes that number to 1+, inputs data into the fields and clicks save that the data would be persisted to the DB.
 

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Configure an activity to have multifields that start at 0
2) Add that activity in OIPA
3) Change the number of multifields to be 1+
4) Add values into the fields
5) Save the activity but do not process
6) If you re-open the fields tab it will be set at 0 and none of the data you entered will be present
6a) None of the fields will be present in the AsActivityMultiValueField table

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot default multifields to 0 instances. This will cause a problem when we need to work with beneficiaries because we will need to default it to 0.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms