RTF report problem (realization relationship)

[Robo]

I have some problems generating my RTF report including realization relationships (using EA7.1). Even if I add "{Element.Realizes}" in the Element section of the template I never get the field replaced with any realized element in the RTF document.

Template looks like this:
package >
element >
{Element.Name}
Realizes:
{Element.Realizes}
< element
< package

Model was a simple realization: Use Case <-- Component

The result is the name of the Component, but no realized Use Case.

any help is welcome!

[Dermot]

Hello Robo,

Thanks for poiting this out.
I have tried the same - without success, so I will pass it on to be looked into.

[Robo]

Thank you very much.

Might be that a similar problem exists for associated issues. If i create an issue for a component and bind these two elements using the realize connector, no issue is generated in the RTF Report even if the issue field is part of the template (I tried other connectors also).

Template:

package >
element >
issue >
{ElemIssue.Issue}
{ElemIssue.Notes}
< issue      
< element
< package

I am not sure if I am binding issues in the right way (using realization) and if the 'issue' field shall list all bound issues in the report , but this is what I expected ...  

[«Midnight»]

Hi Robo,

If you have a small project that you could compress - EAP files tend to be rather large otherwise - and attach to an email, perhaps you could send that in to Sparx. It might help them see exactly where the problem lies.

You could attach the file to a bug report - use the Registered Users page for the correct link, since the link on the forum page might not let you attach a file - or use the support email address (you'll find that on the Registered Users page or the Products page).

David

[Eve]

The issues referenced there are the internal issues on an element (View | Maintenance).

The Element.Realizes although misnamed is more like Elem.Implements.  It documents the interfaces that a class implements.  There is also the External Requirements section for Realizations of requirements.

[Robo]

Using the Maintenance View solved my problems with issues.
Thanks