In the SML (Classification List) Float Values Are Not Displayed If Precision Is Greater Than the Pool Definition (Doc ID 2091624.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Agile Engineering Data Management - Version 6.1.3.0 and later
Information in this document applies to any platform.

Symptoms

On Oracle Agile e6.1.3.0 with the Java Client

Find that opening the classification list returns error
  ... Float value "8.30e-002" too large for form field !'

EXPECTED BEHAVIOR
--------------------------------
Having field value displayed, even if it is too long ( may be cut, but should not be empty )

The issue can be reproduced with following steps:
-------------------------------------------------------
On Windows App server
1. Create new attribute flo1 Type F6.2
2. Create new class TEST-001 for EDB-ARTICLE
3. Assign new attribute flo1 to new class TEST-001
4. For class TEST-001 open classification form
5. Create new classification record - choose any existing item and enter value 0.083

Receive error
  Float value "8.30e-002" too large for form field !

6. Receive same error when trying to open classification list for existing records with invalid values
  ... Float value "8.30e-002" too large for form field !'


Repeat same steps 1-4 on Linux App server
5. Create new classification record - choose any existing item and enter value 0.083

Receive no error
  Find float value 0.083 successfully stored and displayed as "8.30e-02"


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