PM14509: ReqWeb:Re-adding the same requirement in traceability returns an incorrect messgae

APAR status

• Closed as program error.

Error description

• ReqWeb 7.1.1.1 now has the ability to select multiple requiremen
  ts in the traceability search popup.
  
  If a user re-selects a requirement that is already traced, then
  a message is shown indicating circular traceability. In reality,
   it's a duplicate trace, and not a circular trace. Please fix th
  e error to show
  the appropriate message.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When trying to add a requirement Trace To/From relationship
  that already exists, the User error message given provide
  information that is not clear to the user ( Requirements key
  ). Message should show information that clearly especify
  which requirement trigger the error.
  

Problem conclusion

• User error message has been changed to show the Requirement
  Tag instaed of the Requirement key. With the Tag, the user
  can easily find the requirement triggering the error.
  

Temporary fix

Comments

APAR Information

• 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

  REQUISITEPRO WI

• Fixed component ID

  5724G3900

Applicable component levels

• R711 PSN

     UP