eadocX Support

[eadocX Support]

Hmmm. This is very odd…
Could you email a little bit of your model, in XMI format, to support@eadocx.com, and I’ll have a look. Can’t think what’s happening..

[eadocX Support]

..should be just the same….
How about the other question ?

[eadocX Support]

Which eaDocX Version are you using?
What you are doing is correct. There are two ways to print the Internal Requirements of a Use Case:
1 – Add a sub-element called ‘Element Requirements’. If you have not already defined some a Profile for Element Requirements, then eaDocX will privide some initial defaults (a table with the name & description)
2 – Add an attribute of ‘Element Requirements Summary’, and this will print a single comma-delimited list of the Internal requirements.
I’ve just re-run the test cases for this using eaDocX 3.0.5, and it looks OK.
Are these Internal Requirements, or requirements whih are connected to the Use Case via relationships? If the latter, then I suggest you create a ‘Quick Document’ using the package which contains the Use Cases, and Quick Document will find all the relationship types which exist in your model, and print hyperlinks to them.

[eadocX Support]

Are you using a full install of Office 2003, 2007 or 2010? Also, did you install EA first, then eaDocX?
We have seen problems with the version of Word which install new features as you use them (can’t remmber what Microsoft call it). This version usually produces atrange erros like this.
Please confirm:
– Office Version
– OS
– EA version

[eadocX Support]

Oh yes.
eaDocX only supports full MS Office, not starter.
The problem with these other versions is that they don’t have the full MS Word function. In normal use, I think they then download the bits they don’t have, as you try to use a new function.
But, when these ‘missing’ bits are used via the Word APIs (as eaDocX does) then Word doesn’t download them, and there’s nothing we can do to fix this.

[eadocX Support]

New version, with fix for Attributes & Operation/methods, uploaded as 3.0.3.1
Thanks

[eadocX Support]

I’ve also noticed some odd behaviour from Word, where it change widths of tables. I think this is Mr. Gates ‘helping’, in that way that he sometimes does. I;ve tried telling him not to, by making the column widths ‘fixed’ but he seems to ignore this is the HTML we send to Word.
If it’s a serious problem, then post an example, and I’ll have a look.

[eadocX Support]

Ok – done that – fix is available in 3.0.3

[eadocX Support]

Ok – I guess i’d better get going on this one!

[eadocX Support]

Yes.
If you save the profile from the first document (eaDocX | File | Save document profile) then load it into the second (eaDocX | File |Load Profile). Then, the formatting for all elements will move form one to the other, including Conditional Formatting rules.
This is a good way to make two documents look the same.
Alternative is to just save document 1 as document 2 (i.e. adocument copy) and the document 2 will start out with exactly the same Profile as doc1. This is how I usually do it.

[eadocX Support]

The number is measure of Pixels.
It comes from the fact that eaDocX inserts text into Word as HTML, and it’s the same width=xxx variable which you might use when specifying an HTML table.
It turns out that, by trial an error, the width of an A4 Portrait page, with Word default margins and gutter sizes, is about 600, which is why the user interface uses that as a guide when warning you how wide your tables are.

[eadocX Support]

Ah – I see. I will change ASAP. I will update this item when I know which release it’ll be in

[eadocX Support]

Short answer – no.
Long answer:
The way eaDocX works is that it creates tables by reference back to the original element – in your case the Actor.
Each column in the table is then created with reference to that Actor: either a single-hop relationship, or a multi-hop one, but it all starts with the ‘source’ element.
The problem you face is not unusual for a complex model. The simple solution, which I admit isn’t exactly what you want, is to have multiple tables, and use eaDocX hyperlinking to join them.
So, a table of Actors and their Activities, with each Activity being a hyperlink to…
then
…elsewhere in the document,
A table of Actvities, and the Application Components they are linked to. And even a link back to the actors.

Alternative is to use multi-hop, and show all the Application Components for the Actor.

The hybrid which you’re asking for, which would be a MUCH more complex table (rememeber it has to work for any possible model structure) , with some cells being split, has proved too complicated to implement.

[eadocX Support]

Do you mean outputting the data type of the TV. As in the value in the Type=Boolean etc in the definition of the TV ?

[eadocX Support]

You’re quite correct!
I will add Project.Task.Status as a attribute in the next build of v3 – probably at the end of the day today.It will be v3.0.2.04
Thanks

[Author]

Posts