AddRoles BR Creates Field With FieldTypeCode = '00' If NULL Is Used
(Doc ID 2810193.1)
Last updated on SEPTEMBER 29, 2021
Applies to:
Oracle Insurance Policy Administration J2EE - Version 11.1.0.13 and laterInformation in this document applies to any platform.
Symptoms
On : 11.1.0.13 version, General
ACTUAL BEHAVIOR
---------------
A Policy transaction using Attached Rule AddRoles will create a bad entry on AsRoleField if a Null Date is passed to a Role field of type Date.
When using Attached Rule AddRoles with a Policy transaction, if the math variable referenced in the element is DATATYPE="DATE" and the dateValue is Null,
when the Activity processes the created row on AsActivityField will have a FieldTypeCode of '00'.
EXPECTED BEHAVIOR
-----------------------
A Null Date should still save as FieldTypeCode 01 if the expected field type is a Date field.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a Policy transaction with Attached Rule AddRoles.
2. Within this transaction create a MathVariable of DataType DATE and a Null value.
3. Process the transaction and see that the created entry on AsRoleField has been created with a fieldTypeCode of 00.
The workaround is that the configuration must always pass a dateValue to ensure FieldTypeCode sets to 01.
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 |
Cause |
Solution |
References |