IBM Support

PI08792: Proposals Module displays proposed value as Default value of attributes even if no proposal is raised for that attribute

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Current behavior: For attributes which has default values
    proposal module shows up default value as proposed value
    although user has not specified any proposal for that attribute.
    
    Steps to reproduce:
    ===============
    1? Create a Module in DOORS and create custom attribute with
    some default value. Lets say, create a Text based attribute
    named 'Is Urgent' and let it have a default value of 'Yes'. For
    one of the Objects say Object ID # 1 in the Module, you can
    change the value of the 'Is Urgent' attribute from 'Yes' to
    'No'.
    
    2? Create a DOORS Change Proposal System and include the above
    mentioned Module and Custom attribute in it.
    
    3? Submit a CP on any Object for any other attribute other than
    the default valued attribute. In our example, lets propose a CP
    on Object ID # 1 and propose to modify the Object Heading to
    some value.
    
    4? Once the proposal has been changed, open the corresponding
    Proposals Module and insert a column for 'Proposed Is Urgent'.
    You would notice that the default value of 'Yes' for the 'Is
    Urgent' attribute is added in the column. i.e. even though there
    was no proposal raised to change any value corresponding to the
    'Is Urgent' attribute, the proposals Module still shows as if
    its been proposed to change the value of that attribute to its
    default value.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * all users/environments affected                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Current behavior: For attributes which has default values    *
    * proposal module shows up default value as proposed value     *
    * although user has not specified any proposal for that        *
    * attribute.                                                   *
    *                                                              *
    * Steps to reproduce:                                          *
    * ===============                                              *
    * 1? Create a Module in DOORS and create custom attribute with *
    * some default value. Lets say, create a Text based attribute  *
    * named 'Is Urgent' and let it have a default value of 'Yes'.  *
    * For                                                          *
    * one of the Objects say Object ID # 1 in the Module, you can  *
    * change the value of the 'Is Urgent' attribute from 'Yes' to  *
    * 'No'.                                                        *
    *                                                              *
    * 2? Create a DOORS Change Proposal System and include the     *
    * above                                                        *
    * mentioned Module and Custom attribute in it.                 *
    *                                                              *
    * 3? Submit a CP on any Object for any other attribute other   *
    * than                                                         *
    * the default valued attribute. In our example, lets propose a *
    * CP                                                           *
    * on Object ID # 1 and propose to modify the Object Heading to *
    * some value.                                                  *
    *                                                              *
    * 4? Once the proposal has been changed, open the              *
    * corresponding                                                *
    * Proposals Module and insert a column for 'Proposed Is        *
    * Urgent'.                                                     *
    * You would notice that the default value of 'Yes' for the 'Is *
    * Urgent' attribute is added in the column. i.e. even though   *
    * there                                                        *
    * was no proposal raised to change any value corresponding to  *
    * the                                                          *
    * 'Is Urgent' attribute, the proposals Module still shows as   *
    * if                                                           *
    * its been proposed to change the value of that attribute to   *
    * its                                                          *
    * default value.                                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DOORS 9.6                                         *
    ****************************************************************
    Fixed in DOORS 9.6 and its client side fix
    

Problem conclusion

  • Fixed by modifying code in DOORS 9.6
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI08792

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    951

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-12-31

  • Closed date

    2014-06-07

  • Last modified date

    2014-06-07

  • 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

    TLOGIC DOORS

  • Fixed component ID

    5724V61DR

Applicable component levels

  • R960 PSY

       UP



Document information

More support for: Rational DOORS

Software version: 9.5.1

Reference #: PI08792

Modified date: 07 June 2014