There is no DB to GUI translation possible with EA. You will always see what is in the DB, also for dropdown. However, for dropdowns, a user does not need to type the long string but rather select it.
That's not entirely true. Translated versions of EA can and do display a different value from the one saved into the database.
? How is this done/look like?
@Paolo: Interesting. That one slipped my mind (or maybe it was introduced only recently?).
I'm gonna take a wild stab in the dark and say it's hard-coded and only applies to Sparx. I've never seen any documentation outlining how to achieve this in a custom technology. (And I have looked.)
Going back to the OP, there is to my knowledge no way of showing something other than what's in the database in the properties dialog/window (pending clarification from Eve, although that would of course be outside my knowledge so my point stands).
You can have a tagged value stored in the database and show something different
in diagrams using a shape script. But it's feasible only for limited enum tags, and since you can't control the display of those same tagged values in the properties dialog/window, this sort of behaviour will tend to confuse the user.
It is also quite possible to replace tagged values in generated documents if you use either a document generation script, or SQL / script template fragments. But again, very likely not worth the effort.
Paolo's suggestion I read as a - uh, suggestion. I don't think it actually exists.
But it's not a bad one, and in the profile model it could be implemented as an initial value on the enum literal.
But if the functionality already exists to intercept the tagged value data coming from (and going to!) the database, all that's needed is for Sparx to enlighten us as to how to access it in a custom technology.
/U
