cannot edit in exclusive edit

DOORS client 9.3.0.5

I created new project with a set of un-inherited access rights, with two groups having edit access, one particular to the project and one overall admin-ish group. I copied a module into this project and set its access rights to inherit from parent. I can edit this module normally; I am in that admin-ish group. However, users in the project-specific group found in the project's access rights cannot edit the module. They can enter exclusive edit mode, but the grey read-only background shows and they cannot edit. When the user brings up the module properties window and show the access rights tab, it shows they have the edit right, i.e. "Access rights for X: RMCD". So they ought to be able to edit the module, but can't. When I create a new module in the project, the project group can edit this module.

Anyone seen this before? Any idea how to fix this?

Thanks!

Re: cannot edit in exclusive edit
oaklodge - Fri Jan 30 07:47:05 EST 2015

Never mind...

The problem was sharing. The copied module had been setup for sharing, and so the objects were not inheriting the access rights. Duh.

Re: cannot edit in exclusive edit
llandale - Tue Feb 10 18:21:21 EST 2015

Jump straight to [2] below.

[1] I'm too lazy, but somewhere there is some kind of "refresh shared sections" program, which effectively resets all shared sections to have the same access as does the module.  At its core it would:

• "edit" the module
• for each o
• {  if (specific(o))
•     {  inheritied(o)    // Inheritie access from above
•        specific(o)       // reset to Specific
•     }
• }

This works so long as an object is only ever considered AFTER all it's parent objects have been considered; otherwise it will refresh stale accesses.  The "for o in entire mod" loop should suffice for that, but it seems to me that somewhere I wrote a "for o in top mod" followed by recursive "for o in o do" loops; just to make sure.

There is also the considerable problem dealing with deleted objects wiith specific rights.  I'd say undelete-refresh-delete them.

Don't forget about this restored module specific rights for Views, AttrDefs, AttrTypes, and AttrDefs.

Yuuuuck; forget all that:

[2] Restore the module in some foriegn database, then archive it again.  That will erase all the specific accesses when it is restored in the original database.

-Louie