IBM Support

PH11611: DOORS TRIGGERS SAVED IN A FORMAL MODULE ARE DELETED WHEN RQM USES ANY DOORS COLLECTION.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • DOORS triggers saved in a Formal module are deleted when RQM
    uses any DOORS collection.
    Steps to reproduce are :
    
    A- Preconditions for OSLC links between DWA and RQM must be
    fulfilled :
    1- DWA 9.6.1.4 in OSLC v1 mode (minimum client version is set to
    9.5)
    2- RQM/Jazz 6.0.6 iFix004 and DOORS classic are defined as
    consumers/friends
    
    Defect reproduce using DWA 9.6.1.9 and 9.6.1.11 with RQM 6.0.5
    
    
    B- in DOORS
    1. Open a doors module in exyclusive Edit mode.
    2. Select the menu Tools->Edit DXL and enter the following code
    to define an attribute post modify trigger e.g.
    trigger( "Object_Text", module->attribute->"Object Text", post,
    modify, 1, "
               Trigger t=current
                  Object objActual = object(t)
                  if (null objActual) halt
                  Module modCurModule = module(t)
    
               ack \"trigger\"
    
    " )
    
    3. verify the trigger is there by changing an Object Text. The
    dialog "trigger" should appear
    4. Save and close the DOORs module.
    
    C- RQM
    5. in RQM, define a project area and configure OSLC relationship
    such that the DOORs module used above can be linked.
    6. create a new Testplan, save
    7. in the test plan, section "Requirements collections Links",
    add a collection to the testplan (green cross button) ; select a
    view of the module prepared with a trigger in (B) above
    8.save the Testplan in RQM
    
    D- in DOORS
    9. open the Formal module prepared in (B) above in exclusive
    Edit mode, and change the object text.
    => See that no "trigger" dialog appears : the trigger was
    deleted.
    
    
    E- further operations deleting trigger
    Repeat the sections (B)(C)(D) above by replacing step 7 as
    follows
    10. "reconcile" collection
    11. delete collection
    => See that the trigger is deleted for any operation on
    collections
    
    F- kind of trigger deleted
    Repeat the sections (B)(C)(D) above by replacing step 2 as
    follows
    12. with a post open module trigger
    trigger( "RQM test", module, post, open, 1, "
    
               ack \"Hallo\"
    
    " )
    12. with additional post modifiy attribute trigger
    trigger( "Object_Text", module->attribute->"Object Short Text",
    post, modify, 1, "
               Trigger t=current
                  Object objActual = object(t)
                  if (null objActual) halt
                  Module modCurModule = module(t)
    
               ack \"trigger\"
    
    " )
    and any further attribute.
    => See that all trigger of any kind saved in the module are
    deleted.
    
    Workaround:
     Use link discovery instead of back linking so DOORS module
    won't be updated.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of Engineering Test Management (formerly Rational  *
    * Quality Manager)                                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Triggers saved in a formal module are deleted when RQM uses  *
    * any DOORS collection                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Client side fix.
    

Problem conclusion

  • This has been resolved in the DOORS 9.7 release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH11611

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    961

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-04-30

  • Closed date

    2019-07-05

  • Last modified date

    2019-07-05

  • 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



Document information

More support for: Rational DOORS

Software version: 961

Reference #: PH11611

Modified date: 05 July 2019