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

Pages: [1] 2 3 ... 6
General Board / Re: Documentation with elements and attributes from diagram
« on: September 07, 2018, 11:28:14 pm »
WRT to my 'hijack' request, the first part anyway ...

I have a similar need - to create diagram / view based (rich text) documents that pull element details from wherever the elements are, i.e. a document based on a diagram and the elements on that diagram *not* based on a package.  I can't find any examples of that but I'm sure there must be a way.

The advice above gives me part of what I'm looking for - I can now generate a document and include elements from outside the package the diagram is in (and with filtering I can control which of those I include) :-)

But, is there a way to limit the scope of the document to the currently selected diagram ?
If the diagram is in it's own package I get what I'm after, however if I move it into a shared package the document includes all diagrams within that package.

So, specifically, what controls the 'scope' field - the first field of the Generate Documentation dialog?
- If I choose a package that field name is Package and I can select any package I want; the document is generated based on the full package
- If I choose an element on a diagram or in the browser, that field name is Element and has the name of the currently selected Element; the document is generate on the element only
- If I choose a diagram (click on the diagram itself or select on the browser) then the selection changes to Package when choose Generate rich Text Document and does the whole package not just the diagram

If you need to exclude a diagram from your reports, check the box "Exclude image from documentation" in the Diagram Properties.

Another way is to place diagrams that wil always be in- or excluded in a report together in their own package.
To create flexible reports, what you need is a "virtual document", this is created with Model documents and possibly Master documents to assemble multiple Model documents in one document. Begin wit a Model document and drag Packages into it. This gives you complete control over which packages to include in your report. The template to use is selected via a tag in the Model Document properties. When using Master documents, that have multiple Model documents, you can have a report using multiple templates by using a different template in each Model document.

The documentation options in EA are many and it takes some time and experimentation to use them comfortably but you can create large good looking reports with it.

General Board / Re: How to limit Search to one package?
« on: September 03, 2018, 09:59:00 pm »
When you edit the Search, click on the button "Search Options" (the button with a checkbox list icon) and then select "Return matching items for the selected package"

But how to do this with a custom SQL search query? It seems the Search Options button is not available there....
Perhaps include the package limitation in the SQL query then, but can this be done recursively? Including all subpackages?

General Board / Re: Documentation with elements and attributes from diagram
« on: September 03, 2018, 09:42:16 pm »
Thanks so much for the answers!

@Geert Bellekens I love the SQL feature but I couldn't quite come up with a solution that looked good in the document and i'm not very good at scripting so that's is a bit out of my league.

@michielper That is excally what I was after! I'm still not quite sure about the logic behind it though, leaving Diagram> Element empty seems weird to me. But hey, as long as it works I can let that one slide for now.

Again, thanks so much for the help!


The empty element clause in the diagram section is a bit weird (and badly documented) indeed but it sort of indicates that you want the elements but postpone the details. Compare it to the declaration of only an interface in a programming language where the specification of the function is in another place. I do wonder why Geert did not give this example.


I'm using version 14.0 and I want to generate a document that takes the elements from a certain diagram along with the attributes of thoes elements with the end result looking something like this:

Element name X
Attribute name   Attribute value
Name x              Value y
Name z              Value n

Element name Y
Attribute name   Attribute value
Name x              Value y
Name z              Value n

From what I can see the template builder only lets me choose element attributes from elements that are located in the same package as the diagram.
I've tried using the element tag under Diagram but that don't seem to work as it always comes up blank, and even if it did work it would only give me the name of the element, not its attributes.

It's not an option to move all elements into the same package.

Do anyone have a solution for this?

Thanks! /Joel

It is possible to include elements outside of the current package. E.g. with this template. This template only includes name and notes of the elements but you should be able to include any attributes. The trick is to have an empty element clause in the diagram section and a filled one in the packake section. Dont forget to check the box "Include all diagram elements in report" in the Generate Document dialog. And set any other options and filters.....

package >
diagram >
Elements in diagram {Diagram.Name}:
element >
< element
< diagram
child packages >
< child packages
element >
{Element.Name} ({Element.Type}) {Element.Notes}
child elements >
< child elements
< element
< package

General Board / Re: Example of Custom SQL template fragment
« on: August 31, 2018, 11:35:21 pm »
MDG is a way to bundle things such as templates, scripts, profiles etc... as an excel file.

Most modelling languages in EA are distributed as an MDG.

The .eap file already has the MDG imported, so you should find the template I mentioned there.


Ok, I see. However, in the fragments there is no substantial custom SQL. Only in BFR_ElementDiagramFragment there is one line: MyRtfData(#OBJECTID#)

General Board / Re: Example of Custom SQL template fragment
« on: August 31, 2018, 09:45:44 pm »

Check out
In the MDG that you can download, you'll find the template UCD_Linked Requirements as an example of an SQL fragment template.


Thanks for the quick assistance! I downloaded an EAP and an XML file. What does the MDG mean?

General Board / Example of Custom SQL template fragment
« on: August 31, 2018, 09:16:04 pm »
I am trying to create a custom SQL template fragment to be included in a report template. The purpose of the fragment is to show dependency sequences of a certain length starting from the current element. The query works fine as a custom search but I get stuck in trying to get any result at all from the fragment when I make a template fragment out of it. So I would like to see an example of a working custom SQL fragment and the report template that includes it.

Thanks for any help!

General Board / Re: show connectivity/dependency chain
« on: August 30, 2018, 07:39:39 pm »
I've create a number of specific searches and excel export scripts to get this type of information.

I'm not aware of a generic solution, and frankly, I'm not sure if such a generic solution would even be possible (as in, is less complicated then writing your own query/script from scratch)


Alright, so can you lift a tip of the veil on how to do this, where to start? Template fragments?

General Board / show connectivity/dependency chain
« on: August 30, 2018, 06:39:33 pm »
An interesting piece of information that is hidden in an architecture repository are the connectivity and dependency chains between components. These are the answers to questions like: "via which other components and connectors is application A connected to application B". Perhaps narrowed down to certain connector types or component types.

As far as I can see, this type of query/report is not supported out of the box in EA but it should be possible to create it, perhaps by using SQL and/or template fragments.... My question is, has anyone thought about this and created a solution?

Thanks in advance!

General Board / Re: Time traveling in EA
« on: August 08, 2018, 12:34:26 am »
see here:

and here:

Ok, not completely intuitive to get it to work; you have to clone the package first and then all the elements in the diagram together. And then you end up with multiple copies of basically the same objects which may or may not be a problem.

General Board / Re: Time traveling in EA
« on: August 07, 2018, 11:00:18 pm »
Hi Michielper,
I thing the EA answer to your question is the Time Aware Modelling.
However it clones elements and I have the feeling that it causes more problems than solving problems.

I remembered, that I have posted something about that as well you can find here:,39672.msg244604.html#msg244604

However to get such a feature, is not very realistic.

Your idea is good. But where can I find more on Time Aware Modelling?

General Board / Time traveling in EA
« on: August 06, 2018, 06:00:07 pm »
Time traveling is showing a series of views each representing a different lifecycle stage of a system (part of an application landscape).
This can be clearly very useful but is not explicitly supported by EA.

So how can we do this?
One obvious way would be to create new instances for every element for each of the lifecycle stages to show. That has the obvious disadvantage of ending up with many instances of essentially the same element that must be kept in sync. Making all instances inherit from a base instance looks like a possible approach. However, inheritance cannot (i think) be so fine tuned as to exactly specify which aspects of an element are inherited and which are not. Specifically, you want the connectors between elements be different in the different stages. Connectors are not first-class citizens in EA but are part of the Elements so different connectivity requires different elements :-(.

Has anyone else thought about this and created a feasible solution?

Thanks Geert!

We use a word macro to
- shrink the images to the correct size so the title
- set certain styles "keep with next"

Yes, that seems like a work around. It is definitely a bug in EA though. Any chance of sharing that macro code?

I am generating documents with diagrams in EA version 13. Package names are the paragraph headings in my document.
When a package contains a diagram that is not too large, I want the package name (paragraph header) to be on the same page as the diagram and not have a paragraph name followed by a large empty space.
So, I tried the "keep with next" option in my template. When opening the generated document in Word, however, the paragraph heading is NOT marked as "keep with next" and the paragraph heading is attached to the preceding text, is followed by a large empty space and the diagram is on the next page. Not what I want...
I also tried "keep together" but this neither works.

Has anyone else experienced the same problem and perhaps found a solution?

Pages: [1] 2 3 ... 6