![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Reset Access Rights for sharing Topic Summary: Created On: 5-May-2004 14:19 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
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 ![]() |
|
![]() |
|
![]() |
|
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 |
|
![]() |
|
![]() |
|
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) "" |
|
![]() |
|
![]() |
|
[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 |
|
![]() |
|
![]() |
|
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).
|
|
![]() |
|
![]() |
|
So that was MY code in the DXL forum. How embarrasing. There are two closing parens in the isAccessInherited line.
- Louie |
|
![]() |
Telelogic DOORS
» General Discussion
»
Reset Access Rights for sharing
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.