![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Who create a view? Topic Summary: Created On: 16-Aug-2007 11:05 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Is it possible to find out who created a view?
It's not an option under Manage Views, unless the view creator sets it such that the access rights make them obvious, which I don't want to do. |
|
![]() |
|
![]() |
|
The only way to determine who created the view is by looking at access rights, and even then, only if they have saved the view public or private. And if someone saved someone else's public view as custom, well, then you can't even be 100% sure.
So there is no foolproof, sure-fire way to tell who created the view, unless you educate your users to save views with a naming convention. Say something like zTemp - <username> <viewname> If users don't adhere to this method, you have two options--create your own "Save View" dialog box and roll it out to all users, or create a script that deletes views that don't adhere to the convention. And remember, you'd have to run this as Administrator to get all views. My question to you--why do you care who created a view? What are you trying to accomplish, exactly? ------------------------- Kevin Murphy http://www.baselinesinc.com The Requirements Management Experts |
|
![]() |
|
![]() |
|
> My question to you--why do you care who created a view? What are you trying to accomplish, exactly?
We have a set of modules of a similar confirming style. One of these modules has a view created similar but not exactly to a set of views we are about to create, and would like to know who created it before overwriting it, just in case they need it. |
|
![]() |
|
![]() |
|
You could look through the module history it should be in there some where.....
------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
quote: Absolutely 100% incorrect. Views do not modify data, ever, so there is no history to keep. Create a new module. Add some objects. Add a column. Save the view. Look through the module history. You will not find anything. No view operations (save, modify, delete) are saved in a module's history. Further, since you can save and update module views when the module is opened in Read-Only mode, there would be absolutely no way for DOORS to store view changes in history. ------------------------- Kevin Murphy http://www.baselinesinc.com The Requirements Management Experts |
|
![]() |
|
![]() |
|
Alan...
Load the existing view, save it as a new view and add a -old after it or something. The user should see two views that appear to be named identically, and that will cause them to investigate. My first response still remains true--you need a view naming standard so you don't run into this problem again. Good luck. Kevin ------------------------- Kevin Murphy http://www.baselinesinc.com The Requirements Management Experts |
|
![]() |
|
![]() |
|
> My first response still remains true--you need a view naming standard so you don't run into this problem again.
We have one. But that doesn't preclude someone from creating a view that doesn't follow it. Also, the view name DOES conform. One suggestion is to precede (or append) a view names with the initials of the author but, for project-wide views that are also accessible by the customer, that isn't acceptable. So, I guess the answer is that I can't find out without locking the access to the view and waiting for someone to complain. Edited: 17-Aug-2007 at 06:30 by Alan Gooch |
|
![]() |
|
![]() |
|
If you have a naming standard and your users don't follow it, then you should tell them that any views that do not adhere to the standard are subject to deletion. That usually gets them in line. After all, it's just a view, not real data.
When you talk about project-wide views accessible by the customer--again, that sounds like something that an admin should set, and not a user. So called "standard" views or "project" views can have a different naming convention, and user views are for the convenience of your users, not necessarily your customers. I might sound like a control freak here, but the reason you're asking the question to begin with is because of a lack of control in the database combined with deficiencies in DOORS of managing views. I really do not like DOORS' view implementation, but until they change it, you've got to be really proactive and "police" your database for things like this. ------------------------- Kevin Murphy http://www.baselinesinc.com The Requirements Management Experts |
|
![]() |
Telelogic DOORS
» General Discussion
»
Who create a view?
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.