Locking of connectors does not work in EA 8.0

[Adrian Cook]

Here's the background of my issue: Security is turned on in my project. There is a use case that is locked by a certain group. That use case has connectors (Realization relationships) pointing to multiple requirements in a different package. Those requirements are also locked, by a particular user.

Here's the issue: I can delete those connectors from the Relationships window, even though I am logged in neither as the user that has locked the requirements nor as a member of the group that has locked the use case. This appears to be a bug, especially since online help states: "If an element is locked, connectors attached to it are also locked. To unlock the connector, you must unlock the element." Well, they sure don't seem locked to me.

Has anyone else ran into this? Has it been reported as a bug? We're running EA 8.0.864. I've scanned the list of changes in versions since then and I don't see anything to suggest that this problem has been fixed.

Thanks,
Adrian

[Geert Bellekens]

Adrian,

I've noticed that too in some circumstances.
I also noticed that the locking mechanism used for version control seems to work better.

Geert

[Dave_Bullet]

I believe locking simply works on things contained in packages (and their children).  Connectors as such don't really belong to any package.

the problem is
1. User A attempts to lock element 1
2. User B attempts to lock element 2
There was already an existing connection between 1 and 2

what should have happen?

If you assume all connectors attached to an element get locked by the user locking the element, then you have to cascade that to elements attached to those connectors (for example - you cannot let the element pointed to be deleted if the connector requires it).  Pretty soon one user ends up locking the whole model.

I don't have an answer, but can see the design dilemma