BUG: Getlatest not working when using EA security

[Geert Bellekens]

Hi,

We use the security feature in EA with the option "Require user lock to edit" option.
Recently I've controlled a part of the model in TFS.
One of the issues is that I can't do a "getLatest" because the package I try it on is not "locked" by me.
I also cannot lock the package since that option is greyed out when controlling a package in TFS.
The only option I have to get the latest version is to do a checkout, and then an "undo checkout".
EA should allow a getLatest on packages who are not locked by me.

Steps to reproduce:
- Setup EA using security and the option "Require user lock to edit"
- Control a package in TFS (or another VC I guess)
- Make sure the package is checked-in, and the lock are released.
- Select option "Package Control/Get latest..."
- Notice the error saying that the necessarry security is not available.

Reported

Geert

[Geert Bellekens]

Received a response from Sparx:

Thanks for your note.

Having Project Security enabled is only practical when using a Shared
Model deployment. That is, there are many users all connecting to the
same (single) instance of the model database.

With Shared Models, the model database is always up to date with respect
to the information stored under version control, because the (single)
model DB is updated first, before any package is exported and committed
to VC. (The only exception to this is when a given package is used in
a number of different model databases. Either as a common "standard"
package that is used in more than one distinct Shared Model, or of
course in a Private Model deployment.)

Given this, it seems reasonable to disallow the "Get Latest" command
unless a user lock has been applied.

In regard to locking the Version Controlled package, we agree it would
be better if the user lock could be applied and released whilst the
package is still checked-in, thus avoiding an unnecessary import or
export through subsequently having to "undo checkout" or "check-in".
Our developers are investigating ways to remedy this.

If you have further questions or issues please let us know.

To be clear, I'm actually using the "common standard" package setup, that's why I need a "getLatest" function although my model is shared.

Geert

[Geert Bellekens]

I just tested this on version 7.5.850 and they have created an acceptable workaround.
You can now lock the packages prior to doing a "getLatest".

OK, so now this hurdle is out of the way, up to the next one. We now have "getLatest" working, but "get All Latest" is not yet working nicely with the locking feature..
Sigh, I'll have to create another bug report I guess.

Geert