Messages

1

Automation Interface, Add-Ins and Tools / Re: MDG-technology: adding duplicate tags to stereotyped element

« on: July 19, 2017, 12:00:39 am »

Simon, I was just wondering how you had worked around the this behaviour?    Are you using the same workaround as described in Reply #4?

Seeing as the UML profil included in the MDG allow the specification of tags (attributes) with [0..*] multiplicity, surely it should be possible in the GUI to recreate this scenario. Either by allowing the addition of extra tags (as defined by the MDG - not new unknown ones) or having tag values represented by arrays - lists of values.

2

Automation Interface, Add-Ins and Tools / Re: MDG-technology: adding duplicate tags to stereotyped element

« on: May 01, 2017, 04:49:54 pm »

Thanks qwerty, but the issues does not concern showing duplicate tags in general (which has been enabled).

I also sent a message to the Sparx Support Team and got the following response:

"Unfortunately it's not possible to add additional tags which are grouped with the stereotype/MDG Technology tags as you described. This issue has been reported previously by another user also and is logged as a bug to be fixed. We cannot yet say when (in which build) the fix will be implemented."

So, hopefully the bug will be fixed in the near future.

Anna

3

Automation Interface, Add-Ins and Tools / Re: Wrong group type when importing MDG Technology

« on: March 28, 2017, 06:17:46 am »

Ok, point taken. Not all scripts should be distributed as reference data as per default ;-)

However, in my case, I require a small number of user-facing project browser scripts to be made available to the user of the MDG with minimal effort. Ideally, the MDG would support the different types of script groups, but importing the scripts as reference data seemed a fair work-around to make these scripts easily available upon right-click in the project-browser.

4

Automation Interface, Add-Ins and Tools / Re: Wrong group type when importing MDG Technology

« on: March 27, 2017, 11:52:49 pm »

Old post, but if anyone comes across it like I did when trying to find a solution for this problem:

"Script goups are not really supported by MDG", as Hetmut Ortmann states in this thread: http://sparxsystems.com/forums/smf/index.php/topic,4734.msg121728.html#msg121728

He continues "Therfore it's a good idea not to include scripts in your MDG. Export your scripts  as 'Reference Data' and import it in the repositories where you need the scripts and script groups. You have to restart the repository"

5

Automation Interface, Add-Ins and Tools / Re: Tagged Values in Documentation

« on: March 27, 2017, 11:46:10 pm »

Update:

Have now successfully 'hidden' most of my tags without values. For instance, the 'versionInfo' tag:
PkgElement.valueOf(versionInfo).Start{PkgElement.valueOf(versionInfo)}PkgElement.valueOf(versionInfo).End
- oh, and what a shame that the bookmarks aren't shown in the editor - very un-userfriendly ;-)

Have encountered two issues though:
1) If my tag contains a whitespace (ex. label (da)), I cannot created a bookmark for it (it simply won't let me insert it - is there an escape function/joker for whitespaces? - or is there a naming convention (eg. lowerCamelCase) for tag definitions? Haven't yet found it in the UML standard)
2) If my tag has memo as datatype, it's description in Notes will wrongly be used as the 'value field' and thus always be shown.

Instead continuing with the SQL fragment solution, I seem to be getting closer with:
SELECT Property, Value FROM t_objectproperties WHERE Object_ID = #OBJECTID# AND Value NOT NULL AND Value NOT LIKE '<*'

6

Automation Interface, Add-Ins and Tools / Re: Tagged Values in Documentation

« on: March 27, 2017, 06:52:39 pm »

Thanks Geert!
Had actually already (unsuccessfully) attempted to apply bookmarks, but I will delve further into the documentation now :-)
Anna

7

Automation Interface, Add-Ins and Tools / Re: Tagged Values in Documentation

« on: March 24, 2017, 08:54:24 pm »

It seems I require a bit more help ;-)

In the fragment document I now have:

custom >
{TAGName}:{TagVal}
< custom

I have created the beginning of a fragment with the following custom SQL query:

"SELECT TagValue as TagName, Notes as TagVal FROM t_taggedvalue WHERE Notes NOT LIKE '$ea_*'"

but how do I reference the current element and select just those tag/value pairs held by that element? (a join with what? using the #OBJECTID# tag in a where clause?)

Cheers,
Anna

8

Automation Interface, Add-Ins and Tools / Re: Tagged Values in Documentation

« on: March 23, 2017, 08:34:17 pm »

Many thanks, Robert! 
Sounds like a solution which will solve the problem! :-)
Anna

9

Automation Interface, Add-Ins and Tools / Tagged Values in Documentation

« on: March 18, 2017, 01:12:09 am »

I have created a Documentation Template for UML Class Diagrams and have inserted tagged values in my RTF:

{ElementTagVal.Name}:{ElementTagVal.Value}

However, a number of tags are defined in an MDG, and for each element only SOME tags will be populated with values.

Is it possible to include a condition that checks if a tag has a value and if it is null, then the tag is not printed?

Thanks
Anna

10

Automation Interface, Add-Ins and Tools / MDG-technology: adding duplicate tags to stereotyped element

« on: February 02, 2017, 01:04:03 am »

Colleguages and I have created an MDG-technology for modelling using Logical UML Class Diagrams in EA as a base.

One of our issues concerns adding and displaying tags relevant to a specific stereotype described by the profile definition embedded in the MDG technology.

By stereotyping the metaclass Class, we have added a number of custom tagged values, and now we have a new custom tagged value pane next to the standard 'tags' pane.

This works ok.

However, we require the technology to allow the addition of multiple tags with duplicate tag names. So, aside from filling in the predefined tags, it should be possible to add a new tag-value pair. We have tried using the UML-types to present a list of possible tag names (which naturally correspond with the tag names in the custom profile, however, the new tag-value pair appears not to be listed under the grouping containing the other tags specified by the MDG-technology.

In short, how can we allow the addition of duplicate tags in accordance with our MDG?

Thanks
Anna