eadocX Support

[eadocX Support]

As usual, I need to know:
– versions of eaDocX , EA, OS, Office
– What were you doing when the issue happened
– is it repeatable
– can you email a small XMI and word document which will help us reproduce the issue to support@eadocx.com
Thanks

[eadocX Support]

Yes – got them – just haven’t got around to looking yet.

[eadocX Support]

I forgot to ask earlier – which eaDocX version are you using ?

[eadocX Support]

can you chop-out a smaller doc which displays the same symptoms? Then email to my personal address.

[eadocX Support]

Hi Frank,
Just so I’m clear, this text is in the notes field of the UC?

[eadocX Support]

OK – I have just tried this in the about-to-be-released V4, and it all looks fine.
BUT
I don’t think we changed anything in this area, so I don’t see why it doesn’t work in V3.
Can I confirm exactly where this data is located – notes field of an element? But what kind of element? I’m trying to reproduce the issue…

[eadocX Support]

Simplest immediate solution is to replace the “<" characters with "<" which eaDocX will not process.

[eadocX Support]

if you send me an XMI and a document, I’ll have a look

[eadocX Support]

Hi Heather,
eaDocX only creates bookmarks for headings, elements or diagrams which are referenced elsewhere in the document. Otherwise, your document would have a Word bookmark for everything, which could be 100s or 1000s in each document, which makes generation even slower.
If you have very sharp eyes, you might be able to see this happening. eaDocX first creates a GUID-based tag for every element/package/diagram on the first part of the generation, then sees which ones have inbound references. On the second pass, removes all the ones which aren’t used.
Does this explain what you are seeing ?

[eadocX Support]

eaDocX thinks that all <> characters are part of HTML tags, so will try to process them.
There are some places, such as in the notes fields of elements, where we treat <> characters correctly: what element type and attribute contains this data ? Maybe we can pre-process this like notes fields.

[eadocX Support]

It’s an EA Option: Tools, Options, Diagram, some diagram frame options.

[eadocX Support]

If, when you define you Element Report, you choose
“Use defaults for element type”
then eaDocX will use the formatting in the Profile for the element type/stereotype. You can then make that table, inline or Script.
We have seen some really impressive uses of Scripting for eaDocX formatting, where people need/want to reproduce some existing document style exactly. You can add colours, sub-tables, strange fonts, all kinds of stuff. But we only intend for it to be used very occasionally, otherwise you might as well use RTF !

[eadocX Support]

OOps. this has been built, but not release yet.
It will be in the next release (either 3.6 or 4.0, we haven’t decided what to call it yet)

[eadocX Support]

I think we’ve done this. Hidden in the ‘Searches’ tab in eaXL is a drop-down for ‘run script after import is complete’.
Is this what you need ?

[eadocX Support]

Do you have a little example for this as well? Probably the same problem as the return type <> one.

[Author]

Posts