![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Why is inheritance turned off when sharing is turned on? Topic Summary: Created On: 27-Aug-2003 00:31 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
When a module is shared it turns inheritance off on each object in the module. If a new group is added to the project or if access to a particular group is changed the module objects do not reflect the update.
Therefore, as a workaround I have to run a script that turns inheritance back on for each object object. Then I have to set the sharing again. Bug or feature? |
|
![]() |
|
![]() |
|
Hi Douglas,
I have encountered the same problems - it's more a deficiency of DOORS than anything else - Shareable mode can be most useful but is not supported with any built-in functions to assist with changes to users and groups that should be included/excluded from the share. Removal of the shareable mode itself is not supported either - that is, once you have invoked shareable mode, the access rights of the objects at the level in which you have set up for sharable mode have their inhertitance property fixed to "Not inherited" - this can be a real trap for managing access rights. To get around this deficiency, you will have to write DXL, but my opinion is that functions to support shareable mode should be built-in out-of-the-box. ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.