Conditions in RTF reports?

[stereotype]

Is it possible to specify a condition in an RTF template, e.g. in order to only include connections of a certain type in the report? (I only want an element's aggregations to be listed, not all connections...)

If this isn't possible today - is it planned in the future?

[Eve]

Build 833 allows you to filter the types of connectors that are shown.

See http://www.sparxsystems.com/uml_tool_guide/enterprise_architect_reports/rtfdocumentoptions.html

[Ben Liesfeld]

This is such a valuable function: filtering of element and connector types in the RTF generator.
However, it does not seem to work quite as I expected. E. g. I the elements that are at the other end of connectors are not filtered.

In my application I try to construct the following report:
1. List all elements of type "requirement".
2. List all use cases which are connected to the requirements via "realization".
However, there are other element types connected to the requirements from (1.) via "realization".

Will that be fixed or is it that way on purpose?

Regards,

--
Ben

[RoyC]

For the instance you define, try generating a Dependency Report and/or an Implementation Report. They seem to provide the filtering that you want.

[Ben Liesfeld]

Thanks for the hint to Implementation Reports. Haven't used this feature before.
However, you have no access to the RTF generator from there. I am not sure what the purpose of Implementation and Dependency Reports is. It surely is not the printing of information.
Anyway, filtering doesn't work for me here, either. I selected Use Cases as active only (through "Set Target Types") but the report shows Implementor Types Feature, Use Case, Class as if no filter was set...
Is there something broken in my database?

[Gold]

Hello,

 I was also looking for a way to filter based on the type of element that is the target of the connector.

Have you found a solution to that problem?

[Ben Liesfeld]

Hi,

No, unfortunately I have not found a solution. I will 834 now, though. Maybe it is fixed there.