Which parts in RQM need an update when saving a Doors Classic module with a view linked to a testplan?
I have an RQM 5.0.1 project connected with Doors 9.6.1 via DWA.
In my RQM project, there are testplans which link via the requirement collection section to views in Doors modules.
Now if someone changes i.e. the description of a requirement (which is in one of the views) in Doors, he is asked to log into RQM when saving.
I am wondering, which parts in RQM needs to be updated, when saving the change in the requirements!
Accepted answer
have looked into this a bit further.
Prior to saving....did you by any chance change the module from read only mode to exclusive edit?
I found a defect report (the defect is fixed in 9.6.1.1) which describes the same as you have here but the issue is only visible when you: upgrade from read only to exclusive edit, edit something, save the module.
Cheers.
2 other answers
what do you mean by "the description of a requirement "? Object Text? Some other attributes?
In the situation you describe I would not expect an attempt to log into RQM. This would be expected when creating/deleting OSLC links, performing link rendering etc. Do you have any triggers on the module that may be causing this? Or OSLC based integrations installed?
If RQM is logging requests or you're comfortable using fiddler I'd be interested to see what the request is from DOORS that's causing the login attempt.
Cheers,
Graeme.
Comments
Hi Graeme,
It is happening when changing the object text (even if this particular object has not direct link to RQM). But I think it is also happening for all other attribute changes. I will check that as soon as I need log in again (seems that the session has a timer).
I did not create or delete any links. Link rendering I do not even know :-)
The only thing we have set up is the connection between RQM and Doors via DWA and the links from/to the testplans as described in the original question.
Using Fiddler somehow does not work for me. It seems, that is is not fetching the Doors communication by default. Can you help me on that topic?
Thanks a lot!!!
Hi Jochen,
sounds like this isn't going to be trivial to answer (or investigate for that matter). As such I'd recommend raising a PMR and getting support involved as they'll have more time to devote to this then me.
Cheers,
Graeme.
Hi Graeme,
thanks a lot for your help. Trying to raise a PMR now via our tools department!
Hi again,
it also seems to be hard, to raise a PMR for me :-(
At least, I got some new information:
The role I need to assign to the people in RQM that need to be able to save the Doors module does not need to have any write access to RQM. So Doors only seems to fetch some information. The question is, for which purpose?