Book a Demo

Author Topic: Incorrect List Numbering in RTF Report [SOLVED]  (Read 3632 times)

potterm

  • EA User
  • **
  • Posts: 126
  • Karma: +0/-0
    • View Profile
Incorrect List Numbering in RTF Report [SOLVED]
« on: December 12, 2009, 08:28:25 am »
Hi,

Before I raise a bug report I'd like to confirm that this is not just me misunderstanding how the RTF editor/reporting functions work.  I have a number of use cases, each one with a Linked Document attached.  Inside the linked document we are documenting the use case steps using a numbered list.  The linked document for each use case correctly shows the basic path numbering reset from 1 in each document, like this:

Use Case 1
1. UC1-Step 1
2. UC1-Step 2
3. UC1-Step 3

Use Case 2
1. UC2-Step 1
2. UC2-Step 2
3. UC2-Step 3

I have an RTF report template which I'm using to generate a use case report (i.e. including each linked document) but when I generate the report I get this:

Use Case 1
1. UC1-Step 1
2. UC1-Step 2
3. UC1-Step 3

Use Case 2
4. UC2-Step 1
5. UC2-Step 2
6. UC2-Step 3

This looks like a bug to me because the report is not showing the numbering that each linked document reflects.  Can anyone confirm this and/or offer a work-around?

Thanks in advance.
Martin.

P.S.  I'm using the basic list numbering that's available from the tool bar in the Linked Document editor.
« Last Edit: December 12, 2009, 09:26:29 am by potterm »

potterm

  • EA User
  • **
  • Posts: 126
  • Karma: +0/-0
    • View Profile
Re: Incorrect List Numbering in RTF Report [SOLVED
« Reply #1 on: December 12, 2009, 09:32:05 am »
I think I've just got to the bottom of this.  Our Linked Documents are created from a linked document template that we created.  The template includes the first entry of the numbered list for the basic path.  When we create a new use case we end up using the template and (I'm guessing) this is causing EA to use the same List Style for the basic path in every document.  When the whole lot is then combined into a single report then the list style continues from where it left off as it runs through each use case.

So the answer / work-around to this seems to be to create the numbered list afresh each time a new linked document is created, rather than using a pre-canned list in the template.