Hello all,
I'm new to this forum though not new to EA, I've been working with versions 7.0, 7.5 and 8.0 for about five years now. I started as an Information Analyst at a new customer a few months ago, and we are trying to persuade the organisation that document generation from EA is the way to go. In order to do this a working template would be nice. Recently I ran into a problem trying to get our master document made in 7.5 work in 8.0. Let me explain the problem.
I might have worked with EA a lot, I came from an organisation that had it's templates in order, so I never had much to do with maintaining them. This new customer is different, so I had to learn on the job. We orginally had the odd problem we could not insert a Table of Content in our 7.5 template, but then we discovered that this was because we used self-defined paragraph-headers. Unfortunately the "Insert Table of Content" option only becomes active if you use the predefined 'Heading 1', 'Heading 2' etc. No problem, one might think: just use the predefined types, edit the style to suit your needs and you'd be OK. Not so. Recently the need has come up to use dynamic paragraph numbering in our headings, and the predefined heading do not work the way we want, where self-defined headings did. The prolem lies with the secnario's in our Use Cases. This is the code we use:
[highlight]scenario >[/highlight]
2.2. {ElemScenario.Type} scenario: {ElemScenario.Scenario}
{ElemScenario.Notes}
[highlight]< scenario[/highlight]
This works well with self-defined headers, dynamically numbering each scenario as it is found during rtf-generation. Using the 'Heading 2' (Level 2 override in the numbering) however it shows as a 'Heading 3' ("2.2.1 etc.") in the generated document. I thought I could be smart by editting the style of 'Heading 3' to the exact same as 'Heading 2' (including the Level set to 2), but it still shows as a 'Heading 3' after generation whatever I try!
The self-defined headings work fine, but there the problem is that they are not recognized as such by the Table of Content. I can make the ToC in the generated document understand that it should include these self-defined headers, but is there a way to add them to a ToC in the template itself, so they are generated rather than added manually after generation?
Is there anybody here who recognizes the problem, and better still, knows what to do about it?
Mario Wens
The Netherlands
