![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Module Access Issue with DOOR 7.0/7.1 Topic Summary: A user with Read access opened a module in Shareable Edit mode Created On: 3-Dec-2007 18:10 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
We are using DOORS 7.0 with at least one DOORS 7.1 client (myself) and we recently saw that a user had managed to open a module in Shareable Edit mode even though he only has Read access to the module.
I have not yet received a reply from him on what method he used to open the module, but the best guess is that he was in a different module in the same project and followed an outgoing link into the module in question. I couldn't find anything in the Knowledge Base or in the list of resolved issues for the various DOORS 8 versions. Does anyone have any thoughts? ------------------------- Jeremy Eble Software Engineer Teragon Consulting LLC jeremy.r.eble@lmco.com |
|
![]() |
|
![]() |
|
Back in v4.2 days, the open mode of a module had nothing to do with any rights you have to it. Sloppy folks would open a module for 'edit' even though they possessed only 'R' rights. They couldn't do anything but nobody else could edit it. That makes a little sense. The mode in which you open a module is a different thing than your rights to it.
Telelogic 'resolved' that by greying-out 'edit' and 'share' open options in the menues when the user lacked more than 'R' rights. I thought, however, that you could still open it Edit or Shared. I'm pretty sure in v5 and v6 you could still open it in an improper mode. Well, I was wrong. In v81: I tried using DXL to 'edit' a module to which I had only 'R' access, and it opened it Read. I tried using 'setExclusive()". I tried setting defopenlinkmode to 'READ_WRITE_SHARED' and then followed a link, and it still didn't do it. Perhaps you could still do it in v71. - Louie |
|
![]() |
|
![]() |
|
I have the same notion that this "feature" was fixed somewhere between version 7 and 8. But did not find any mention of it in the DOORS documentation.
------------------------- Pekka.Makinen@softqa.fi SoftQA Oy -http://www.softqa.fi/ |
|
![]() |
|
![]() |
|
Louie, could you post your test code? I still have occasion to use 4.2 and I know exactly what you're talking about. I had forgotten about it, though.
The user is fairly certain that he only uses the right-click menu to open a module, but who knows? I'm also not convinced that there is a problem since I didn't see it myself and we have a couple of modules that have very similar names. ------------------------- Jeremy Eble Software Engineer Teragon Consulting LLC jeremy.r.eble@lmco.com |
|
![]() |
|
![]() |
|
Didn't save the code. Try the following:
functions setExclusive() and setShare() and setReadOnly() changes the edit mode of the current module to Exclusive-Shared-ReadOnly respectively. These functions are used by the module Edit >Edit Mode.. menu. To make sure of the current module, they should routinely be preceeded by "current = mod". I have some very old code that used those functions, but for some reason that I don't recall but I see a note that it works only on visible modules. I abandoned them in favor of this sequence: ... downgrade(mod) // sets module read-only. Don't recall if this prompts to save or not ... mod = edit(fullName(mod)) // or share(). I see in my code that downgrade is surrounded by noError() and lastError(), don't recall why. There is also a downgradeShare(mod) function, that changes from Edit to Shared. - Louie |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.