Author Topic: tagged value of type memo?  (Read 15090 times)

Patrick Julian

  • EA User
  • **
  • Posts: 51
  • Karma: +0/-0
    • View Profile
Re: tagged value of type memo?
« Reply #15 on: March 25, 2013, 10:52:28 pm »
I dropped a feature request at Sparx' asking for an integration of the memo type to the dropdown.

KP

  • EA Administrator
  • EA Expert
  • *****
  • Posts: 2919
  • Karma: +54/-3
    • View Profile
Re: tagged value of type memo?
« Reply #16 on: March 26, 2013, 09:13:11 am »
The full answer (how to create a memo-type tagged value in a profile) is:

1. Create a tagged value type in Settings > UML Types > Tagged Value Types. Tag Name is the name of the tagged value you want to create and Detail contains "Type=Memo;"

2. Create your profile giving your stereotype class an attribute with the name (and type?) set to the name of the tagged value type created in 1.

3. Generate an MDG Technology including the profile created in 2 and the tagged value type created in 1. The technology must have exactly the same name (case-sensitive) as the profile for this to work.

The other steps are as expected...
« Last Edit: March 26, 2013, 09:14:25 am by KP »
The Sparx Team
[email protected]

philchudley

  • EA User
  • **
  • Posts: 744
  • Karma: +21/-0
  • EA Consultant / Trainer - Sparx Europe
    • View Profile
Re: tagged value of type memo?
« Reply #17 on: March 26, 2013, 08:10:35 pm »
A million thanks, it now works!!

The key to success was the all important step 3 (highlighted) which I had overlooked, renamed the MDG to agree with the profile and hey presto, everything works including one of my favourite tagged value types DateTime

The step which is vital is

[highlight]The technology must have exactly the same name (case-sensitive) as the profile for this to work.[/highlight]

Thanks again

Phil
Models are great!
Correct models are even greater!

Robert Sheridan

  • EA User
  • **
  • Posts: 105
  • Karma: +0/-0
    • View Profile
Re: tagged value of type memo?
« Reply #18 on: March 27, 2013, 08:54:54 pm »
I found that using <memo> in the tagged value of the stereotype meant that I did not have to set up a tagged value type via UML types which meant that the profile was portable (important if the users will be creating their own repositories and are not technically savvy).  The downside is that the 'details' of a new element created using the stereotype contains '<memo>' etc. as the default value; the only work around to this I have found is that if you are doing an import via the automation interface you can add a step to check for and delete the default value if the details field should be empty.