Messages

1

General Board / Re: Exported diagram has empty space

« on: January 16, 2023, 10:57:56 pm »

A similar thing happens when you show a diagram embedded in another diagram (the workaround to allow the same element to be shown twice on the same diagram). The diagram editor won't allow you to shrink the diagram, leaving a lot of white space in the embedded diagram.

For this scenario, there is a workaround.

The diagram becomes small when you do the following:
1) Open diagram properties
2) Select "Connectors" tab
3) Uncheck "Show Stereotypes Labels"

For some reason the system thinks it needs to reserve space for these labels, even when these are not rendered!

I assume the same logic is used for calculating the diagram size when generating the diagram in document.

2

Bugs and Issues / Reporting a state transition list

« on: September 21, 2011, 06:50:05 pm »

I'm trying to report a state transition list from a state transition model, but failed to do so far.

Steps I've done:
- start with empty EA database
- I created a simple state diagram (state objects connected with transition connectors)
- Then I created the following RTF report definition using as a base template None:
[highlight]package >[/highlight]
[highlight]connector >[/highlight]
{Connector.Type}:
[highlight]source >[/highlight]
[highlight]element >[/highlight]
From: {Element.Name}
[highlight]< element[/highlight]
[highlight]< source[/highlight]
[highlight]target >[/highlight]
[highlight]element >[/highlight]
To: {Element.Name}
[highlight]< element[/highlight]
[highlight]< target[/highlight]
[highlight]< connector[/highlight]
[highlight]< package[/highlight]
- Then selecting the package that has the state transition and hit F8: create a report using the template.
- Result: empty report.....

Apparently I'm missing something. Can anyone add some hints to get my report to work? Even, the trivial one?

Version info: EA 9.0 build 906
If needed, the EA database I used for this sample can be provided.

3

Bugs and Issues / Re: RTF document based on Search with SQL fails

« on: July 13, 2011, 04:56:14 pm »

 :-? Very unlogical, but it works....

4

Bugs and Issues / RTF document based on Search with SQL fails

« on: July 12, 2011, 12:59:33 am »

I'm trying to get a RTF report, where the set of elements is based on a search result. In order to drill down to the problem, I've gone to the simples query possible:

select o.ea_guid as CLASSGUID,
o.Object_Type as CLASSTYPE,
o.name as Name
from t_object as o

When this query runs through the search window it is ok. my entire (small) model is returned.

Then I associate the model document to the search by specifying the Searchname tagged value. When trying to generate the report, I get an error message. The log-window shows the text below:

To run a custom search you must specify ea_guid AS CLASSGUID in your select statement

I don't understand this, because the CLASSGUID is in the query.

Please suggest or ask good questions for more info to solve this. I'm lost.

Marco

5

Bugs and Issues / No StereoTypeEx can be reported for external req

« on: January 20, 2010, 07:30:00 pm »

Steps to reproduce:
- Create a report tempate
- Add the section Package/Element/External Requirements
- Pop up list of possible fields only shows StereoType, but no StereoTypeEx  


Please add this field in your next build.

6

Bugs and Issues / Re: Cannot report attribute links

« on: January 20, 2010, 08:18:42 pm »

Well, it is all about complexity. EA as a software product has a rather high complexity with functional dependencies and glueing all over the place where even small changes lead to even more changes to be applied in various areas. Keeping track of such things is one of the most challenging tasks in actual requirements engeneering and software architecture as I learned some while ago.

Oliver

I know, but isn't that what this tool is all about: tracability  

7

Bugs and Issues / Cannot report attribute links

« on: January 20, 2010, 07:36:15 pm »

When a connector is linked to an attribute or method, I cannot report this information in a report.

I was expecting this information as a field in the section where you can document connectors (Package / Element / Connector/ Source|Target), but I couldn't find these fields.

8

Bugs and Issues / Popup menu inconsistent with menubar

« on: January 20, 2010, 09:10:22 pm »

When I start a template editor in a modal window, the options for "Keep lines together", "Keep with next", "Widow/Orphan contract" from the menu-bar show checkboxes when this applies for the selected text.

When using the template editor in embedded mode, these options can only be reached through the pop-up menu. The checkboxes don't appear there, even when the text is marked with these attributes.