![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: How to delete a view which was creating by a deleted user? Topic Summary: Created On: 7-Dec-2006 14:32 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi, i have a question. Edited: 7-Dec-2006 at 14:45 by Blasius Giers |
|
![]() |
|
![]() |
|
Use the DOORS built-in Administrator account, not some DOORS user account with Database Manager powers.
------------------------- Pekka.Makinen@softqa.fi SoftQA Oy -http://www.softqa.fi/ |
|
![]() |
|
![]() |
|
hi,
thx works! Blasius Giers |
|
![]() |
|
![]() |
|
Know this: AccessRecords store the RMCDA access along with the user's UniqueID. Thus, if you rename a user that user retains all her old accesses. If you delete a user then her old AccessRecords are unseen in the interface, and are presumably somehow removed in the background by DOORS (presumably via normal 'garbage collection' algorithms). Yes, creating a new user with the old name isn't going to work since the new user has a different UniqueID. I digress: if you archive the module with say User 22 access to the view and restore in a different DB, then whichever user in the new DB that has the old UniqueID 22 has accesss to the view; often that means nobody has access. You thus need to clear out access records from modules when restoring them (likewise for AttrDefs, AttrVals, and AttrTypes).
Yes, the 'Administrator' can see and edit everthing. v70 has these bugs: [1] even 'public' views are only editable by the user who creates it. After saving a view, Folks should ROUTINELY manage Views and adjust the Access to the view, presumably starting off by making the view Inherit its access from the module. [2] When the Administrator creates a view, the 'Administrator' is given an access record to modify it. That causes havok in other Access records issues with DXL since the Administrator user account (UniqueId #1) is available to anyone else. Thus, the Administrator either should never create a view or MUST perform step [1] right afterwards. - Louie |
|
![]() |
|
![]() |
|
This topic is a bit old, but we just came across this problem. I will cut the the essence with: BTW: I see all of my CR/LFs have been removed from my message. I don't see an FAQ. How do you put line feeds in your messages? I clicked the symbols hyperlink but did not see that. Oops, after I edited, all my line feeds appeared. Edited: 2-Aug-2007 at 16:55 by Bryan Kelly |
|
![]() |
|
![]() |
|
This little script allows you to reset the access rights to inherited for all items below the current folder.
Script is posted here.. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Bryan,
The only sure fire way to get a view to "inherit" in the DOORS interface when saving a view is to ensure that the view that you originally loaded was set to inherit and save as "custom" rights. Of course, you can't know that unless you got to Manage Views... I really, really dislike View Management in DOORS. Telelogic really needs to redesign the save view dialog to be more friendly. Instead of "Public" "Private" and "Custom" it should ask things like, "Let others see view? Yes/No" and "Let others update view? Yes/No." and "Inherit View Access from Module? Yes/No." I think those options alone would save thousands of hours of admin view management in modules. Public, Private, and Custom tells the user nothing and is unnecessarily confusing. ------------------------- Kevin Murphy http://www.baselinesinc.com The Requirements Management Experts |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.