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 - kepNCI

Pages: 1 2 3 [4]
Automation Interface, Add-Ins and Tools / Custom UI Toolbox
« on: September 08, 2012, 01:15:45 am »
I would like to create a toolbox for my MDG that contains UI elements. I am having trouble getting started. I assume I must start with a metaclass and select GUIElement, but I do not know how to set up the associated stereotypes for each UI elelment, including redefining existing UI elelments in simple or win32 toolboxes  So.....  
1)  How can I include existing elements that are included in three other UI toolboxes into my custom toolbox?
2) What is the best way to create custom (company-specific) UI elements which can display differently depending upon tagged values (like many of the elements in the simple UI toolset do).  


When using the icon attribute to assign a 16x16 image for either a custom toolbox or the project browser, you must enter the full path of the image file as the string value of the stereotypte's icon" attribute. I assume the image is then embedded in the resulting xml.

Is there a way to reference an image in the EA Image Manager instead of a file for the icon attribute?  
If so, would the image still be embedded in the resutling xml?


In MDG, i have an enumeration list. I then have an attribute of a stereoype set to the enumeration list.  All is well on that th lst becomes the option in the sttribute's dropdown.

Is there a way to allow the dropdown so that the selection is not required to be in the list?  (I am guessing no)  

The use of alternate images seems to get posted once a year, at least. I am new to EA within the year and wanted to use alternate images for stereotyped within an MDG as well as on elemeents on diagrams within a model template referenced within the MDG MTS file.  I initially could not get either to work.  Here is what I know so far.

Alternate Images of stereotypes within MDG Profile:
Does not currently work. This is a known bug that EA says will be fixed in some future build. During the interim EA Support recommended to use shape scripts by adding an "_image" attribute to the stereotype and selecting the browse button [...] on the" Initial Value:" field to open the shape script editor and apply script. Ensure the fully qualified name of the image begins with the technology id followed with image name.
Example Script

shape main

shape name
This does work, that is, when one drops the stereotype element from a toolbox onto a diagram, the image is displayed. Unfortunately one looses the capability to set feature visibility.  In my case I wanted to display the alternate image AND the tagged values on the diagram. For me, displaying the tagged values on some diagrams was more important, so I chose not to use the share script and hope that EA soon fixes the alternate image functionality.

Alternate images within model template diagrams.
Initial problem:
In my model template EAP project I use an alternate image on a
boundary element in a diagram (used to display compnay logo on several
"home page" diagrams). The package is exported as an XML file, which is
referenced in my MTS Control file as the model template. When generating the MDG file, I also select the image file as one of the images to include in the technology. The generated MDG XML file is referenced via the Settings/MDG Technologies/Advanced method. When  I create a new project or add a new package using the generated MDG technology, all the packages/diagrams are correctly created, however any element/stereotype that was associated with an alternate image
reverts back to the original image and properties. However, if I import
the same XML file, the alternate image is correctly displayed, thus
leading me to believe the problem is not with the generated XML, but
with the MDG technology usage.

I was able to get this to work if:
1) I selected an image that was NOT imported via MDG.
2) When exporting package to XML, used UML 2.3 (XMI 2.1) and checked the option to same alternate images.

Hope this helps.


In my MDG profile I have an existing stereotype extened form a node. I added a new attribute to the stereotype and generated a new MDG.

What is the best way to update existing elements in porjects that were created with that stereotype so that they also include the new attritue?

Is the process any different if instead of add a new attribute, you changed the name of an existing attribute?

In my MDG profile folder I have metaclass for Node where I extend stereotypes for various network devices such as router, patchpanel, switch, server, etc as well as a metaclass for port where I extend a port stereotype.  I then have created a toolbox and a diagram for network design which reference the defined network  stereotypes. All is working fine.  For example, I can select a PatchPanel device from the network design toolbox and drop in onto s network diagram.

Now I would like to define a specific model in my MDG profile under the a node which would already have the number of ports configured. For example, I was hoping that I could use the network design toolbox to select a patch panel that when puilled onto the diagram would already have all of the ports configured. Can I do that?

This is what I tried to do, but it does not work.
In my MDG profile, I created a stereotype called PatchPanel12 to which I configured 12 ports to it and then connected it to the PatchPanel stereotype as a Generalization.
The PatchPanel12 does appear in my toolbox, but selected and dropped into a diagram, the ports are not there. (FYI: It does pickup the attributes from the parent PatchPanel stereotype)

Automation Interface, Add-Ins and Tools / Stereotype background color
« on: April 26, 2012, 01:16:33 am »
I think I must have been dreaming. In my MDG model I had 3 stereotype elements extended from the same metaclass element. I gave the background a different color for each stereotype. When using the model to create a new element on a diagram, the element would have the background color of the profile's stereotype.

I thought that was all I needed to do, but now the profile xml is not picking up my background color (or font color), but instead setting it to the defaults, so now when I create a new element from any of the 3 stereotypes, they all look the same, even though when I saved the profile XML, I have the color and appearance checked.

Seems the only way to get it to work is on my stereotype in myprofile I must now set the background via the Appearance/Default Appearance.

Was it always this way?

(not sure if this had anything to do with it, but seems I had to use the Appearace/Default Appearance option after using a _metatype attribute in the stereotype. I think that may be just a coincidence.)

In my MDG profile I have defined a stereotype to which I have assigned attributes. The attributes are arranged in a specific order. The defined stereotype is then used in a toolbox for the MDG.

However in a diagram using the MGD technology, when I drag the element from the toolbox, the order of the MDG's tagged values are always alphabetical by name. Likewise when I create an RTF template to display the tagged values, they are displayed in alphabetical order.

Is there a way to maintain the order of the tagged values as defined in the profile stereotype? If not, then what is the purpose of having the order in the stereotype attribute definition?


Automation Interface, Add-Ins and Tools / Losing aternate image in MDG
« on: February 23, 2012, 06:09:31 am »
Having a problem with images in a diagram from a user defined MDG technology.

When I create a new project via the user defined MDG technology, any elements with alternate images are not displaying the images, even though the images are in the new project's image manager.

We are running EA 9.2. I searched forum topics within the last year and there is one thread that was similar, but apparently is slightly different.

Here is my scenario:
The user MDG Tech file is generated from 3 saved xml profiles whose source are 3 packages within an EAP profile project. The 3 packages are:
- profile (defines 2 stereotypes for requirements with tagged values and an alternate image)
- toolbox (creates a toolbox which includes the new requirement stereotypes)
- diagram (defines a requirements diagram that uses the new toolbox)
This profile EAP file also includes custom images in its image manager that are selected to be included when generating the MDG file as well as RTF document template. I use an MTS control file.

I also have another EAP project that provides the company's model template for its project management process (PMP). The model defines the PMP's 6 phases as packages under a parent package. Each phase includes a documentation diagram which includes a company logo image inserted as an alternate image to a boundary element. The parent package is then exported as an XML file and is then referenced in the generated MTS file as a model template.

The MDG generation appears to be working OK. For example when a new project is created with the user MDG technology plus it has the entire PMP package and associated model diagrams. I can also see the MDG images in the image manager and the RTF templates under Resources.

Problem is that any elements in the diagrams which were defined with alternate images are no longer associated to the image, that is, the corporate logo in the boundary element is now blank and the requirements stereotype is back to the default image. In the case of the boundary element, I am able to re-establish an alternate image, but for the requirements stereotype, it is not an option.

What am I doing wrong that is causing the MDG technology to lose the alternate image linkage?


I have created an MDG technology guided for our requirements collections/tracking. I am having difficulty in creating a custom diagram. I think I am following the directions as documented in "Create Custom Diagram Profiles", but I must be missing something.

In the MDG profile I have defined two stereotypes that extends a Requirements <<metaclass>> element. One is for user requirements and the other for functional requiremetns. Each have defined company-specific attributes.

In the Toolbox profile, I have one metaclass for a toolbox, named "ToolBoxPage" and then one stereotype extended that includes attribute that link to the two custom requirement stereotypes in the MDG profile.

When I generate the MDG Technology file, using an MTS control file. The technology and toolbox are being created sucessfully.

I am now trying to create an associated Custom Diagram for requirements which would use my customized toolset. The "customized" diagram is being generated in the MDG Technology and is selectable in the "Add Diagram" dialog under my technology. Problem is that when added as a new diagram, it is a normal class diagram with the "Profile" toolbox.  

So far, I cannot figure out what I am doing wrong. Here are the steps I did:
Step 1) Created a diagram profile name. Profile name, Package and diagram all have the same name as the MDG profile name, package and diagram, which is the value used as ID when creating the MDG technology.
Step 2) the <<stereotype>> class element, has no attributes. Not sure if this is required, but the Name of the elelment = the same value as used in the <<meteclass>> attribute, DiagramID (see step 3)
Step 3) the <<metaclass>> class element has a name of "Diagram_Custom" with attributes:
  Alias :string="Company User Requirements"
  DiagramID :string="CompUserReqmtDiagram"
  Toolbox :string=the value of the MDG Techmology ID
       (same as diagram profile name, package and diagram name).
Step 7: Saved the diagram as a profile and generated the MDG XML.

Not sure, I think I am getting something wrong when making the association to the built-in diagram type.

During step 3, I used a name = "Diagram_Custom" for requirements (based upon "Built-In Diagram Types" help. Since that did not seem to work, I tried using a name based upon the built-in types as documented in "Defining Child Diagram Types, that is, "Extended::Requirements". That did not appear to work either, so I tried to add an attribute:
_defaultDiagramType :string=Extended::Requirements
that did no work either.  
So I am out of ideas.

Any suggestions?


Are there two different sets of built-in diagram types? or is the documentation wrong in either "Built-in Diagram Types" or "Defining Child Diagram Types"?

I imported an MDG model (used the TigerTeam XML for this test). While the model is displayed under Settings--> MDG Technologies and its associated toolbox in the Toolbox-->More Tools, I do not see it as a choice when initially creating a new project or when adding a new model via wizard. I tried multiple methods of importing the MDG XML file, that is used  Tools --> MDG Technology Import and tried adding path to file in Settings--> MDG Technologies --> Advance). Both methods deployed the technology under Manage Technologies, but not in the model wizard.

How do I have an MDG model/diagrams included in the model wizard's selection of technologies?

Pages: 1 2 3 [4]