Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Shegit Brahm

Pages: [1] 2
Hi there,

I try to generate a documentation on package_1 by using virtual documents, see project browser structure:
  • Package_1
    • UC diagram
  • (...)
  • Package_5
    • sub package_5.1
      • sub sub package_x.y.z
        • UC1
          • AD (Composite of UseCase)
            • Activity
              • Action1
              • (...)   
              • Final
              • Initial
        • UC2

  • UC diagram - UC: UC imported as “Link” in diagram
  • UC - AD: AD is composite child diagram of UC, stored in same package as UC
  • AD - AD elements: AD elements have the activity as parent and are stored in same package

There's need to get UC diagram, UCs, AD, activity, action, (…), initial and final included in that documentation.

The first approach to get that done was to use template and fragments. The resulting documentation contains UC diagram, UCs, but neither AD, activity nor anything being a child-child of the UseCase.

So I turned to virtual documents. In order to grab the missing AD and its diagram elements and get them reported, I tried to create a model search applied as tagged values of a model document.

But it turned out that my created model search doesn't work. I think, my approach of implementing a model search into a model document isn't correct.
Beside any general solution to my context I think I need to understand first:
How to use model search in model document?
Where do I have to write what? The modal search as a query is a custom sql of a fragment within the template that is chosen for the modal document?

I was unable to use the help in to get a working virtual document that uses a modal search. The semi-automated approach published there by Geert is not “copyable” for me because I need to start on a package, not a diagram.


PS: If you prefer to revitalize the old thread as it seems to be the topic: short notice and I will to so.

General Board / How to create / design completely new elements for EA?
« on: February 09, 2018, 01:12:42 am »

in my understanding there is a vast variety of toolset available for EA.
OMG modeling like UML, SPEM, SoaML, BPMN and others like ICONIX, DatabaseModeling, Win32 User Interface, NIEM.
These come with there own element description the EA can work with.

I already configured UML profiles and created toolboxes, providing them via MDG Technology.

How to create something "new" that is not derived from existing models?

Own elements with there own shape and stuff.

The problem I want to solve?
Well there is an new interface description in research and I'd like to model with it.
Right now I would use an UML Profile which comes up with stereotypes and stuff, but it is not "right" as it is yet not based on the UML.


Hi there,

I'm writing template fragments and need to play around with the SQL queries as I'm not that familiar with it.

Now it happens that I get more or less useful error messages from EA and I wonder: which way could I use to debug a template fragment?

I tried to create a search first and use it. It seems that it's not always possible - should it be?
(like usage both of #PACKAGEID# and #OBJECTID# inside a query)

Even if I don't get an error, the fragment does nothing because my query didn't deliver anything - so I need to evaluate why.


Hi there,

I have following situation:
I'd like to use as much onboard mechanics as possible to create a customized PDF of a package's content.

EA has build in the way: F8 on a package and selecting some templates (front, toc, main) and set some options and ... voila, a PDF is generated.

What I think I don't want: write my own addin. Because the more "wysiwyg" is visible via template and the less code, the better for maintenance by other people (I suppose).

The tricky part already started that the achieved PDF is that individual, that I start with a template, go over to a fragment with TemplateSelector and run specific fragments.

In my attempts I figured out that a TemplateSelector can only decide by element type and a sql query misses something like "if then else". Because I would need for each table a fragment - otherwise the tables got mixed up.

So I'd like to point the template to a JScript-fragment which should point to a fragment again. (JScript instead VBScript by flip of a coin)
Because I want to decide e.g. on element's colour which I cannot so far by using a template selector.

My questions:
- Is that possible, to go from a template to JScript then to a fragment and having everything inside the PDF which is created by the template in the first place?
- Where can I read about it?

I'm able to pass the object id and package id from template to JScript  - main(#OBJECTID#, #PACKAGEID#) - and create a separate document (Class EA.DocumentGenerator).
I just tried to read through EA pages and examples and don't know which keywords I need to look for.

Thanks, Shegit


I was working on a costumers notebook with EA and one day I was told that my EA version / build does not fit the requirements to gain a license.

Support just installed the newest version and everything was fine.

Now I want to know: as for my own company - do "I" as the license server owner configure it that way? Or does it come together with bought (corporate, floating) licenses as a default feature?
I didn't find any answer on sparx or google.

In earlier scenarios a file based keystore allowed EA 7 as well as  and EA 9 and EA 11.

So who decides which version I need to have in a floating license environment? Sparx or the company?


Hi there,

I have a question about documenation generation:

I have a package and there a diagram that contains some requirements. These requirements are linked to several use cases.

I want to generate a document that lists me the package with the diagram and afterwards each requirement with description and a table with use case to which this requirement is linked (source-target relationship is shown in relationships window).

circumstances: the requirements and the use cases are located inside project browser somewhere else, they are not stored inside the package of the diagram.

from section package I chose:
- package
-- package element
--- external requirements
--- tagged value
-- child packages
-- diagram
--- element
--- connector
-- element
--- extension points
--- tagged value
--- connector
---- source
----- element
----- linked feature
--- attribute
--- child elements
-- connector
--- source
---- element
---- linked feature
--- target
---- element
---- linked feature

so the template looks like:
Code: [Select]


package >

package element >
external requirements >
< external requirements
tagged value >
Member Company- department
{ElementTagVal.Value} {ElementTagVal.Notes}

< tagged value

< package element

child packages >
< child packages

diagram >

image {Diagram.Figure}: {Diagram.Name}
element >
state: {Element.Status}    release: {Element.Phase}  version: {Element.Version}  modified: {Element.DateModified}
author: {Element.Author}


Type Name Version Release
{Element.IsSpec} {Element.IsLeaf} {Element.Owner} {Element.Phase}
< element
connector >
< connector
< diagram

element >
extension points >
< extension points
tagged value >

< tagged value
connector >
source >
element >
< element
linked feature >
[Package/Element/Connector/Source/Linked Feature]
Linked Feature
< linked feature
< source
< connector
attribute >
< attribute

child elements >
< child elements
< element

connector >
source >
element >
Connector/Source/Element - Type:

Connector/Source/Element - Name:

Connector/Source/Element - Notes:
< element
linked feature >
Connector/Source/LinkedFeature - Stereotype:
< linked feature
< source

target >
element >
Connector / Target / Element - Type:

Connector / Target / Element - Name (full):

Connector / Target / Element - Notes:
< element
linked feature >
Connector / Target / Linked Feature - Type:

Connector / Target / Linked Feature - Type:
< linked feature
< target
< connector
< package

property setting for this diagram: "add each contained element in documenation"

After prompt for document generation comes up, I choose "include all diagram elements in report" and set all exclude filters to "none".

What do I miss - in explanation here and in generation there?
Bug, feature, wrong concept of documentation?


PS: If the requirement is stored in the same package as the diagram then it works. But that is not useful as I need seperate packages for documents and for the model itself.

I digged into MDG and created several technology exports.

Now I realize: the dropdown of "open an existing mts file" is filled - and denies any new ones. And the existing ones occur in random order.

My question: how to get rid of these entries?

If I delete one in windows file explorer, EA does (obviuosly) not know and just tells me: oops, this is unknown and has no information stored.
But it persists as dropdown entry.
is quite quiet about.

Thanks, Shegit

Using EA 13.0

If I define a stereotype extending metaclass "ActivityInitial" with some attributes,
create myToolbox with it and export all as MDG,
import it to other eap.

In activity diagram I
- have to drag'n'drop from myToolbox to receive my customization (see,38479.0.html for my observation)
- if I whyever delete any tagged value (originally attributes) from this node, I'm unable to restore them.
- neither sync nor "apply" again works.

Looking for a workaround I tried to define Tagged Values in UML1-style: using "UML Types"

But "AppliesTo" is fully ignored on ActivityInitial:

- e.g. for Decision works fine:

- for ActivitiyInitial doesn't show up:

"AppliesTo=Action" works as well, but not these nodes.

Any ideas how I can workaround this bug set a "model" Tagged Value that only applies to ActivityInitial?

To define a stereotype with specific tagged values for a specific element type I define an UML profile.

Now I'd like to have some tagged values of this stereotype to apply depending to which element type the stereotype was added.

Is that possible?

- ActionTV = my stereotype
- extends Action, ActivityInitial, ActivityFinal, Decision
- has attributes attribute1, attribute2, attribute3, ActionOnly, InitOnly, FinalOnly, DecisionOnly

-> visualization

importing the UML profile (or MDG technology to have toolbox) I want to create (inside activity diagram):
- stereotype "ActionTV":
- an action with tagged values            attribute1, attribute2, attribute3, ActionOnly
- an initial node with tagged values     attribute1, attribute2, attribute3, InitOnly
- an final node with tagged values       attribute1, attribute2, attribute3, FinalOnly
- an decision node with tagged values attribute1, attribute2, attribute3, DecisionOnly

- stereotype "Together"
- an action with tagged values      together1, together2, ActOnly
- an decision with tagged values   together1, together2, DecOnly

Question: is that possible?

The option "first stereotypes from each metaclass, later specialization from these to one stereotype" results in elements, that have all time all tagged values from all classes, just grouped by their original stereotype. And synchronizing one element updates all :-)
Here stereotype "Together" specializes from ActionFirst and DecisionFirst.

-  UML Profile
- Toolbox defintion for profile
- MDG of profile and toolbox
- eap where everything was defined
- picture of profile
- picture of tagged values as result

thanks, Shegit

I created an UML Profile for individual stereotypes and a Toolbox based on that.
- create in ToolboxBase.eap, use in TboxUse.eap

need sync for full definitions from myProfile:
- constraints will be added only after syncing the element (User Guide already says so:

my problem with ActivityInitial:
- creating an element from original UML and adding stereotype myInit does nothing: neither tagged Values nor constraints added. And stereotype is visually wrong: instead of "<<myInit>> it shows <<myProfile::myInit>>
- syncing the stereotype from myToolbox: does nothing
- adding stereotype using drag'n'drop from myToolbox: impossible, creates always new node
- only solution so far: creating ActivityInitial from myToolbox, sync it, re-connecting & transferring everything from now-old node, delete now-old node.

my problem with Decision:
- creating element from original UML: adding stereotype myDec using properties page is impossible, myProfile is not offered for selection
- solution: drag'n'drop from myToolbox, adds everything or create from myToolbox

my problem with CallBehavior:
- defining toolbox needs "special skill": the metaclass is called "BehaviorCall", the toolbox attributes need full qualifier with "myProfileTB::myCallBehavior(UML::BehaviorCall)" (other stereotypes need only myProfileTB::myAction, guess it is because of CB vs BC)
- drag'n'drop from myToolbox on empty activity diagram does nothing
- drag'n'drop from myToolbox on default action does nothing
- creating action from default toolbox, changing kind to CallBehavior, drag'n'drop myCall from myToolbox: I get choice "apply myCall/ add myCall" - but nothing happens.
- only solution: create action from default, change kind to CB, select stereotype in properties

So all in all everywhere a different kind of workaround exists - but is there nothing to achieve a consistent work flow?

files for example:  profile definition as UML profile  entire stuff as MDG technology  toolbox definition as UML profile   eap where MDG is used eap where profiles got defined

Thanks, Shegit

I created UML profiles and usually set all exporting and importing options, including "Element Size".
In detail, I set stereotypes extending several metaclasses.

I use these to ways:
- right click on package and using "Advanced -> Save package as UML profile"
- click on package and then "Layout-> (Diagram) Manage -> Save as Profile" (works only after one diagram was opened in advance but exports entire package)

My question is:
- Where is the "Element size" stored, when I export the UML profile?
- Should I dig into "Shape Script", to ensure any sizing? (Because appearance like "grey merge node" works fine)
- and can this Shape Script be exported together with UML profile or at least MDG, because there is inclusion of "Other -> Scripts"?

In the beginning, I had only one diagram and "accidentially" did diagram export
-> that way "imported" ActivityInitial got the size of the stereotype that defines it in the base eap.
like stated here

is silent about size.

Thanks in advance, Shegit

Base eap to define a UML profile with
- stereotype "myStereo" extending metaclass Action (myStereo1 for only one per attribute, myStereo2 for more than one)
- several attributes for this stereotype
- connector "taggedValue" between metaclass Action, ActivityInitial and Decision
- connector role specified as attributes names intend

exporting as MDG Technology or UML profile

Use eap to have tagged values depending on stereotype
- creating activity diagram with at least one element for each type of metaclass in base eap
- importing MDG Technology/ UML profile
- creating Action "useStereo1" and Action "useStereo2" in Activity diagram
- setting "myStereo1" and "myStereo2" as stereotype for this action.
- defining entries for each tagged value of both actions

what is:
- every tv is limited to only one metaclass

what should:
- every tv is limited to each metaclass as defined in base eap

source of problem:
- generated xml selected one metaclass by random

- editing xml so that 'notes="Type=RefGUID;Metatype=Action,Decision,...;"

With the XML I can achieve almost any limitation.
But that's what the generated xml should do as well.

example files: eap used to define stereotypes with tagged values MDG generated by EA MDG edited to achieve aimed behavior UML profile for single tagged value connectors  UML profile for multiple tagged value connectors diagram RefGUIDs with multiple connectors
(edit: changed dropbox links to start download directly (dl=1) instead opening dropbox page (dl=0))

general discussion took place here:,38459.0.html


I tried to do the following:
- creating a definition eap where I set my UML profile
- creating a usage eap where I will use defined profile
- extending Action with stereotype and attributes so I will have Tagged Values after import of Profile

what works:
- Setting any enum works fine (->"WithEnum")
- defining Memo works only with <memo> as "Initial value" of corresponding attribute (-> "WithMemo")

my problem:
- how to enforce "Integer"?
- how to enforce "RefGUID"?

my workaround:
- creating profile as intended
- exporting as MDG as well
- editing MDG-XML with an editor:
Code: [Select]
<RefData version="1.0" exporter="EA.25">
<DataSet name="Property Types" table="t_propertytypes" filter="Property='#Property#'">
<Column name="Property" value="WithInteger"/>
<Column name="Notes" value="Type=Integer"/>
<Column name="Property" value="WithRefGUID"/>
<Column name="Notes" value="Type=RefGUID;Metatype=Decision;"/>

See files if you like:
(Edit: changed to dropbox)

For Memo I did it that way to, but found out that "initialValue" takes it as well.

I prefer to include the Tag-Definition inside eap because otherwise I need to take care for every change of Profile whil updating mdg-xml.


I have similar problems like these ones:

Here feature has been requested, but I don't see valid fulfilment so far.

As I can say:
current EA 12.1 exports still conflicts with (almost) current HP ALM 12.2

My core question:
EA mistake or HP error?

Whenever I create a sample BPMN in EA and export the model, all I get is
- export as BPMN 2.0 XML
Code: [Select]
<?xml version="1.0" encoding="windows-1252"?>
<bpmn:definitions xmlns:bpmn="" id="EAPK_E444FEBD_8B92_4fe2_87B3_83154728E814" targetNamespace="" xmlns:ssbp="" xmlns:xsi="" xmlns:di="" xmlns:dc="" xmlns:bpmndi="" exporter="Enterprise Architect" exporterVersion="12.1.1224"></bpmn:definitions>
- export as XPDL 2.2
Code: [Select]
<?xml version="1.0" encoding="windows-1252"?>
<Package xmlns="" Id="EAPK_E444FEBD_8B92_4fe2_87B3_83154728E814">
<Created>2016-06-08 09:56:55</Created>

I could export the package with the diagram only and got a bigger export file, but it failed with any of file names .xml, .xmi, xpdl.

I can't upload attachment here directly, can I?


Hi there,

I realized, that EA 12.1 creates a much bigger model output if I use "export to XMI": from 92 MB .eap it builds 280 MB .xml.
Taking old EA 9.x it produces only 110 MB.

Any idea what the reason might be?
Any effects beside bigger size? (I didn't do any kind of file comparison)

I choose XMi 2.1 in both cases, all checked options are same.


Pages: [1] 2