Exclusive open mode

llandale - Fri Jul 09 13:24:59 EDT 2010
Most likely you lack modify rights to any of the objects, or less likely lack modify rights to any of the attribute (values). Right click on an object, properties, access; it tells you your rights.

• Louie

SystemAdmin - Sun Jul 11 23:32:27 EDT 2010
I kind of wonder if this module has previously been configured for shareable edit mode and some where down the track the module level access rights have been modified to provide edit access to some new users. However, these changes to access rights at the module level will not have any effect on the objects as the "Inherit from parent" option will have been disabled by setting up the module for shareable edit mode. After all of these years - I still don't understand why DOORS doesn't have a menu options to remove or refresh shareable edit mode.

---

Paul Miller

BPA - Tue Jul 13 21:09:33 EDT 2010
Thanks all for your responses.

Paul you are right that this module has been configured for shareable edit mode. At the time of the configuration, the module level access rights were set as follows:

• DB Admin (RMCDA)
• Everyone else (R)

Followed that I added a new user group which has RMCD access to the module. This was when the issue occured - members of the new user group were not able to edit in the exclusive mode.

Peter I have also checked the individual attribute’s access rights, and they all have RMCD (‘Inherit from parent’ option is enabled).

And yes Louie the New User Group has a None access to the objects.

Is there a way to populate the correct rights to objects in bulk?

Is there a way to manually remove the shareable edit mode?

BPA - Tue Jul 13 21:09:33 EDT 2010
Thanks all for your responses.

Paul you are right that this module has been configured for shareable edit mode. At the time of the configuration, the module level access rights were set as follows:

• DB Admin (RMCDA)
• Everyone else (R)

Followed that I added a new user group which has RMCD access to the module. This was when the issue occured - members of the new user group were not able to edit in the exclusive mode.

Peter I have also checked the individual attribute’s access rights, and they all have RMCD (‘Inherit from parent’ option is enabled).

And yes Louie the New User Group has a None access to the objects.

Is there a way to populate the correct rights to objects in bulk?

Is there a way to manually remove the shareable edit mode?

void  RefreshSection(Object obj) 
{ 

if (

null obj) 

return bool  IsInherit Object oChild isAccessInheritied(obj, IsInherit)   

if (!IsInherit) 
{  specific(obj) inherited(obj) 
} 

for oChild in obj 

do 
{  RefreshSection(oChild)  
// *** RECURSION *** 
} 
}  
// end recursive RefreshSection()   Object oTop 

for oTop in top (current Module) 

do 
{  RefreshSection(oTop) 
}

llandale - Wed Jul 14 11:13:25 EDT 2010
Sadly, shared sections are implemented via object access rights. Once you set an object to 'Specific' and no longer 'Inherited', you get a shared sections. But since it does not 'Inherit', adding a group to the module will not add it to these objects. You need to 'refresh' the module's objects with the new Module rights.

The following should do this 'refresh'. Note that if you already provided certain folks access to certain objects, those will be erased.

void  RefreshSection(Object obj) 
{ 

if (

null obj) 

return bool  IsInherit Object oChild isAccessInheritied(obj, IsInherit)   

if (!IsInherit) 
{  specific(obj) inherited(obj) 
} 

for oChild in obj 

do 
{  RefreshSection(oChild)  
// *** RECURSION *** 
} 
}  
// end recursive RefreshSection()   Object oTop 

for oTop in top (current Module) 

do 
{  RefreshSection(oTop) 
}

The normal "for obj in entire module" loop might not work since you must insure that all parent objects of an object are refreshed before you refresh this object.

An alternative method is to store all the 'specific' objects in the module, set them all 'inherited', then set those back to 'specific'.

• Louie