Filtering out subordinate acitivities in RTF repor

[Damir]

Hi guys

We're using UseCases with structured scenarios and we're genereting activity diagrams from them. When EA generates a diagram from structured scenario, it creates an Activity element under the use case, and then it places the diagramm and the generated acitivity and other elements of the model inside this Activity element (named with <name_of_the_UC>+_ActivityGraph).

Now in documentation that goes to the client we need to generate UC information and inside that should be the generated diagram - but not information on all the elements generated for the diagram (that information we already have in the UC scenarios).
Following tries were made in RTF documentation in vain:
- include element diagram but exclude child element - since diagram is under child element - the diagram is not shown
- include child elements but exclude elements of type activtiy, activityfinal, decidion, merge... - again problem since the first child of the UC is Activity so you don't get the diagram under it.
- include child element, include activites, but try filtering out activites which don't have tag diagramType which is added to the "<name_of_the_UC>+_ActivityGraph" and not other activites -COULD NOT MAKE SUCH ELEMENT FILTER ON THE ELEMENT FILTERS TAB OF THE DOCUMENT OPTIONS.
I think we're close with this one but I cannot figure out how to tell EA through element filters dialog box to: include all elements except activites that don't have tag diagramType

any help?!
many thanks

ps. I've tried moving diagram from activity to UC directly and filtering activities in the RTF template completely. this technically works but it is not solution for us since we'll be having hundreds of use cases and they have to be maintained and the diagram generation process simply makes another diagram when existing one is moved out that main activity under UC.

[Geert Bellekens]

I'm having the same issue now.
Anyone found a solution yet?

Geert

[Damir]

Not that I know of.

[Geert Bellekens]

My current solution is to create a new model document with a search that returns only the Activity element that owns the diagram.
Then I created a template that shows the scenario diagram.

A bit of a complicated solution for something that ought to be standard.

Geert