Lock indications not updated

[Uffe]

Hi!

We're using EA 9.1 in a DBMS repository, with the "Require Lock to Edit" policy. We have observed the following behaviour:
1) User A locks package P, including child packages.
2) User A sees P and its child packages as locked (blue exclamation).
2) User B selects P in the browser, and expands it.
3) User B sees P as locked (red exclamation), but not its child packages.

The desired behaviour would of course be that user B sees all child packages as locked as well.
Has anyone else observed this, and/or has any input?

Cheers,


/Uffe

[Geert Bellekens]

Yes,

We have the same setup, and I see the same behavior. The lock indicators only get updated when the GUI refreshes the content of the model, but that is the common behavior for all aspects of the model.
You won't see a change anyone else made until the GUI refreshes the content.
Using right click|Contents|Reload current package you can selectively reload a part of a model.

Geert

[qwerty]

What you desire is obvious. But it's extremely difficult to implement. For that you would need to subscribe as listener to your central database. Nothing a SQL server has build in. So you would need an additional server component. Which does not exist for good reasons. So the passive way EA is doing it is the best compromise you will find.

q.

[Uffe]

Yes, it makes sense for it to work that way since EA has no server of its own and the actual lock itself (in t_seclocks) does not remember whether it was applied recursively. Thought I'd check though. Thanks to you both.

/Uffe