Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Adding new group when module is set for sharing
Topic Summary:
Created On: 26-Aug-2003 15:21
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 26-Aug-2003 15:21
User is offline View Users Profile Print this message


Adam Gerber

Posts: 17
Joined: 8-Oct-2002

Several of my modules are set for sharing. When a module is shared it turns the 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 see the update. Therefore I have to run a script on the module that loops through each object setting each inheritance to on for each object. I then have to set the sharing again. Is there another method (better) for doing this? This gets to be an annoyance.

I’m running 5.2 and plan on going to 7.1 when it is available. Maybe this is not an issue in the next version.

Adam
Report this to a Moderator Report this to a Moderator
 27-Aug-2003 00:33
User is offline View Users Profile Print this message


Douglas Zawacki

Posts: 97
Joined: 14-Aug-2003

Adam,
I have had the same issue and have done exactly the same thing you have done to correct the problem. I have created a post that asks the question "Why is inheritance turned off when sharing is turned on?" because it certainly seems like a bug.
Report this to a Moderator Report this to a Moderator
 27-Aug-2003 03:21
User is offline View Users Profile Print this message


Paul Miller

Posts: 376
Joined: 2-Oct-2002


I've got a feeling that inheritance is disabled during Shared access to protect against cases where a locked area doesn't traverse the full object tree ie: an inherited change, whether it be to access rights or an attribute, cannot traverse into areas that are not locked for editing.



-------------------------
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
Report this to a Moderator Report this to a Moderator
 19-Sep-2003 20:00
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

It was a deliberate design issue to equate "specific access" with "shared sections". I don't think that was a good decision and they should change it. However, that makes this an "undesirable feature" and not a "bug".

Anyway, try something like this:

for oCurr in mod do
{ if (!isInherit(oCurr))
{ set it inherited
set it back to specific
}
}

This, each object will re-inherit the module's current accesses. Be advised that this WILL erase any specific access you have given to sections for specific users.

- Louie
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.