![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Modified VIEW - modifed Access Rights ???? Topic Summary: Modifying Views changes Access Rights Created On: 1-Jul-2005 18:18 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
We are new to using Telelogic DOORS, so this might be an obvious thing to some of you. If so, I hope you can give me a quick answer.
We are setting up our DOORS system before masses of users start using it. A team of us is doing this, we find that if one of us on the team of database managers modifies a VIEW and then SAVE AS the same name, making it PUBLIC, that the Access Rights get changed. So that only the person who edited it has full access. The rest of the Group is elliminated and Everyone Else is Readyone. Is there a setting that will cause the Access Rights for a View to remain the same? |
|
![]() |
|
![]() |
|
Alan,
What version of DOORS are you using. We found the same thing happened to us with DOORS 7.0. I can't remember whether it was v7.0 SP1 or v7.1 that added the custom access rights option. Creating a new view, ie from Standard View, and saving as a public view gives only the user who saved the view full access rights. The user must then go into Manage Views and change the access rights as necessary, usually by ticking 'inherit access rights', this then creates a view with custom access rights. If you create new views using an existing view which has custom access rights and save as a new view it will inherit the custom access rights from the original view, ie you will not need to Manage Views to change the access rights for the new view. Hope this helps, not sure if DOORS 8.0 will change the default for new views to inherit. ------------------------- - Martin |
|
![]() |
|
![]() |
|
The "private-public" buttons simply set the views accesses to defaults, the real difference is whether other's can Read it. You'll need to explicitly set the accesses for these view for these system-wide views giving your Database and project managers full access and everyone else R.
- Louie |
|
![]() |
|
![]() |
|
We are on DOORS 7.1, build code 71167.
So it appears that there is NO way that Telelogic DOORS can allow a team to jointly develop and refine a View, without forcing the user to re-set the team's access rights after each and every modification?
|
|
![]() |
|
![]() |
|
Your problem is caused by using the standard view as a starting point.
The standard view, is by definition READ-ONLY to everyone. DOORS creates new views as private by default, so when you set it as public it merely confirs read access to everyone else. Do this: Create a new view, say default view and explicity set the access right to inherited or RMCDA for all or whatever. Then use this view as the starting point for new views, setting them pblic as you go. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.