![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: "Read Locked Data" showing in Module history records Topic Summary: Is this a bad thing? Created On: 13-Apr-2006 21:45 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Some of our modules show the phrase "Read Locked Data" in their history records. It says it across all four columns -- "User," "Session," "Date," and "Modification." Is this just DOORS trying to say that somebody opened the module in read-only mode while somebody else had it locked?
Or does it mean something else? I couldn't find any reference to this in the manuals. We're using DOORS 8.0.0.4. Thanks, Kevin |
|
![]() |
|
![]() |
|
Kevin, ------------------------- - Martin |
|
![]() |
|
![]() |
|
Martin,
Thanks for your reply. I did a little more research on the issue based on what you said. When I logged in as the built-in "Administrator" account I was able to see all the history records. What I found was that the "Read Locked Data" rows showed up whenever there was a record tied to an attribute that no longer existed in the module. Each one was an attribute that I deleted because we changed the way we planned to do something. I don't know why a permissions issue would arise based on that. Will keep looking. Thanks again, Kevin |
|
![]() |
|
![]() |
|
I had the same problem. Mine resulted from setting the module up for Shareable Edit. I went back in as Administrator and set each item's access permission to "inherit from Parent" and that cleared up my problem. I've never seen it before where DOORS sets the permissions different for each level in the shareable edit. This must be a new "feature" in DOORS 8.0
------------------------- David A. Rose TSgt USAF NCOIC System Administration |
|
![]() |
|
![]() |
|
This is DOORs fix for maintaining security of deleted attributes. In earlier versions, a deleted attribute could be viewed by anyone. This change keeps history access restricted as sensitive information may be visible in deleted requirements that have not yet been purged. Not a clean fix, but it keeps the info secure...
Dan |
|
![]() |
|
![]() |
|
Doh, I ment deleted Objects... not attributes
|
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.