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: Reset Access Rights for sharing
Topic Summary:
Created On: 5-May-2004 14:19
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.
 5-May-2004 14:19
User is offline View Users Profile Print this message


Frederick Simmler

Posts: 2
Joined: 10-Jul-2003

We recently converted access rights from individual user names to groups. This helped in the management of access to modules because the fluid nature of the user movement between projects was causing a nightmare. Now I just add or remove users from groups as they leave or start on the project.

Question #1:
It has caused another problem that I hope is easy to correct. The majority of our modules are set up for sharing and we have been required to go in and find each instance where the Access Rights are NOT set to “Inherit from parent”. We then set to inherit from parent, apply, and then remove the check mark from “Inherit from parent” This sets the inheritance to group based access. This is VERY time consuming and error prone. Is there a script I can run to set ALL objects in a module to “Inherit from parent” and then run the “Setup for sharing” script?

Question #2:
I have an object which, whenever I select the “Inherit from parent” check box, inherits access rights which do not match what I think would be the parent. How do I determine the object ID of the parent to an object? I need to find this so I can check it’s access rights.

Any and all help would be greatly appreciated.

Fred Simmler
United Space Alliance
321-861-6154/ -7544
Report this to a Moderator Report this to a Moderator
 5-May-2004 14:30
User is offline View Users Profile Print this message


David Rose

Posts: 80
Joined: 10-Oct-2003

Fred,

I had a problem similar to your question #2. The permissions were all messed up on an object one of my users needed to delete. I found that "surfing" the module explorer gave me the information that I needed to fix the problem. It could still be a slow and tedious process but its the best method I've found.

Good Luck

-------------------------
David A. Rose TSgt USAF
NCOIC System Administration
Report this to a Moderator Report this to a Moderator
 5-May-2004 16:46
User is offline View Users Profile Print this message


Brian Azelborn

Posts: 36
Joined: 2-Dec-2002

Here's a DXL script that I use to remove all specific access from a module.

// Resets all specific access within the current module back to inherited

/*
Removes all specific access from the current module
*/
pragma runLim, 0

Object o

bool accessIsSpecific(Object oCur) {
bool bSpecAccess = false // default to false
AccessRec arTmp

for arTmp in oCur do {
bSpecAccess = true
break
}
return bSpecAccess
}

for o in (current Module) do {
if (accessIsSpecific(o)) { // test whether object has specific access rights
inherited(o)
}
}



Also, if you want to get the Object ID of the parent of the current Object, you can press Ctrl-Left Arrow to go to the parent. If that doesn't work, here's a DXL that should tell you the ID:

Object oCur = current
Object oPar = parent oCur
ack "Parent ID: " (identifier oPar) ""
Report this to a Moderator Report this to a Moderator
 5-May-2004 20:22
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

[1] You can cause existing Specific-Access objects (= shared sections) to re-inherit the Module's access records as part [1] attached.

[2] The attached functions recursively finds the parent SECTION object for the given object, if any.

- Louie
Report this to a Moderator Report this to a Moderator
 23-Jun-2005 15:07
User is offline View Users Profile Print this message


Kirk Walker

Posts: 32
Joined: 18-Sep-2004

The (1) DXL for some reason gets syntax error on the "isAccessInherited", "inherited", and "specific" lines. I had been trying something similar and my stuff didn't work either (DOORS 7.1).
Report this to a Moderator Report this to a Moderator
 23-Jun-2005 23:19
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

So that was MY code in the DXL forum. How embarrasing. There are two closing parens in the isAccessInherited line.

- Louie
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 0 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 0 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.