eadocX Support

[eadocX Support]

Yes – just been off with Sparx at Gartner. This one is next-but-one on my to-do list….

[eadocX Support]

Hello.
Yes eaDocX will print information about related elements which can be located anywhere in your model.
Here is a link to info which describes various ways in which you can structure your documents using eaDocX:
https://store.eadocx.com/help/index.html?structuring-your-document.htm

There is information about printing related elements (and the relationships to those elements) in the help here: https://store.eadocx.com/help/index.html?related_elements.htm
And in more detail here: https://store.eadocx.com/help/index.html?related-element-data.htm
(there are also sub-pages which go into even more detail)

In addition you can print multi-hop relationship data –
https://store.eadocx.com/help/index.html?advanced-relationships.htm
(PS the help says that this is an experimental feature but that message is old and will be removed shortly – multi-hop is now an established part of the core eaDocX function)

Best regards

[eadocX Support]

Sorry for my lack of knowledge of EA, but what does it mean when a property is ‘derived’. Does it mean it has a flag which says ‘derived’ or does EA do something clever to derive it? eaDocX only works on data which is actually saved in the database.

[eadocX Support]

I think I have fixed this in 3.8.4.4, now available on the website. Please let me know if this works.

[eadocX Support]

I have just added eaDocX 3.8.4.4 to the website, which has additional tracing on the method which is failing for you. I’ve also re-written it, to use the latest XML framework, which is MAYBE where the problem was (though I still can’t make it fail….).
So, enable the eaDocX trace, and try it again.
(I don’t like releasing ‘fixes’ when I have no idea if they really fix the problem, but I’m afraid this is the best I can do…)

[eadocX Support]

This is possible, but hard for us to check.
eaDocX does make use of Word .DLLs, so if your environment doesn’t allow this, then eaDocX won’t work.

[eadocX Support]

eaDocX is, indeed, clever 🙂
No more 50-page glossaries….

[eadocX Support]

Can you confirm the exact step you too to create this error?
I can see where the error is produced in he code, but can’t figure out how you would get there!
I’ve just tested the basic function, and that’s OK:
– create a quick document of some bit of the model
– add a glossary to the document (EA Glossary was empty at this point)
– eaDocX doesn’t print anything – correct
– added some glossary items to EA, where those items are present in the generated document
– eaDocX created a glossary, showing only the terms present in the document – correct

[eadocX Support]

Whither attachment?

[eadocX Support]

‘fraid so.
As you may be aware, we only do fixes on the current version.

[eadocX Support]

please can you install latest version – currently 3.8.4.3

[eadocX Support]

eaDocX version ?

[eadocX Support]

OK – found it!
‘Key’ is used by EA when an ‘Attribute’ is really the definition of a column in a database table.
Where the column is the key of the table,then the ‘key’ = “PK”

[eadocX Support]

select count(*) from t_object
gets the total number of elements.
same as
select count(*) from t_package
gets the total number of packages.

[eadocX Support]

I suggest you look at Tomas Killin’s book Inside EA to see what that column does.

[Author]

Posts