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.

Messages - Polymorph

Pages: [1] 2 3 ... 9
Uml Process / Cross references in embedded RTF documents
« on: October 30, 2018, 08:03:18 pm »
We are all familiar with being able to create a caption within an MS Word document (e.g. Figure 1) and then cross referring to that caption from somewhere else within the document.

Does anyone know how this can be achieved within an RTF document written within EA?


Hi everyone

I want to prevent any structural features that I add to a block/class from being automatically added to any existing diagrams by default...

For example, on let's say I have a BDD called "My System Diagram"and onto this I place two blocks: "My System" which connects (via reference association) to "Another System". Neither of these blocks own any structural features such as ports or part properties at the time the diagram was created.

Now, assume I create a new diagram (perhaps in a later development phase) and I add a new block, called "My Subsystem" and then create a compositional relationship from this new block back to the "My System" block. This causes EA to create a Part Property on "My Block" (this is good!). I then do some more work and I add a port to both "My System" and "Another System".

Now, I return to the BDD diagram that I created earlier and I see that EA has added these structural features to the blocks inside their respective compartments. This causes the elements on the diagram to resize and messes up the look of the diagram (this is bad!).

Does anyone know how to stop EA from doing this by default?

The only way I have found is to create a diagram in a "Template" package, on which EA bases all future diagrams. I can use this template to turn off all of the various structural display elements - but the problem is that I have hundreds of diagrams that were created before the template diagram was created. This means that my old diagrams are not affected by the template!

Please say I don't have do go back and manually change them all!!

Note: "locking" the diagram does not help - that only stops people from dragging elements around and/or manually resizing them

Automation Interface, Add-Ins and Tools / Discussions and Reviews
« on: November 30, 2017, 11:25:33 pm »

EA recently introduced a new "Reviews and Discussions" feature which we are trialling at the moment.

Does anyone know where in the database these discussions get stored? I want to extract them out to a Word document


Excellent - Hidden Text Works fine for me. Thanks everyone!

I think that comment feature only works when editing Rich Text Document Artefacts, not templates...?

I must be doing something wrong... the Apply Comment text is greyed out. This applies when I select any of the text on the template. Is this setting controlled by access permissions?

    You can obtain more control over the documents you produce by creating virtual documents:

Let's suppose you want to generate documentation from each of the sub-packages in your project:

My Root Package (the package that you are using to group sub-packages, but one that you DON'T want to include the name of in your report)
 - Sub Package 1 (you want this to be Section 1)
 - Sub Package 2 (you want this to be section 2)
 - Sub Package 3 (you want this to be section 3)
      -Sub-Sub Package A (you want this to be section 3.1)

  • Create a Model Document model element and add it to a diagram (
  • Drag Sub-Package 1 from the project browser onto the model document - this will create an attribute that points to Sub-package 1
  • Repeat for other sub-packages you wish to include
  • Open the tag value window to view the tagged values for the Model Document and select the appropriate template (this is where you will specify the outline level of the package name)
  • With the model document selected, press F8 to open the document generator window and press generate

EA will now process each of the sub-packages that are referenced in the model document's attributes. The root package will be omitted.

I hope that makes sense. If not, I'll try to explain further...[/list]

Does anyone know if it is possible to add comments to document templates to help others understand what the template is doing?

Basically, I want a way to add text to the template that will not be exported into the final document...


Automation Interface, Add-Ins and Tools / Re: Understanding OCL
« on: May 26, 2017, 12:11:37 am »
So, if I want to add checks to my MDG that ensure that when I create a model element it has the correct types of relationship to other model elements (for example) how can I do it? Are we talking about scripts?

Automation Interface, Add-Ins and Tools / Understanding OCL
« on: May 25, 2017, 08:13:22 pm »
I'm interesting in writing OCL expressions to help me apply my own model validation rules to my custom MDG Technology...

Can anyone recommend any good resources to help me get started? I have found a few generic tutorials on OCL on the web which explain the syntax. But I am not really sure how I actually use them in EA. Does anyone know of any tutorials that show how it can be used?


I went for the stereotype option. A good balance between simplicity and functionality

Thanks guys

Why on Earth isn't this something EA supports?!? Seriously, who wants a JPEG of a relationship matrix!!

Uml Process / Re: Matrix Specifications & Searches
« on: March 09, 2017, 10:20:04 am »
I can't see any link to a form?!? ???

Uml Process / Re: Matrix Specifications & Searches
« on: March 03, 2017, 08:52:51 pm »

Matrix specifications currently only allow source and target packages to be specified. The ability to also define source and target searches would allow more control over relationship matrices

See original thread:,37982.0.html

Pages: [1] 2 3 ... 9