eadocX Support

[eadocX Support]

You’re right – the glossary doesn’t get created with the relevant Word tags to make it a table.
I have added this to the backlog for V4, which is now being designed.
…but I can’t promise it will make the first release 🙁

[eadocX Support]

When eaDocX imports a Profile, and you choose not to delete the existing ones (which we recommend) then it tries to only overwrite where it’s cure there is a match. This is not an exact science, as there are so many combinations of Profiles.
I suggest you choose the’delete existing’ option – safer.

[eadocX Support]

When you imported the Profile, what options did you choose ?

[eadocX Support]

Just re-tested this, and it looks fine here.
You’re using the same EA and eaDocX version as me.
What I did was:
– create some resource allocations in EA for an element
– choose eaDocX / eaDocX/ Open in Excel / Resources
– selected the columns I wanted in eaDocX/Excel
– re-exported the data to excel.

[eadocX Support]

All this function does is tell work to hide/show hidden text. So, if the text inide the brackets is not ‘hidden’ style text, then this won’t work.
eaDocX tries to create a special Word paragraph style for this text, called something like eaDocXSection: if yuo have this, make sure it’s ‘hidden’ paragraph style.

[eadocX Support]

???

[eadocX Support]

What are the differences?
You can compare the two documents using the standard Word ‘compare documents’ function. If you can then post what the differences are, we can investigate.

[eadocX Support]

Ah – my bad. I promoted the wrong file.
I have added it to a new release – 3.9.5.1, now on the server. Please can you download and try it, and verify that it’s OK for you?
Thanks
Ian

[eadocX Support]

Whoops – quite so – CANNOT use a script.:-)
My scripts are all in a ‘normal’ script group, which seems to make them live in the t_script table of the repository. That’s where eaDocX looks for scripts.

[eadocX Support]

The answer is quite simple. You told eaDocX to print the Use Case twice – so it did that.
– first time, you told eaDocX to print the diagram as ‘diagram and contents’. This means you will get (1) the diagram image and (2) all the element in that diagram, printed in the way you specified in the profile for Use Cases. In your case, this is a quite strange: you don’t print the name of the use cases, just it’s pre- and post conditions.

– Later in the document, eaDocX finds the actual use case, in the “Eisen & Condities” package. So, it prints the use case again, using the same profile.

To confuse things a bit more, your document also uses a ‘Diagram Filter’ setting, which tells ALL UseCase diagrams to print as ‘diagram+contents’, so you need to switch that off as well

Solution – reset the ‘diagram filter’, and make the diagram ‘print as normal’.

[eadocX Support]

Quite simple – add an eaDocX Element Report, using the top-level package as the source.
It will collect all the elements of the type/stereotype you need, and even print in a different way from other parts of the document.

[eadocX Support]

Ok – so there is no way we eaDocX can do that.
Normally, if you need really specialized generation of documents, you can use an eaDocX/EA script – a kind of mini-generator. eaDocX passes the script the identity of the element(s) you are trying to generate, and you can do whatever you like, so long as you send eaDocX back a simple string of HTML.
The exception to this is for generating diagrams, because this doesn’t just put some HTML into the document: it does a copy/paste of the diagram image, as well as setting various Word features so that, for example, diagram numbering works.
So this is why you can use a script to generate diagrams.

[eadocX Support]

Hi Markus,
There is also the option to print diagram.notes for any diagram – just choose that option under eaDocX / Tools / Options and Settings / Diagram / Print notes for Diagrams.
This will add the diagram notes after the diagram title.
Is that what you need ?

[eadocX Support]

At the moment, you can’t add your own caption text, but you can have a title above the table. But I’ll look into using the same text as a caption instead.
We’re just about the start work on the next eaDocX release, but I’ll see what I can do in the short term.

[eadocX Support]

Ah – that’s it. We stopped supporting Office 2003 a few releases ago.

[Author]

Posts