IV91238: UNABLE TO USE NUMERIC KEYBOARD WHEN USING A COMMA AS DECIMAL SEPARATOR

APAR status

• Closed as change to accomodate OEM Vendor's code.

Error description

• ERROR DESCRIPTION:Ø
  PROBLEM:
  When an input is configured for a decimal attribute by using a
  text element with the property enableNumericKeyboard=true.
  As explained in:
  https://www.ibm.com/support/knowledgecenter/SSPJLC_7.6.0/com.ibm
  .si.mpl.doc/upgrade/r_differences_app_xml.html
  An error similar to the following is always being returned
  regardless of the input:
  For the input 2,32 -> The value 2.32 is not a valid decimal
  Notice that the value is incorrectly being converted from 2,32
  to 2.32 and consequently the error is being returned.
  Issue is only reproducible with a European language like
  Portugese(Brazil), i.e. this only seems to occur when the
  device regional settings consider the comma (,) as the
  decimal separator. Also, if a numericKeyboard is not used the
  field is being correctly validated.
  This issue was reproducible by client contact using an IOS
  device on the Maximo Anywhere 7.6.0.0 version.
  The issue was also reproduced using Eclipse MobileFirst Studio,
   iphone, Preview.
  PERFORMANCE ISSUE: no
  STEPS TO REPRODUCE:
  Issue is device OS independent
  1. Set tablet Language to: Portugues (Brazil)
  
  2. Open a Workorder record in Anywhere application, i.e. Work
  Execution app
  3. In the first row, the custom field Custom Value is
  displayed:
  
  
  Click into field to enter a numeric value in the Custom Value
  field.
  
  
  The numeric only keyboard is displayed, rather than the full
  standard   alphanumeric keyboard.
  
  Enter in a value, i.e. 40 and click away to remove focus on
  field... the field remains as 40 or is wiped away from field if
  you click into a field like Asset description.
  
  
  If you enter 40,00 then the error appears:
  
  O valor 40.00 nao e um decimal valido.
  
  Translated:  The value 40.00 is not a valid decimal
  
  This is the reported issue, it should be setting and using
  40,00.
  CURRENT ERRONEOUS RESULT:
  Unable to use numeric keypad when working with decimal input
  values in European language.
  ENVIRONMENT:
  IBM Maximo Anywhere 7.6.0.0 Build 20160422_182617-0500 DB Build
   V7600-07
  Tivoli's process automation engine 7.6.0.5 Build 20160611-0100
  DB Build V7605-45
  IBM TPAE Integration Framework
  7.6.0.5-MIF_7605_IFIX.20160714-2314 Build
  20160610-2330 DB Build V7605-50 HFDB Build HF7605-03
  TPAE OSLC Object Structure 7.6.0.0 Build 20160422_182552-0500
  DB Build  V7600-10
  IBM Maximo Linear Management 7.6.0.0 Build 20160611-0100 DB
  Build V7600-06
  IBM Maximo Asset Management Scheduler 7.6.3.0 Build
  20160611-0100 DB Build V7630-25
  IBM Maximo Spatial Asset Management 7.6.0.0-20160802-1628 Build
  20160318-0236 DB Build V7600-61 HFDB Build HF7600-10
  IBM Maximo Asset Management Work Centers 7.6.0.0 Build
  20160610-1318 DB Build V7600-38
  IBM Maximo Asset Management 7.6.0.5 Build 20160611-0100 DB
  Build V7604-01
  App Server: IBM WebSphere Application Server 8.5.5.8
  Server OS:  Windows 6.3
  Server DB:  Microsoft SQL Server 11.0 (11.00.5058)
  

Local fix

•  N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Any users in a locale that uses the comma for a decimal      *
  * separator, that have enabled numeric keyboards on certain    *
  * fields.                                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When typing the comma separated decimal value, the framework *
  * incorrectly gives an error message that the decimal value is *
  * in the wrong format.                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• This is actually due to the strange way that Android and iOS
  interpret number type input fields.  They seem to automatically
  convert from the input locale, into a decimal that looks like
  this "1.3".   We needed to fix our code to handle this case.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels