eadocX Support

[eadocX Support]

I’ll have a look at this – not part of the standard regression test suite 🙁

[eadocX Support]

No.
The Document Details is a single set of metadata about the document, and so can’t have stereotypes (it doesn’t exist in EA) and has one set of values for a document.

[eadocX Support]

I’m adding some additional trace function into the next maintenance release (3.6.2.5) , which will be available later today. Then let’s see what going on…

[eadocX Support]

I think so.

[eadocX Support]

We have decided that the medium-long term solution to this is to move away from our own Licence Server to using the Sparx one, now that Sparx have created a public API for us. But we have no timescale on when that will be implemented. Sorry

[eadocX Support]

1. The only difference between a Composition and Aggregation connector in the EA database is that Composition connectors have a column called ‘SubType’ set to ‘Strong’.
eaXL just populates the ‘Connector_Type’ column with whatever you specify: there doesn’t seem to be a ‘Composition’ Connector type, even though this is defined in EA’s list of valid connector types. So it looks like this is an EA ‘feature’ which we doesn’t deal with. Sorry.
Did you try making the connector type ‘Aggregation’ and the stereotype “Archimate_Aggregation’ ?

2. eaXL does not, and will never, delete any Element, Package or Connector – it’s just too easy to accidentally delete a big part of your model. We know, because we did it once!

• This reply was modified 9 years, 5 months ago by eadocX Support.

[eadocX Support]

Is Style2 a table style? Or a paragraph style? Used as you have done it here, eaDocX is expecting Style2 to be a table style.

[eadocX Support]

can you tell what the invalid file name is?
Can you then change it? Windows doesn’t like file names with some special characters….

[eadocX Support]

Children!
Always a problem…

[eadocX Support]

Hi Jan,
This was a feature which got dropped from the launched Collaboration Edition product, but we have a prototype of it working, and we plan to add it back into the product ASAP.
We have a choice, however, and would welcome your views:
– make it a feature which is called from your client machine, to your local machine’s email API
OR
– make a further integration from your Web Server to an email-sender. This makes the web server installation a little more complicated, but will enable some other stuff which we have planned.

Do you have a preference ?

[eadocX Support]

The only non-standard changes which eaDocX makes to your model is to put the settings which are repository-specific into the t_xref table, as a single row, which has an XML payload of all the settings.
So, if you do an XMI export of your whole model, the eaDocX Repository Settings will NOT be exported: you’d need to do an EA Model Transfer.
Other than that, when eaDocX Corporate/Collaboration editions create documents and document version information, or when Collaboration Edition saves Comments, Questions, Answers etc, these are all saved as plain EA Elements, which can be XMI’d into any other model. These are all viewable in your project browser.

[eadocX Support]

Try printing the package using Quick Document. That will usually find most things which are user that package, and under any child elements of the package.
Also, there look to be some Inline-printing elements with no titles – hence the blank after the Heading icon, so worth a look at those as well. Also make sure that whatever has your Activity Diagram as a child diagram has a profile to print its diagrams: in a Quick Document, packages print their diagrams, but I’m not sure if Elements do as well.

[eadocX Support]

Quite do! Don’t know how I missed that yesterday.
And moving the scenarios up & down does indeed show up in the database. But it doesn’t seem to change the sequence of the scenarios in the Structured Specification section – strange.Might be another case where changing the ordering using up/down adds a correct, explicit sequence to the items, just like it does with items below a Package.
I’m off on holiday all of next week, so I’ll get to look at this when I get back
Thanks

[eadocX Support]

Ah – you’re using an older EA version than me: are you on v11 or v10 ?
That bit of function you are using is not in V12 (and good thing too, IMHO)

• This reply was modified 9 years, 5 months ago by eadocX Support.

[eadocX Support]

Really? In my EA (V12 build 1212) those buttons don’t change the order of scenarios, just of the steps within a scenario. The order seems to be set by the step number where the alternate/exception starts, followed by a letter which seems to be based on the sequence in which the alt/ex was created

[Author]

Posts