PM01103: Traceability Tree (Traced out of...) is not refreshing properly when a requirement has already an existing trace and you add

APAR status

• Closed as program error.

Error description

• Problem description
  ReqWeb 7.1.0.2
  Windows Server 2003 SP2
  1) Create a view 'traced out of'
  
  2) Open the view
  
  3) modify a requirement in the view and add a new trace to
  4) Save the requirement.
  
  5) go to the view again.
  --? changes are not reflected; not even when pushing F5. You hav
  e to
  logout/login to make the changes visible!!
  
  ---? if the requirement modified didn't had a trace already you
  need to add a second 'trace to' to reproduce this issue.
  This is a very urgent bug and must be resolved asap!
  
  
  apparently, it's not even possible to update the query either al
  l seems lock on the view until you logoff login again
  

Local fix

Problem summary

• Problem description
  ReqWeb 7.1.0.2
  Windows Server 2003 SP2
  1) Create a view "traced out of"
  
  2) Open the view
  
  3) modify a requirement in the view and add a new trace to
  4) Save the requirement.
  
  5) go to the view again.
  --? changes are not reflected; not even when pushing F5. You
  have to
  logout/login to make the changes visible!!
  
  ---? if the modified requirement didn't had a trace already
  you need to add a second "trace to" to reproduce this issue.
  

Problem conclusion

• Starting the default Depth Level on Trace Tree View in "1"
  for problems refreshing new traces. Additionally, the ReqWeb
  documentation the default depth level is "1".
  

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

• R701 PSN

     UP