eadocX Support

[eadocX Support]

Hi Simone,
Thanks for your patience – we’re right at the end of creating a whole new release, and I have to sleep sometimes 🙂
I have found the problem: eaDocX tries to treat <> characters and HTML tags, but there are only a few places where EA allows this: I think you just found another one!
I have fixed it in the next release, but that’s not ready yet to publish – probably 1-2 weeks.
In the meantime (and not a good answer -sorry) perhaps if you make the return type :
iMyInterface<Class> then eaDocX will be happy.

[eadocX Support]

I suppose we could add a simple option to ‘print all’ if that would be helpful. I’ll have a look….

[eadocX Support]

If you’re feeling brave, then have a look at ‘multi-hop relationships’ in the help.

[eadocX Support]

Documenting EA Mind Maps with eaDocX is new to me, and I’m not 100% sure I know what output you’d like to seem, but this is how I created my document:

1. Right-click on the Central Topic, and created a Quick Document. This looks for interesting strcuture in the model, but disappointingly, didn’t find much 🙁
2. Changed the Profile for <>Classes to print Inline, not as a table
3. To get a nice nested set of Word headings, I decided to print the children of each ‘level’ in the mind map using ‘Add Related Element’. (in the Profile, it’s in the Attributes of Related Elements’ tab, the bottom button. This tells eaDocX to print whatever it finds at the end of a relationship in whatever way that ‘thing’ normally prints. So I needed to specify that I wanted eaDocX to follow an ‘Association’ relationship type, in ‘either’ direction, but only to <>Classes
4. I then did the same for <> and <>Classes, but kept the <>classes printing in a table.
5. This seemed to produce a nice nested set of headings, with the leaf-level sub-topics in tables.

There are lots of other ways to do this, but this at least seemed to print a sensible initial document.
For example, I also added an additional attribute to my sub-topic table, to print a hyperlink to any other associated sub-topics, just in case mine was not a simple tree-structure model.

Like I said, lots and lots of other ways to do this, but I hope this gives you some pointers.

[eadocX Support]

Yes – there are standard attributes (of most element types) which are ‘Element Feature link’ and ‘Element Feature link Alias’. These will print most of this stuff which is connected by the EA Element Feature linking mechanism, and print either the name (hyperlinked) or the Alias(hyperlinked) of the target of the link.
At the moment (as if v3.5) these Element Feature Links don’t appear in the ‘Model Expert’ meta-model bit of eaDocX: we’re working on an update to this to discover these more obscure corners of EA!

[eadocX Support]

I’d try just creating a QuickDocument from the Centraol Topic. eaDocX will then try to understand the structure of the model, then you can customise the results you get from there.

[eadocX Support]

Looking at the eaDocX code which finds this data, KenN is quite right that its in the StyleEx field of the connector between the elements, where the StyleEx is either “LFSP” or “LFEP”

[eadocX Support]

Later. But soon.

[eadocX Support]

We are already using EA12 for our development and testing, so we know that eaDocX is fully compatible.
I’m assuming that all new EA12 functions will just create different kinds of EA Elements, Attributes, Connectors etc, so eaDocX should work just fine. We might perhaps create a new eaDocX Built-in Profile for database engineering, but that would only take you 10 minutes to create yourself.
What additional function do you think eaDocX should have for EA12?

[eadocX Support]

Can you send a small XMI with an example of your model, and I will take a look.

[eadocX Support]

This would be a great feature, and it’s one which we’ve thought about quite a bit.
The difficulty is where to specify the order of items in a package (or the order of packages), when the contents may increase or decrease between generations. So, if each item had a ‘TreePos’ (the name of the absolute tree position in EA) then when happens when items get added?
This is why we have gone for a simpler sorting approach.
BUT – help is at hand!
If you want to specify the order explicitly, but don’t want to change the sequence in EA, just create a ‘Favorites’ folder in EA Model Views, then get eaDocX to print the Favorites folder: eaDocX will print them in the right order, which you can set in EA Model Views. Its does mean that if you add new items, you’ll have to remember to add them to the Favorites list, but it’s a start.

[eadocX Support]

Just tested this, and you are quite correct!
I have created a fix, and this will appear in 3.5.7.0 which I plan to release later this week.
Sorry for the problem.

[eadocX Support]

Well, as you are all so enthusiastic about this, I will add it to the feature list for the next release (probably 3.6)

[eadocX Support]

Have you tried simply enabling the add-in? Also, do you have Admin rights on the machine ?

[eadocX Support]

‘LinkedDocument’ is a standard attribute of most items in eaDocX. Just select ‘linked document’ from the drop-down list of attributes.

[Author]

Posts