eadocX Support

[eadocX Support]

I added some function in 3.3.9 to insert the name of a Diagram as a heading, immediately before the diagram. As with most new behaviour, it’s set by default to be ‘off’.
Have a look in the Diagram options for your document, and see if this gives you what you need.

[eadocX Support]

There is no function which examines ALL the entries for a row/column: all the Conditional Formatting is done at cell level.

[eadocX Support]

have you tried adding a sort order to the rows/columns?
Yours may also be a variation of thus problem: https://store.eadocx.com/forum/2-eadocx-queries/519-use-cases-not-printing-in-specified-order#521

[eadocX Support]

Good idea.
It’ll be in the next build, sometime next week.
Just tried this, and it looks slightly odd: it’s hard to tell which is the ‘name’, and which the ‘notes’. Where there are notes to print, should the Name part be highlighted somehow?
e.g.
My Requirement
This requirement is really important

I don’t like adding fixed bits of formatting like this – for each person who likes it, another will hate it! – but I think it looks better. For now, I’ll leave it as you described.

• This reply was modified 11 years, 4 months ago by eadocX Support.

[eadocX Support]

The Moderator does agree!
Listen to Heather – she speaks wisdom.

[eadocX Support]

I agree. I’ll have a look.

[eadocX Support]

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!

[eadocX Support]

– draw an example diagram(s) which show the relationships you have created
– export it as XMI
– say what the the fragment of the document which will look like, which traverses the multiple hops involved
..so I can see if eaDocX can do it!

[eadocX Support]

Either:
– Use ‘print diagram + contents’ (see the Help)
– whenever you print a Use Case, print the name of the Actor as a ‘Relationship Attribute’. Optionally, then print all the Actors as a separate section, or as a Cross-reference Element report. Then the Use Case can have a hyperlink to the Actor.

[eadocX Support]

Just to make sure I get it, could you mail me a little XML with an example of the relationships ?

[eadocX Support]

Sorry, but I don’t know what a Microsoft Application Virtualization Client is, so we have not tested eaDocX in this environment.
Same applies to the licence server.

[eadocX Support]

I Agree – that’s very strange. I’ll have a closer look.

[eadocX Support]

I’ve tried to reproduce this, following your steps from above, but can’t seem to break it.
Can you email the eaDocX XML profile to me, and I’ll have a look.
Not we generally recommend it, but if you want to look at the Profile, the bit which deals with the Class should look something like:

[eadocX Support]

I just use the built-in Word property field for this, which is why we haven’t reproduced it in eaDocX.

[eadocX Support]

There have been no changes to the Glossary function for quite a while. You are correct that only the first occurrence is underlined. We found that documents where EACH occurrence was underlined looked terrible, and those with hyperlinks looked even worse. So, we never completed this feature, and currently have no plans to put it back.

[Author]

Posts