Hierarchical Numbering for RTF Documentation

[amr]

Hi!
I'm using EA 9.2 for Requirements Management and RTF documentation. For my actual project have created a fairly simple structure in the Project Browser, like this:

Component1 (package)
    Functional Reqs (child package)
        REQ001 (element)
        REQ002
        ...
    Non-Functional Reqs
    Tests
Component2

I think you get the idea.
Now I want to create an RTF document, with the following numbering:

1 Component1
1.1 Functional Reqs
1.2 Non-Functional Reqs
1.3 Tests
2 Component2

I have created list and overrides according to the EA Help. What I was not able to do so far, is to assign different formats and numbering to the two different hierarchical levels of packages.
Currently my template looks like this:

package >
{Pkg.Name}

element >
{Element.Name} {Element.Stereotype}
{Element.Notes}

child elements >
< child elements
< element
child packages >
< child packages
< package

Now the rtf looks like this, which is not what I want:
1 Component1
2 Functional Reqs
3 Non-Functional Reqs
4 Tests
5 Component2

The problem is, that I can only assign one format to the field {Pkg. Name} and also only one numbering level. As soon as I include an additional field {Pkg. Name} to the child packages section, the rtf document will not contain any elements any more.

What am I doing wrong, any ideas?

[Stefan Bolleininger]

Have you tried to set the option "adjust heading levels to heading9" within the document options for the template?

Therefore open your template in the document designer, click on "document options" ( the fourth button on the very top) or rightclick into the template File>>Document options.

Greetings

Stefan

[amr]

Yes, this option is already set by default.
When I include the field {Pkg.Name} also in the section child packages, it looks like this:

package >
{Pkg.Name}
element >
{Element.Name} {Element.Stereotype}
{Element.Notes}
child elements >
< child elements
< element
child packages >
{Pkg.Name}
< child packages
< package

The results are perfect in terms of numbering of the packages. It's exactly what I want. But, now there are no elements exported. I just get the heading structure in the rtf document, but no requirements at all  :-/

[Robert Sheridan]

I got this to work by following the instructions in the user guide exactly (it is a very tedious and repititive process); however, I found a bug in the process which means that sometimes the numbering restarts. Sparx have accepted it as a fault but I do not know when it will be fixed.

[skiwi]

I found a bug in the process which means that sometimes the numbering restarts. Sparx have accepted it as a fault but I do not know when it will be fixed.

Nice one, it is a significant feat to get a repeatable bug that Sparx will accept. Take it from one who has tried, and tried, and

well done