Book a Demo

Author Topic: Cannot generate table for Element > Diagram in Report Generator  (Read 5198 times)

mse

  • EA User
  • **
  • Posts: 308
  • Karma: +1/-0
    • View Profile
I was so happy to see how easy it was to generate a table based on elements on a diagram within a package (my BDD diagrams).

However, when it came time to generate tables for the IBD Diagrams within each element, I could only output the diagram itself. Unfortunately there is no option for selecting subelements of the diagram as is the case one level up. How can I accomplish this?

Forget the tables for simplicity sake, even just a listing of the parts of the IBD when the IBD is embedded under the element, does not seem possible. I could move the diagram out, but then I'm not keeping to the nature of what an IBD is, which is internal to the block.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Cannot generate table for Element > Diagram in Report Generator
« Reply #1 on: August 23, 2019, 04:19:09 pm »
In general is not the best idea to base your document generation on what is shown on diagrams.
It's usually a lot easier if you can base it on the model structure.

In that case you can tell the document generator to go one level deeper in the structure using "child elements" and "child packages" sections.

A possible, very versatile alternative is to use SQL fragments to fill your table.

Another option is to use virtual documents with model documents for each of your IBD elements.

Geert

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1183
  • Karma: +30/-8
    • View Profile
Re: Cannot generate table for Element > Diagram in Report Generator
« Reply #2 on: August 23, 2019, 08:41:56 pm »
In general is not the best idea to base your document generation on what is shown on diagrams.
It's usually a lot easier if you can base it on the model structure.
The only exception being reuse. It is a pity a real pity that Sparx EA does not easily allow reuse of elements in other packages by allowing the creation of a link/shortcut to elements in another package.

Of course, elements can be reused but as the OP highlights, creating documentation templates gets tricky. I would love if Sparx EA could do the below, if the Paste\Drop As had an extra option to create a link/shortcut to an element in another package, it is almost a form of pseudo-instantiation.

Model
---->Information System 1 Model
------->Class Model
------------->Diagram 1
------------->Class 1
---->Information System 2 Model
------->Class Model
------------->Diagram 2
------------->Link to Class 1 (from Information System 1 Model)
------------->Class 2

Maxim Kuznetsov

  • EA Novice
  • *
  • Posts: 6
  • Karma: +2/-0
    • View Profile
Re: Cannot generate table for Element > Diagram in Report Generator
« Reply #3 on: November 02, 2019, 12:54:20 am »

Hi.To generate the same report for diagram under element as under package, just leave "element>diagram>" section blank. It will inherit rules for "package>diagram>" section from this template.


See details here.

skiwi

  • EA Expert
  • ****
  • Posts: 2081
  • Karma: +46/-82
    • View Profile
Re: Cannot generate table for Element > Diagram in Report Generator
« Reply #4 on: November 04, 2019, 11:42:10 am »
To generate the same report for diagram under element as under package, just leave "element>diagram>" section blank. It will inherit rules for "package>diagram>" section from this template.

See details here.

Thanks for this, but I'm not seeing it work when the package diagram is defined in a fragment (because I wish to use the same format for Package > Diagram as I do for Element > Diagram)
Orthogonality rules
Position and Team disestablished, thanks austerity.
Now itinerant.

Maxim Kuznetsov

  • EA Novice
  • *
  • Posts: 6
  • Karma: +2/-0
    • View Profile
Re: Cannot generate table for Element > Diagram in Report Generator
« Reply #5 on: November 05, 2019, 06:28:28 pm »
Yes, it doesn't work for fragments, only for diagram explicitly defined in the same template.