IBM Support

PM84755: None access to attribute definition results in value not being visible in trace columns

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • If a user has no access to an attribute definition, but (read)
    access to the values of the same attribute, those values will be
    shown in a standard column, but not shown in trace columns.
    
    This is a result of probeRichAttr_() giving precedence to the
    definition permissions.
    
    Workaround: Use richText() instead of probeRichAttr_().
    
    To recreate:
    
     - create source and target module with links between each
     - create an attribute in the source and assign 'None' access to
    the definition for a given user (leave at least read access to
    the value)
     - assign some values to this attribute for linked objects
     - in the target, run the analysis wizard and create a trace
    column for in links which shows the above attribute
     - save the column as part a view
     - as the user with restricted access, login, open the new view
    and examine the contents - the values will not be shown
    
    This behaviour is the same in v8.3.
    
    There are other inconsistencies in behaviour when attribute
    definition access is none.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users affected                                           *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * If a user has no access to an attribute definition, but      *
    * (read)                                                       *
    * access to the values of the same attribute, those values     *
    * will be                                                      *
    * shown in a standard column, but not shown in trace columns.  *
    *                                                              *
    * This is a result of probeRichAttr_() giving precedence to    *
    * the                                                          *
    * definition permissions.                                      *
    *                                                              *
    * Workaround: Use richText() instead of probeRichAttr_().      *
    *                                                              *
    * To recreate:                                                 *
    *                                                              *
    *  - create source and target module with links between each   *
    *  - create an attribute in the source and assign 'None'       *
    * access to                                                    *
    * the definition for a given user (leave at least read access  *
    * to                                                           *
    * the value)                                                   *
    *  - assign some values to this attribute for linked objects   *
    *  - in the target, run the analysis wizard and create a trace *
    * column for in links which shows the above attribute          *
    *  - save the column as part a view                            *
    *  - as the user with restricted access, login, open the new   *
    * view                                                         *
    * and examine the contents - the values will not be shown      *
    *                                                              *
    * This behaviour is the same in v8.3.                          *
    *                                                              *
    * There are other inconsistencies in behaviour when attribute  *
    * definition access is none.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Fixed - client-side fix. Now the user can see the attribute
    value in the layout DXL column even when he has None access to
    the attribute definition providing he has at least Read access
    to the attribute value.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM84755

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    930

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-13

  • 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.3

Reference #: PM84755

Modified date: 07 June 2014