Home › Forums › eaDocX queries › Navigating behaviour › Navigating behaviour
Home › Forums › eaDocX queries › Navigating behaviour › Navigating behaviour
OK – I’ll cut to the chase with this.
There’s no way eaDocX is ever going to support relationships of this complexity.
Our design point is to create great documents in a simple way, and this is WAY beyond ‘simple’!.
We support multi-hop-connector relationships, but the problem here is that you have two other kinds of more subtle relationship:
– the Method.behaviour one, which has caused me to add some support for this in the next version, but only to let method.behaviour hyperlink to an element
– the connection between a Message in an SD, and the Operation it calls. This is ‘fudged’ in EA (IMHO) using the name of the message/operation as a matching string. We’ve been asked before to make this a navigable relationship, but I just can’t make it reliable.
There MAY be some help on the way, by allowing you to write your own EA-Script based ‘exit’ to return hand-built HTML for eaDocX to insert directly, but that’s looking hard as well!
Download eaTeamWorks today for several free for life features, plus no obligation, 30-day trials of all the products: eaDocX, ea Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why we sell the world’s best-selling Enterprise Architect extension.
Download