My Oracle Support Banner

Multifield Field States Reset When MultifieldCount is Written to Via an Action/Event (Doc ID 2979343.1)

Last updated on OCTOBER 20, 2023

Applies to:

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

Symptoms

On : 11.2.9.0 version, Activity

ACTUAL BEHAVIOR
---------------
When the number of instances of a MultiField is updated via Action/Events, the Field states of all Fields in the existing instances of the MultiField are reset to their defaults however the Field values are not.
This opens up opportunities for users to interact with Fields which are expected to be locked due to instance conditions.
This same problematic behavior does not occur when manually changing the number of instances via the dropdown box at the top of the MultiField.
This issue prevents the users from making use of the new MultiField Utility which allows dynamic programmatic control of the number of instances available in a MultifFeld.


EXPECTED BEHAVIOR
-----------------------
When the number of instances of a MultiField is updated by an Action/Event, the states of the instances which already existed should be preserved.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Use the Test Transaction and MultiField Rule at any level (this test was performed at the Client level).
2. Add an instance of the Activity and scroll down to the second MultiField section named Demo Nonzero MultiFields, and in the first instance check the Event Trigger 1 and 2 fields.
This should result in the Event Result 1 Field being hidden, and Event Result 2 Field being disabled. They are both visible and enabled by default.
3. Scroll back up to the top of the Transaction and check the Set MultiField 2 Count checkbox. This will assign a new value to the MultiFieldCount element via Action/Events.
4. Scroll back down to the MultiField which was interacted with in step 2.
5. Observe that while the Field values were persisted for index 1, (both checkboxes are still checked), the Field states were not (the hidden Field is back to its default visible state, and the disabled Field is back to its default enabled state).

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.