IBM Support

PM28911: RCP client does not recognize field value as present if field is present multiple times on form

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Environment:
    
     - Operating System:
    Solaris 9
     - Product name:
    ClearQuest
     - Product Version:
    7.1.1.1
    
    
    Description of problem:
    
    
    
    If a field is present multiple times on the form (whether on
    separate tabs or on the same tab) and the field is mandatory,
    the RCP client on Solaris does not recognize the value as valid.
    This appears to be due to a timing issue as the validation of
    the field (which takes place even though there is no
    FIELD_VALIDATION hook attached) happens before the value of the
    field in which the value was entered is also populated into the
    other fields.
    
    What's more, if the value is entered on any other field than the
    first field (i.e. for example on the second tab), the value
    disappears after the error message is displayed. A value can
    only be entered on the first tab.
    
    Similary, if the value of the field is deleted from any other
    field than the first field (i.e. for example on the second tab),
    the value of the field reappears in the field after the error
    message is displayed. The value can only be removed from the
    first field.
    
    
    This problem does not occur in the Windows RCP client.
    
    Steps to reproduce:
    
    
    
    - Use SAMPL database
    - Put 'headline' field on second tab of 'Defect_Base' form
    - Check in Schema, upgrade DB
    - Log in to DB from Solaris 9 client and run 'All Defects' query
    - Select first record returned, start 'Modify'
    - Remove the value from the 'Headline' field on the first tab.
    -? A correct error message appears twice (once for every
    occurrence of the Headline field)
    - Enter a value in the 'Headline' field on the first tab and
    switch to another field -? An error message occurs, saying the
    field has no value but is mandatory (this refers to the
    'Headline' field on the second tab).
    - Switch to second tab, remove value from 'Headline' field -?
    The error message appears, but the value reappears.
    
    
    
    Workaround:
    
    
    None known
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The ClearQuest eclipse client does not recognize field value
    as present if exists multiple times on form.
    

Problem conclusion

  • A fix is available in ClearQuest 7.1.1.8, 7.1.2.5 and 8.0
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM28911

  • Reported component name

    CLEARQUEST UNIX

  • Reported component ID

    5724G3601

  • Reported release

    711

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-14

  • Closed date

    2011-12-19

  • Last modified date

    2011-12-19

  • 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

    CLEARQUEST UNIX

  • Fixed component ID

    5724G3601

Applicable component levels

  • R711 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 December 2011