eadocX Support

[eadocX Support]

Strange…
Please can you email a little piece of your model to support@eadocx.com, and I’ll have a look. Adding hyperlinks in this way isn’t something we’ve seen before, so not surprised it’s a bit odd.
Ian

[eadocX Support]

We have >250 customers in 20 countries.
This is the first time this problem has occurred.
Please ask your questions nicely, and we will do our best to help.

The test results indicate that eaDocX can’t talk to your Word instance. This is impossible for us to test, as we don’t know what your environment is. In order to function, eaDocX needs to talk to both EA and Word, both using their standard APIs – that’s what this test checks for.
Does your machine setup allow you to talk to the Word API?

[eadocX Support]

Seems like a fairly serious failure – not at all typical of what all our other customers experience.
What’s this TRIM extension you mention? Might it make a difference to how Word behaves?
Can you send more details to support@eadocx.com – such as a little piece of your .EAP file, Word document, and this extension, and we’ll investigate further.

[eadocX Support]

Problem indentified and fixed.
Was in the printing of Scenario Steps, where we have to maintain our own cache, to overcome lack of Sparx APIs.

Fix in is V3.2.3.2, dated today.

Thanks

[eadocX Support]

If you can send an XMI fragment of your model (with any secret bits taken out) and a simple document, then I can reproduce the problem.
Please mail to support@eadocx.com – these kinds of problem are our #1 priority!
Thanks

[eadocX Support]

Part-solution is now available in 3.2.3.
I’ve added ClassifierName as an extra attribute, so it can be used as title (for inline printing) or column in any table.

I’ll follow this with adding InstanceClassifier as an additional relationship, so that other attributes of the IC can be printed, but this is more complicated. This is captured as feature ref #118.

[eadocX Support]

Try documenting the Class as Inline, then you can have sub-tables for the associated classes, or hyperlinks to them, or inline tables. Try inporting the ‘Class, Dat and State’ build-in profile: that’s a good start.

[eadocX Support]

I can see an attribute called ‘Type’, which seems to work.
..but I’m wearing my glasses..:-)

[eadocX Support]

Interesting idea – makes it much more efficient to print a sparse matrix.
…but this would be a new feature.
I guess there would need to be ‘omit empty rows’ (and columns) options on the definition of the matrix report.
I’ll add this to the feature request list for v3.3, but that list is already long…
Thanks

[eadocX Support]

Please can you send a small XMI & document to support@eadocx.com, so we can reproduce the problem, and we will look at it as soon as possible.
Thanks

[eadocX Support]

This looks like a useful feature, so it’s next on the ‘to do’ list.
I’ll re-post when the solution is available: should be this week or next.

[eadocX Support]

“N/A” is the eaDocX way of saying ‘I don’t know what to do’. Also knowns as a graceful failure error!

Can you send a little XMI & document which will let us reproduce the error, to support@eadocx.com, and we’ll have a look right away.

[eadocX Support]

This is a recurring issue!
We keep changing our minds on this one: we get the generator to remove extra lines in some cases, when then makes other cases look untidy, and we put them back.
Spaces after diagrams is a good example: if they aren’t there, we think it makes the next bit of text look too close, so we added an extra space, which clearly isn;t what you want.

Not sure what to do about this one. We could remove ALL extra spaces, then leave it to you to change Word styles to add ‘space before’ to fix it, but that can make the rest of the document look TOO spaced out.

What do you think ?

[eadocX Support]

Can’t print it exactly that way.
You could try using the inline tables function, which allows for tables of different shapes & sizes.
A horizontal inline table would get close: it has the name of the attributes on the top line, then the value of each attribute below.

We have always avoided merging table cells, which is I think what you want. It just makes the eaDocX user interface really complicated, and there’s enough stuff there already. It’s what allows eaDocX the generate Quick Documents which look reasonable.
Thanks

[eadocX Support]

In the Scenario Step profile, add an attribute called ‘Linked Elements’.

[Author]

Posts