Auto-Report Generation Questions

[Sagi]

There are three things I can't seem to customize in the auto-report generation feature.

1. When choosing a node to start the report generation procedure, the content which I'm pulling and the base node selected can be 4 levels deep.
Thus, the heading will start with 1.1.1.1 and I can't seem to correct this (instead of desired 1 or 1.1)

2. The filtering option allows elements to be filtered to certain criterias but it doesn't allow packages to be filtered. For example, If the root node contains 10 sub packages, and each subpackage then contains 2 sub-sub packages and I'd like the template to filter out certain packages by keyword, how would I do that?

3. Lastly, the table of contents seem to lack in any sort of customization. Is there something I'm missing?

Thank you all.

[djdejong]

By node do you mean a package within Project Browser?

I'm not sure I understand exactly what you're asking, but when it comes to document generation, I recommend learning to using virtual documents. I've tried a few ways to generate documents and this seems to be the best. I've been using virtual documents that use a combination of templates, filters, and template fragments. It's still very finnicky and a significant learning curve to get the hang of it, but it will allow a very high level of customization.

Perhaps this doesn't help, but if it happens to then Geert has a really a good tutorial about virtual documents: http://bellekens.com/2015/11/12/tutorial-generate-complex-documents-from-enterprise-architect-with-a-two-step-semi-automated-approach/

[Sagi]

@djdejong

Yes. By node I meant package. Let me illustrate:

1.   Generating filters for packages
         a.   EA has filters allowing for element filters and they’re easy to implement, however when it comes to package filters, it’s much harder.
         b.   I’m trying to use {Pkg.Name} and grab only certain package names.
                 i.   Example Package structure:
---------------------------------------------------------------------------------
1.   Base Package
      a.   SubPackage
               i.   Sub-sub-Package
                        1.   Use case
                                a.   Activity diagram
                                b.   Elements
      b.   Sub package
                i.   Sub-sub package
                        1.   Use case
                                a.   Activity diagram
                                b.   Elements
---------------------------------------------------------------------------------

c.   How would I only call {Pkg.Name} for the packages shown in red text?

Thanks.

[Geert Bellekens]

I agree with djdejong. You should look into virtual document.

It is very hard to make a single template that fills your complete document, but it is very easy to create small focused templates and combine them using virtual documents.
I'm sure it will save you a lot of time (and headache) in the long run.

Also check the learning centre (Alt-F1) for some good step by step instructions.

Geert

[djdejong]

So a possible approach to what you want using virtual documents might involve writing a script to conditionally set the source of a model document such that it's the desired package within that package structure you depicted. Then when you insert the {Package.Name} field into the template for that model document, it will grab the name of the source package.

I recommend first manually creating the virtual document that does what you want so you have an intuition, then adapting the script provided in the link to make it automated. Of course this is all assuming you'll ahve some sort of consistent package structure.