Book a Demo

Author Topic: Potential Bug when rendering reports of Elements as Table Items.  (Read 2981 times)

skysigal

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Goal:
Create a report using Master/Model documents, that can render each package's child Elements (of the same Type/Stereotype) combined into one table.

Desired:
The expected result should be a table that has one header, and multiple rows, one per element.

Actual:
The actual result is one table, with a pair of Header/Body rows for each element processed.

Observations:
The same happens if the first 'Package' template references directly the 'Element' template containing the table (bypassing the TemplateSelector).
The same does not happen if the Element Table is embedded directly within the Model Document 'Package' template's Element tags.
In other words, it appears the behavior is specific to using the Template embedding process.
It's not an 'errant line return' issue: all templates have no extra rows, no spaces between end of table and closing tags, etc.


Setup:
* Using EA 12.1.1224

To recreate our situation, Our situation is as follows:
* One Master Document
    * containing multiple Model Documents (Head, Body, Footer)
* The Body Model Document
    * is associated to a Model Document template, configured to be render the Package information, then iterate through Elements, then child Packages.
    * the Element tag contains nothing but an invocation of a Template -- in this case a Template Selector.
* The Template Selector contains no text, but is configured to choose the right Template, based on Element type/stereotype.
* The template that is invoked contains a Table, with the top row defined as Header Row, and the second row filled with Element attributes.


Any work-arounds would be greatly appreciated.

Thank you!