Migration from EA 10 to EA 14

[seweryn]

Hi,

We're planning migration from EA 10 (10.0.1010) to EA 14 (14.1.1429). Yeah... I know EA10 is "quite" old but it did its job through these years 
We use Oracle database repository, it has quite a number of objects which we'd still like to use in EA14 -- ca. 2000 diagrams and thousands of elements used in these diagrams.

Do you know any problems that may occur during such migration?
Sparx support says it's only opening repo in a new EA version, but so far we've noticed following major problem and looking for its resolution as it possibly impacts our ~400 diagrams and ~1000 connectors.

The problem is that connector labels of connectors that have 3 or more bends are placed by EA14 in other positions than by EA10 (links to screenshots at the bottom of this post). After investigating the issue it looks like EA 12.1.1230 changed default positioning for such connector labels and since actual label position is calculated basing on default position and relative offset from geometry then actual label position is different.

I will be thankful for any advice what else we should look at during this migration and a fix to the problem above (I know we have to recalculate and update offsets for such labels, thought that maybe someone could share the code).

Screenshots:
EA 10, default labels positioning: https://drive.google.com/open?id=17nUNiAKespmajNiSPzbaFqd00qPJSCAq
EA 14, default lables positioning (same repo, same diagram, different label positions for connectors with 3 or more bends): https://drive.google.com/open?id=1B7p5H09hGimlWcggLxg04l8rWy72QgDT

EA 10, labels positioned manually: https://drive.google.com/open?id=1BSZXBuRaOdjxB6izuNdu3yqgdfHD-Pv0
EA 14, labels positioned manually (same repo, same diagrame, different label positions for connectors with 3 or more bends): https://drive.google.com/open?id=1gI00j6mIqkVNQNlRysAmFqsZkxBkVFS9

Thanks,
Seweryn

[Mauricio Moya (Arquesoft)]

In my personal opinion, this is a minor issue. Label positions are irrelevant to me in order you always can click the label and it appears a line indicating where the label belongs.

But I know, every environment is different and every users prioritize different things (consistency, look & feel, etc).

So, my suggestion is: install EA 14 only in one PC and try to open some of the diagrams (without modifying or saving). Check if this is a real problem for you, or is not as important as you thought in your particular diagrams.

If the issue is significant, I suggest try to create a script that fix the problem, or fix it manually, diagram by diagram, whenever you need one of those diagrams.

Maybe not the answer you want.

In general, I've evolutioned models since version 9 to current 15, and yes, I remember some diagrams that got weird when changing some version (maybe 10 to 11), but we just fix them manually from time to time.

[seweryn]

Thanks for your insight. Actually we're already doing what you advised -- we copied our repo and we're using EA14 on the copy to see if we have any issues in tasks that we usually do.
Currently we have this label positioning issue which affects ~400 diagrams maintained by our business users.

I just hoped that somebody remembers what other problems occur during migrations from version to version.

Thanks,
Seweryn

[Geert Bellekens]

Thanks, for your insight. We're doing what you advised -- we copied our repo and we're using EA14 on the copy to see if we have any issues in tasks that we usually do.
Currently we have this label positioning issue which affects ~400 diagrams maintained by our business users.

I just hoped that somebody remembers what other problems occur during migrations from version to version.

Thanks,
Seweryn

In general there are very little issues upgrading EA, that is probably why you don't get too many answers here.

Issues I can think of
- difference in sort order when generating XML Schemas
- problems with RTF templates, especially when used with scripts that call the document generator API

The most problematic thing is finding menu options after upgrading since they moved it all around.

Geert

[Mauricio Moya (Arquesoft)]

Another possible issue I remember is the deprecation of some methods in the API. It could affect your scripts or the document template fragments using scripts.

[qwerty]

Another possible issue I remember is the deprecation of some methods in the API. It could affect your scripts or the document template fragments using scripts.

Deprecation? Which? I'm really curious.

q.

[seweryn]

Another possible issue I remember is the deprecation of some methods in the API. It could affect your scripts or the document template fragments using scripts.

We have already migrated and tested our tools which use EA API and fortunately there are not any issues