Reports: Table heder repeated for each row

[Pawel Zubkiewicz]

Hi,

In a report template, according to the help file called "Create Sections as Tables", when I set a top row of a table the header should not be displayed only once.

I want to display in a table Use Case steps from Structured Scenario. Here is a fragment of my template

In a table top row is marked as header (context menu: Table | Header Row).

Unfortunately in generated document, header row is repeated (actually I think whole table is repeated) for each element in Structured Scenario of a Use Case.



Can anyone please explain me what am I doing wrong?

Thanks in advance  

[Pawel Zubkiewicz]

Ok, I managed to do a workaround like that. It works but it's ugly (Header is a separate table above the structured scenarios section).


After fixing that I found out a much more disturbing problem.
The same part of template is used to display also information about Exceptional and Alternative flows of Use Case.

However I don't see any possibility to display information

• at which step of Basic path the alternate path starts,
• and when it is going to join Basic Path.

This is serious.

On the picture below in sections "Alternate. PIC not found" & "Exception. Could not connect":

• in red marks I would like to have Join-step number (respectivly 4a and 3a).
• yellow marks, step one... well it should be 4a and 3a in my opinion. but i can live with that
• and finally biggest problem: there is no information when alternative/exceptional flow is joining Basic Path.

Does anyone have any idea how I can add those information to generated documentation about use cases? Right now, document generated will be not complete, therefor not useful for developers.

[Geert Bellekens]

You have to select the header row and mark it as being a header.
(right click, Table|Header Row)

That will prevent the header row from being duplicated.

Geert

[Pawel Zubkiewicz]

You have to select the header row and mark it as being a header.
(right click, Table|Header Row)

Hello Geert,
I did this (it is mentioned in the first post) and it's not working as expected.

However, the problem from my second post is much more important for me. Do you have any advice on that?

[Geert Bellekens]

Hi Pawelz,

If it doesn't work you might be able to get it working by deleting and recreating the table.
These templates sometimes get confused I think, and then often the only way to solve it is to delete the offending part and start again.

For the other problem I would create a separate topic. It's always best not to mix different problems in the same topic.

Geert

[Pawel Zubkiewicz]

If it doesn't work you might be able to get it working by deleting and recreating the table.
These templates sometimes get confused I think, and then often the only way to solve it is to delete the offending part and start again.

I used to work with EA9 & 10 and I see much has been improved but some problems remain.
Back to the topic: I created table for use case steps on my work and private computer, both times creating new template from EA's built in "Use Case Details" template. Maybe this is a problem?

For the other problem I would create a separate topic. It's always best not to mix different problems in the same topic.

Ok, I will make another topic for this problem.

[Geert Bellekens]

Yes. If I were you I would try to start with an empty template.

Geert

[Pawel Zubkiewicz]

Geert I did what you suggested and created template from scratch:


And row header problem is eliminated as you can see in the picture below:


One curious thing: in template I have headings numbered correct, but in output Heading 3 is skipped and Heading 4 is displayed instead. Any logical reason for that?

[Geert Bellekens]

It he style wrong, or is the numbering wrong?

Numbering in header styles is a bit specific. The main thing is to make sure that they use the same numbering list.

It took me a few tries too before I got a working set of header styles.

Geert

[Pawel Zubkiewicz]

Thanks for you help :-)

I'm using build in 'Numbered Headings' style in my custom template.
Headings are correctly assigned (as you can seen in previous post image):

{Pkg.Name}	Heading 1
Use case: {Element.Name}	Heading 2
Scenario {ElemScenario.Type}: {ElemScenario.Scenario}	Heading 3

Now, I changed last element to Heading 2 and it works as I want it  .

So it's a little bit confusing, either there is a bug or heading levels are also taken from section level - what I mean here is that I imagine  Scenarios are children of Use Case element and as children they are pushed one level under the parent. So setting in template Heading level 2 for scenarios is evaluated as Heading of one level below: Heading 3.

I still don't understand how it works exactly, but at least I managed to have desired output. I think topic can be marked as closed.

Thank you Geert again for your help