PM83548: APPLICATION IS REMOVING PRECEDING 0'S FROM USERNAME UPON DEPENDENT FIELD HIDE ACTION.

APAR status

• Closed as program error.

Error description

• Application is removing preceding 0's from username upon
  dependent field hide acion.
  
  
  The following generic steps to reproduce can be used to
  replicate the issue:
  
  
  1.  Open and use a supported browser. For debbuging, IE8/9 with
  Developer tools, or Firefox 19 with Firebug.
  2.  Login as administrator id (ie: OpenPagesAdministrator).
  3.  Create any user that starts with a zero (0).  For example:
  0058585.  No other text or characters except numbers.
  4.  Create a new field group <abc> with the following:
    Enum Field: ?Selector?     {Hidden|Shown}, Req.=false, Def.
                               value=null.
    Simple Str: ?UserField1?   req.=false, Def. value=null.
    Simple Str: ?UserField2?   req.=false, Def. value=null.
  5.  Under Object Types, include the field group <abc> to an
  Object Type.
  6.  Within the selected object type, create a field dependency:
    Dependent Field  =        ?UserField1?.
    Controlling Field=        ?Selector?.
    Controlling Value=        ?Shown?.
    Behavior Type    =        ?Visible?.
  7.  Use the profile which you are assigned to.
  8.  At profile level, include the 3 fields ?Selector?,
  ?UserField1? and ?UserField2? to your selected Object Type.
  9.   Edit ?UserField1? and ?UserField2? to make them
  user-selector type fields.
  10.  Within the profile for the Object Type selected; Add the 3
  fields to the Detail page of the Object View table.
  11.  Open any item within the Object Type and edit.
  12.  Change ?Selector? field to ?shown?.
  13.  In Userfield1, enter the username you created that starts
  with the zero (for example 0058585).
  14.  Save the Object.
  15.  Reopen the Object and Edit.
  16.  Open Firefox Firebug or IE Dev Tools, it shows the correct
  username in both the field, and the backend code.
  17.  Change ?Selector? to ?hidden?.
  18.  Now again view the Firebug output. The value has changed
  from ?correct userid with a leading 0? (for example 0058585) to
  just ?the numbers without the leading 0? (for example 58585)
  19.  Save the Object. The incorrect value has now been saved to
  the database.
  20.  Confirmed within the Change History that the wrong user is
  saved.
  
  
  The expectation is for the application to not trim the leading
  zeros prior to saving the data.
  

Local fix

• NA
  

Problem summary

• ***************************************************************
  * USERS AFFECTED: Users in OpenPages 6.0
  ***************************************************************
  * PROBLEM DESCRIPTION: Application is removing preceding 0's
  * from username upon dependent field hide action.
  ***************************************************************
  * RECOMMENDATION: Customers should download OpenPages 6.1
  * from Passport Advantage. See the following document
  * for details on obtaining 6.1.
  * http://www.ibm.com/support/docview.wss?uid=swg24031983
  ***************************************************************
  

Problem conclusion

• When a User Selector field contained a user name with
  preceding 0's (i.e. 001), they would be truncated if the
  field became hidden.
  
  This behavior has been corrected in the OpenPages 6.1
  

Temporary fix

• Do not set a hidden dependency rule on a user selector field
  until upgrading to at least OpenPages 6.1
  

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

• Fixed component name

  OPENPAGES GRC

• Fixed component ID

  5725D5100

Applicable component levels

• R610 PSY

     UP

• R620 PSY

     UP