Administrator

[Administrator]

Thanks for running the installation inspector – always a good idea.
It looks like eaDocX can’t find Word any more – have you just changed your Office installation ?

[Administrator]

More likely is that eaDocX is trying to interpret the ‘less than’ character as the start of an HTML tag.
I’m guessing that this comes in a ‘notes’ field – is that right ?

[Administrator]

I probably should have explained this better. The attribute prints the names of all child diagrams of the element.
Though I think it would be useful to have another attribute which, as you suggest, prints the places where the element occurs. I’ll have a look at that…

[Administrator]

Interesting. Never seen this before.
eaDocX pulls the image from EA by asking for a JPEG of the whole diagram.
If you copy/paste the diagram image into, say, Word, does the same thing happen?

[Administrator]

I’m out of the office at the moment, so can’t look at the code, but from memory MX does not treat Boundary objects as ‘real’ objects, as they are mostly used on diagrams just a boxes, to make things look neat.
I have a feeling that in Archimate 3 this may not be true. Is the Archimate ‘Group’ idea based on the Sparx ‘boundary’ ? If so, than maybe I need to change how this works.

[Administrator]

This also sounds like a Word paragraph style issue.
The section marks are created by eaDocX with a Word style which says ‘invisible’, which means they can be seen only where you switch on ‘shown invisible text’ – which is what the ‘toggle section marks’ command does.
Probably means there is something in Word which is making this ‘invisible’ text visible.

[Administrator]

I’ve never tried calling into an addin from inside an ea script. Is this possible?
If so, what would the eaDocX API call look like? That is, what parameters would you expect to pass?
We have the beginnings of this function in the Auto-template capability, so internally we might have most of the moving parts.

[Administrator]

I have fixed (1) – table-of-tables will now update correctly.
As for (2), where should eaDocX get the caption from? The field which is ‘table title’ is used to add an additional heading above each table of that type, using this text as the heading text. But this will be the same text for all tables with elements of that type. So not much use as a table caption.
To explain, the table title lets someone print

Some Requirements
==================
(a table of requirements)
Table 1.

…then later in the document
Some Requirements
=================
(another table of requirements)
Table 42

etc.

So, if I used the same text for the table caption, the table-of-tables would say:

Table 1 – Some Requiements…….page 1
Table 42- Some Requirements ……page 99
etc

Is this what you want ?
I’ll look at the glossary table..

[Administrator]

Do you mean elements, or element types? If its types, then both eaDocX and eaXL only show element types in the current model.

[Administrator]

Worksheet settings

[Administrator]

Quite right – I keep meaning to hook this up, but it looks like I forgot.:-(
I will put it back in for the final release. Sorry for the inconvenience.

[Administrator]

I will be issuing a second beta this week of V4, so my expection is for a production version by the end of May 2018.

[Administrator]

Yes, but you won’t get notified of updates.

[Administrator]

please see
https://store.eadocx.com/forum/2-eadocx-queries/1467-failed-to-open-document?start=6
and, if you have Skype for Business:
https://store.eadocx.com/forum/2-eadocx-queries/1312-error-message-when-trying-to-create-open-document?start=6#3009

Always a good idea to search the forum before asking a new question.

[Administrator]

When eaXL exports data into Excel from EA, it deletes row which are already there. So if your validation is in those cells, it will delete them.
We have to do this, for the case where the number of rows exported DECREASES form one export to the next.
We always suggest that you leave the eaXL worksheets alone, and if you need to create additional function in the workbook, add it into new worksheets which eaXL won’t touch. This is how we create charts and tables.
Adding validation logic into eaXL worksheets is not a use case which we support.

[Author]

Posts