Author Topic: Nested elements dont show up in documentation - continued  (Read 3134 times)

michielper

  • EA User
  • **
  • Posts: 120
  • Karma: +1/-0
    • View Profile
Nested elements dont show up in documentation - continued
« on: September 14, 2016, 08:30:42 pm »
This is a continuation and update from a thread in General Board.

I have a nested structure in my Project Browser with various element types (actually Goals, Principles and Requirements in Archimate). Now I want to make a report where only one type of element is included, independent of its level in the Project Browser nesting.
So I checked the box  <Include child elements even if the parent element is filtered out>.
However, that seems to work only for the first level!! Not recursively..... Elements which are two levels deep and are children of elements that are not included in my filter, are not printed!!!! Very weird indeed.

Update 1: I have reported this issue with Sparx. Awaiting their answer.

Update 2: I have been able to partially work around this issue by separating the document template from the selection query through the use of a Model Document which uses a Search as input. However, this has the disadvantage that the project browser hierarchy is no longer visible in the report. So no more paragraphs corresponding to packages; it is just one long list of elements.

Update 3: Another disadvantage of using a Search as input for a report seems to be that the sort order cannot be specified..... I would like to sort on package but I have not figured out how. Creating the search as an SQL query and sort by t_object.package_id works perfectly as a search on itself but when I specify this search in the Tag of the Model Object, it gives an error when trying to generate the document. Please help!
« Last Edit: September 14, 2016, 10:00:28 pm by michielper »

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 9480
  • Karma: +266/-27
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Nested elements dont show up in documentation - continued
« Reply #1 on: September 14, 2016, 10:40:44 pm »
I've reported the sort order issue as a bug a while ago, but it has not been fixed yet AFAIK.

Geert

michielper

  • EA User
  • **
  • Posts: 120
  • Karma: +1/-0
    • View Profile
Re: Nested elements dont show up in documentation - continued
« Reply #2 on: September 15, 2016, 06:31:38 pm »
Ok, I do get very frustrated about all these random things not working as they should. I think they have an issue with their testing process...

Here is another issue with Model Documents:

I use Model Documents to create reports consisting of a random number of packages. The packages are dragged into the Model Document class and become attributes referring to the actual package. This seemed to work quite nicely..... There are two ways to specify the element selection to be included in the report: (1) in the RTF-Template tagged to the Model Document (2) in the Search tagged to the Model Document. Now, due to the recursion bug in the RTF-Templates, I had to revert to the second method. However..... The Search specified in a Model Document is IGNORED when there are packages in the Model Document class! The search works (more or less.... because the sorting does not work) with a Model Document that has no packages in it but once you drag in packages, the Search tag is ignored. Completely illogical and VERY FRUSTRATING!!!

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 9480
  • Karma: +266/-27
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Nested elements dont show up in documentation - continued
« Reply #3 on: September 15, 2016, 07:15:06 pm »
Yes, it's one or the other.

Either you define the source by dragging package(s) onto the model document or you define a search in the tagged values. You can't combine both methods.

But if you need both then you can simply create a new model document. You can create as many as you want, and they will generated in the order of the elements in te project browser.

This is in fact somewhat of a workaround that I've used in some instances. Create a model document for each single element I want to get generated. In those cases I would recommend scripting the creation of the whole virtual document to avoid going completely nuts... :-X

Geert

michielper

  • EA User
  • **
  • Posts: 120
  • Karma: +1/-0
    • View Profile
Re: Nested elements dont show up in documentation - continued
« Reply #4 on: September 15, 2016, 08:15:32 pm »
And all this to work around a bug..... very frustrating. I hope Sparx will come up with a solution soon!

michielper

  • EA User
  • **
  • Posts: 120
  • Karma: +1/-0
    • View Profile
Re: Nested elements dont show up in documentation - continued
« Reply #5 on: September 15, 2016, 08:37:18 pm »
I have EADocX here but not really used it. Would that solve my problem?

Will it be able to do all of the following in one report?
1. Specify random packages to be included in a report?
2. Include elements based on a search criterion independend of their nesting level?
3. Retain the model nesting structure in the report, or at least sort by package?

Michiel

Jeff Weedman

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: Nested elements dont show up in documentation - continued
« Reply #6 on: September 17, 2016, 01:00:55 am »
I'm also having this same issue with nested elements not appearing on reports. Please let me know when this is fixed.

Thanks

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 6822
  • Karma: +63/-7
    • View Profile
Re: Nested elements dont show up in documentation - continued
« Reply #7 on: September 19, 2016, 05:36:16 pm »
3. There's a line in the release notes for 13 that suggests we have added the capability to specify a sort in this scenario.

2. Yes, a search lists the elements only. Without reference to the packages that contain them.

1. I didn't even remember that there was an option to include the child element if the parent didn't match. So my comments on your issue aren't going to be helpful.

To get the report you want, create a template selector fragment (http://www.sparxsystems.com/enterprise_architect_user_guide/13.0/model_publishing/define_a_template_selector.html)

For the element types you want to document, specify a template that shows their content.
Specify an empty (or cut down) template for the elements you don't want.

In your main template, add a reference to your template selector (http://www.sparxsystems.com/enterprise_architect_user_guide/13.0/model_publishing/adding_fragments_to_a_template.html) and also include the child element section.

This should allow you to filter reported elements without using the built-in filter mechanism, and allow the behavior you are after.
Eve

support@sparxsystems.com