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

Pages: [1] 2 3 ... 17
Many thanks, peterc and Geert. O.K., I will go with virtual documents. V.

Hi, we have created several models (top level packages) within EA. Each model reflect a domain. The models are interrelated, meaning that they reference each other. We would like to export all models that also users without EA-access can see the content. This was not possible in the past (see also My understanding was that EA is becoming more and more a tool that supports EAM. So it should be possible to export all models into one html-site because all together represent the view of the enterprise. Is there a possiblity to export all models at once in the meantime or to integrate the models later? Many thanks in advance, V.

Glad it helped :) :)

Do you also have a solution for this: "Unfortunately I get only Alias + Attribut Name instead of Attribut Name + Alias. For my opinion the alias shoud be at the second place." ?

Hi Viking

Please enable Alias and Name in the Alias usage section of Diagram -> Behaviour tab in preferences.

and in the diagram setting please enable Use Alias if Available in Diagram -> Appearance

You will get both name and alias displayed .


Thank you very much, Arshad. This works.

Unfortunately I get only Alias + Attribut Name instead of Attribut Name + Alias. For my opinion the alias shoud be at the second place.

Just for your Information: I cannot see the pictures, uploaded by you.



I would like to show additional information of an attribute of an UML class. Default is that the class shows its attributes with formats and its methods.

The best way would be to use and show aliases in addition. Unfortunately the alias “replaces” the name of the attribute. So I tried tagged value, but I can only show the tagged value of a class. Another possibility would be to use the attribute name plus the alias name as alias and show the alias. But than I would have redundant information.

Is there a way to show additional information of an attribute (e.g. attribute name plus alias)?

Many thanks, V.

Why would it be a workaround?
You started from a template that reports everything. Feels pretty normal to have to filter it out to leave out some parts.
Personally I always start templates from scratch. That way I know exactly what is getting reported and what not.

Thank you for clarification, Geert.

Maybe you are right. My point is that the report includes diagrams, which are in other packages than the intended ones. They are just referenced by hyperlink. They have completely different meanings. The concept of Sparx says that a report includes packages.


Then you'll have to update the your template to exclude those parts I guess.
You might be able to use the filters in the template properties to filter out these elements.

O.k. Another workaround of the workaround of the workaround :-)

I hope the is no bus around. I am afraid that nobody would understand my report anymore.

I am using a customized copy of the system template "Model Report".

Default behavior is, that the report generates the diagram and just underneath the hyperlinked document.

It futher generates chapters like $diagram://{AD0D3E48-CB4F-4fe8-9EDB-E712C9B624E3}.


I am using Elements (e.g. Business Process) with hyperlinks on them pointing to other diagrams.

When I create a report, the report generator also creates the figure of the hyperlinked diagram with some text (e.g. $diagrams). I don't want this to happen. Hyperlinked diagrams should only included like normal diagrams.

Is this standard behavior which cannot be changed or is there a check box which has to be activated or deactivated, respectively?

Many thanks in advance, V.


I currently try to generate a report with Virtual Document. A Report Package has several Model Documents. Each document has the same Template assigned. In this template I want to retrieve a Report Constant (or a Tagged Value, if possible) of the Model Document, it is assigned to.

The current situation is as follows:
(1) The Report Generator uses the Report Constants from the Report Package for the Cover Page, which has been defined in the Report Generator.
(2) For the templates, used by the Model Documents, the Report Constants stay empty. I do not know which Report Constants get retrieved.

My questions are:
(1) which Report Constants are used by the template under processing? As I said, they stay always empty.
(2) is there a way to retrieve Report Values of the Model Report currently under processing?

Many thanks in advance, V.

Hi Geert,

It works now. It was the caching issue, I think. Many thanks. V.

Hi Geert,

Thank you very much for your valuable feedback. It helped a lot.

(0) “You seem to be making a difference between master document package and master document element. I only see master document packages. Am I missing something.” -> I am using Report Package (as the successor of Master Document). I am using Model Documents for each Package to be reported and assign these Model Documents to the Report Package.

(1) “Master document (packages) don't need templates. The template dropdown is disabled or readonly, and shows the default "Model Report" but is should really be blanked out. So the behavior is what is expected although it can be improved” -> o.k. This is REALLY confusing. It is even more confusing, that the generate ignores my template assigned as Tagged Values.
(2) same as (1)
(3) “supposing you mean "model document element" and not "master document element") -> no, Master Document (Report Package).
“I'm not seeing the "jumps one level up to the package" behavior you are describing.” -> see above.
“I'm currently using 13.5.1352, but I haven't noticed such behavior in previous versions either. In my case it opens up the dialog with the template dropdown filled in with the template from the tagged value.” -> as I said, the drop down list is inactive.
“The template dropdown is still enabled though, so I can select another template if I wanted to.” -> see above
(4) “I don't see different behavior between diagram and project browser.” -> because I use Report Package (Master Document).

“In all of the above cases the document is generated with the correct template.” -> in my case all use correctly except my own Model Report (which is a copy of the system Model Report). In this case SparxEA uses always the system Model Report. There must be a caching, as you described below.

“We did notice a bug like you are describing sometimes, when pressing F8 right after creating the Master Document package. Then sometimes the dropdown in enabled. In those cases the document would use the model report template and not report on the linked packages/search, but on the master document package itself. This behavior would be solved by first selecting something else in the project browser and then selecting the Master Document package again. Looks very much like a caching issue to me, like when the application cache isn't aware of the special status (stereotype) of the package yet and treats it as it would be a regular package.” -> could you tell me what you mean with “linked packages/search”? The Report Generator uses the right package, but the wrong template (in my case the system Model Report).


I tested the tutorial on two different environments. I always get the same result: an empty page.


I followed the instructions in to create a report.

The document says "Double-click on the Document Artifact. The 'Generate Documentation' dialog displays". In my test a template gets opened, but not the "Generate Documentation" dialog. Is that correct? If not, how can I change this behavior?

Many thanks in advance, V.

My current situation is this and it makes me mad:

(1) Select Master Document (or Report Package) in der Diagram > F8 > in Generate Document: System-Template “Model Report” is default and CANNOT be changed.
(2) Select Package of the Master Document element in the Project Browser: same as above.
(3) Select Master Document in the Project Browser > F8 > in Generate Document: the selection jumps one level up to the package, but Template can be changed. But this is not of any interest for the report generator: it still uses Template “Model Report”. It also create a report about the report elements, which is not intended.
(4) Select Diagram: same as above.

Sometimes the system takes my template, but in only about 5% of the tests.

I did not understand the concept at all or this is a bug.

Help is very welcome, V.

Pages: [1] 2 3 ... 17