Multi-hop relationships are one of the hardest features in eaDocX, and that’s after we deliberately tried to simplify it!
I guess you’ve found the ‘Advanced’ button on the relationship page, where you can specify the relationship ‘hops’. This page, and the ‘Add Hop’ page which follows, allow you to describe all the relationships between the source element – in your case, ‘Task’, and the target.
We designed this to print single attributes of distant elements – in our case, the distant element was the ‘Release’ to which an element is linked.
This is fine, of you just want to show a single attribute of the distant element.
If you want to show many attributes of the distant element, or – as in your case – the route of how we get to that element, then multi-hop isn’t really suitable. What gets lost is which of the intermediate nodes is linked to which other one.
This is why we developed the ‘relationship table’ idea, where you define the relationship once, then the list of attributes to print at the end of it. This works OK for a single ‘hop’, but not for the multi-hop AND multi attribute situation which yo’re describing.
All I can suuggest is creating your report using more hyperlinks, and fewer multi-hop links. So, create a report with the Tasks and their related Screens, with a hyperlink between the two.
Then, where the Screens are printed, print both attributes, and a link to their related Use Cases. Etc for the other links.
Not as nice as a simple table, but w could never figure out what a ‘simple table’ would look like which did all of this.
.
