"Get Latest" not available for certain packages

[ChrisDr]

Hi all,

I have the situation where I have branches of individually version controlled packages that are used from two different models. When someone updates a model branch within one model and checks it in, a "Get Latest" on that package in the other model updates the model itself and they are again in sync.
Problem now is that this works for nearly all packages, but suddenly for one package the "Get latest" menu item is gray and cannot update the corresponding package. Version control setup rules forbid checkouts so the only way to get an updated model is to do a "Get Latest"

Does someone have any idea how such a situation can happen?

Thanks in advance

Best regards,
Chris

[«Midnight»]

Without proof, I suspect you might see something like this if some diagrams or packages are locked. That behavior could cause some packages to be locked - they might contain elements that appear or are referenced by locked items - and might produce variable results depending on which user tries to check out packages.

[ChrisDr]

Do you refere to "locking" with respect to EA Security? We don't have this feature enabled as the locking itself is done via the version control setup. The version control environment doesn't show any checkouts and there are no sub-packges within this one that could (maybe) cause some locking issues.
Are there any known-issues related to EA-ClearCase integration regarding such behavior?

A temporary fix was to reconfigure the version control setup to allow check-outs. I did a checkout of this particular packages which updated the model immediatly followed by an undo-checkout. But "Get Latest" remains unavailable.

Thanks for your support!

[«Midnight»]

No, I meant something a bit different. In the EA help index, look up Locking | Diagram, Security Off.

[ChrisDr]

The "Lock Diagram" feature behaves a little bit different when version control is enabled for the package where the diagram resides (at least when I compared it with a project that has no VC enabled).
All diagrams in checked-in packages are always "locked", when doing a check-out, they are automatically unlocked (according to the settings in the context menu of the diagram).
You're right that the diagram is actually locked when checked-in (which makes sense) but I cannot change this setting without check-out, but that is what I actually want to avoid.

[«Midnight»]

What I was thinking of is a variant of what you describe. I believe that an element - this might apply to the entire diagram such an element is shown on; you'll have to check if it might apply to you - cannot be edited if it is linked to a locked element elsewhere (perhaps in another package tree). I was thinking that this might prevent your edit, even though the package your element resides in is unlocked.

[Lars H]

Are you 100% sure that no other users has the package checked out? That would and should disable Get Latest, to avoid overwriting that user's changes.

[ChrisDr]

Yes, 100% sure, the version control setup is such that no check-outs for this particular package are possible and I also verified it with the Version control tool itself that no other user has a lock/check-out on this packages.

I have to check the subelements regarding locking as described in the previous post.

Chris