Recent Posts

Pages: 1 ... 7 8 [9] 10
What do you mean by "is locked". There are a couple of possible culprits. Can you be more specific?


I'm new here and I'm using EA for my work. I've encountered a for me unsolvable problem. I've made some tables and mysteriously one of them became locked, without me having locked that element in the element context menu. I read that somebody had the same problem and has unlocked the element in the DB Table of EA. But I have no idea how to do that. Does anyone have a solution for my problem?

Bugs and Issues / Re: Slow import of large codebase
« Last post by MaXyM on March 22, 2018, 03:39:09 am »
What type of engine did you use for mysql? If MyISAM (which is non-logged/non-transactional) then it would explain the boost comparing to MS SQL. If InnoDB then it would be real benchmark.

Speaking about databases I can suggest to try postgresql :)

1) Create a package. The name of this package will be shown in the browser tab title when navigating the HTML.
There's no need to create a master document, just a regular package.

2) Create a documentation diagram and a model document. The name of this element is not used anywhere. "HTML Generator" is a good name.

3) Leave the model document's tagged values empty or default. They are not used for HTML generation.

4) Drag-and-drop each package you want to include onto the model document.
You can't drag root nodes onto the model document, but you can drag view-level packages from multiple root nodes.

5) If you wish, you can edit the names and top-down order of the resultant attributes.
The attribute names control what package names are displayed in the HTML tree view. The actual links to the packages will not be lost, and (in EA) you can right-click each attribute and find the package in project browser.

That's the setup.
To generate, select the model document and hit Shift-F8. In this dialog is where you select the style (= HTML template set).

You might be able to save a generation configuration (ie, the settings in the HTML generation dialog) as a resource document. I don't know, I haven't tried that for this type of setup.


You're welcome, glad I could help. :)

General Board / Re: specify maximum size of a diagram in a report
« Last post by on March 22, 2018, 02:57:38 am »
In Diagram properties, Page Setup, Advanced you can select page with or any scale
I dont see how to use Virtual document when creating HTML reports??
Same with Report packages, cant select HTML templates
Maybe not supported or....
Ok, consider this as solved.
I gave the template and the fragment different names - which however did not solve the issue at first.
But after I restarted EA, it magically worked like it should!
I will note for myself to restart EA the next time before fiddling with something which does not work like it should...

So in conclusion, I might not parametrize the "RMM*" conversion string in the SQL query, but since all affected requirements are located in a distinct package, using #PACKAGEID# will do the same job for me.

Geert, thank you very much for your answer! It helped me to keep following the right approach on this.  :)
I might note that the Fragment and the Template both are named "KLS_RiskMitigationCoverageTemplate".
I don't guess this should be a problem but I just renamed the template to avoid any trouble from coming from that.
It doensn't change anything though.
I don't think that statement is correct. I use #PACKAGEID#, #OBJECTID# and #DIAGRAMID# all the time in SQL fragments, and I always use master/model document for code generation.

Well, I don't know what I'm doing wrong then. I added the package ID to SQL query accordingly:

This is the content of the fragment:

The template basically justs refers to it:

All risk mitigation measures are located as requirements in a package in the model:

If I select this package as shown in the image above and generate a document from the template directly using the button, this works as expected.

But if I have a Model Document which uses the template and the package

and I select the Model Document, press F8 and run a report, the result stays empty.
The same applies if I generate the report from the Master Document.

Pages: 1 ... 7 8 [9] 10