Author Topic: RefGUID Tag behaviour different for profile vs UML Types  (Read 1365 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8548
  • Karma: +253/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
RefGUID Tag behaviour different for profile vs UML Types
« on: February 06, 2020, 12:20:55 pm »
We have defined a RefGUID Tag thus:
JurisdictionalLocationReference
Code: [Select]
Type=RefGUID;
Values=Class;
Stereotypes=Cntry;
Default={4D8BF378-485E-442f-BDB7-AADC6AF007FB} ;«Uninitialized»

We then use this definition in our MDG thus:
Code: [Select]
<Tag name="JurisdictionalLocationReference"  default="{4D8BF378-485E-442f-BDB7-AADC6AF007FB}"/> <!-- "«Uninitialized»" -->
As will be seen, we don't specify the type of the JurisdictionalLocationReference tag in the MDG.

If we create an object of the appropriate metatype from the toolbox, all is fine and the RefGUID returns the target value.

However, if we add the JurisdictionalLocationReference to another item (from UML types), we just get what seems to be a "string" with the value of the GUID clearly visible.  Once you change the value (via the [...] builder button) you get the appropriate dialog and thence all is as one would expect.

Reported,
Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8017
  • Karma: +118/-20
    • View Profile
Re: RefGUID Tag behaviour different for profile vs UML Types
« Reply #1 on: February 06, 2020, 01:37:53 pm »
Your tagged value definition has a tab as part of the default value which is breaking it. (Because the default isn't a guid)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8548
  • Karma: +253/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: RefGUID Tag behaviour different for profile vs UML Types
« Reply #2 on: February 06, 2020, 04:51:16 pm »
Your tagged value definition has a tab as part of the default value which is breaking it. (Because the default isn't a guid)
Sure does!  My bad!   :-[  Typo and "Snow Blindness"!  All good now!

Thanks,
Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!