Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Pawel Zubkiewicz

Pages: 1 ... 4 5 [6]
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.


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  :)

Automation Interface, Add-Ins and Tools / BusinessRule auto names
« on: March 20, 2015, 11:10:48 pm »

I'm using EA12 and I have a problem with auto names.
I created auto name rule for Requirement element type and it is working correctly.
Unfortunately, every time I create new BusinessRule element it has auto generated name as it was Requirement.

Now, I understand that BusinessRule is just a stereotype for Requirement type, nevertheless I'd like to have my business rules auto-named with different naming schema than my requirements.

Is there any way to achieve it?

Pages: 1 ... 4 5 [6]