IBM Support

PI61764: DOORS/CM: PROBLEMS APPLYING RCR WHEN MANDATORY FIELD FOR APPLY STATE NOT SET IN RTC

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as documentation error.

Error description

  • An RCR won't properly apply if RTC has a mandatory field to
    transition to the apply state which has not be set by the end
    user. The RCR ends up in an unknown state.
    
    Steps to reproduce:
    1. In the RTC process make the "Planned For" attribute mandatory
    in order to transition an RCR to the "Applied" state
    2. Through DOORS/CM, work an RCR against a module through to the
    approved state
    3. Leave the "Planned For" attribute in RTC unset
    4. In the DOORS module, select "Change Mangement" >
    "Requirements Change Request" > "Apply..."
    5. Attempt to apply the RCR from step 2
    
    Expected Results:
    The integration should prevent the RCR from being applied and
    perhaps give a warning saying there is a mandatory field in RTC
    that needs to be set before the apply can happen.
    
    Actual Results:
    - There is an error that says: "Cannot transition RCR
    Requirement Change Request 138 to rcrworkflow.state.s5."
    - The status log on the apply dialog says "Applying RCR
    Requirement Change Request 138 Failed."
    - And now the "Target Modules" in the Apply dialog goes blank.
    But the RCR still remains in the dialog. If you try to apply it
    again you get this message in the status log:
    Apply process Stopped!!!
    ===================================================
    Start processing Requirements Change Request Requirement Change
    Request 138 :
    ===================================================
    RCR Requirement Change Request 138 has already been applied.
    
    Applying RCR Requirement Change Request 138 Cancelled.
    - If you look in the DOORS/CM config files for this module and
    RCR you will notice there is an "applied" folder created and the
    RCR action xml file says the doorsIsApplied is TRUE and the
    status is readonly. So it seems like the integration still tried
    to actual do the apply even though it shouldn't have.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users.                                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * DOORS documentation. Problems applying RCR when mandatory    *
    * field for apply state not set in RTC.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • This has been resolved in the DOORS 9.6.1.9 release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI61764

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    961

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-02

  • Closed date

    2017-12-19

  • Last modified date

    2017-12-19

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels



Document information

More support for: Rational DOORS

Software version: 961

Reference #: PI61764

Modified date: 19 December 2017