eadocX Support

[eadocX Support]

Fixed in 3.3.11. Thanks

• This reply was modified 11 years, 3 months ago by eadocX Support.

[eadocX Support]

Fixed in 3.3.11

• This reply was modified 11 years, 3 months ago by eadocX Support.

[eadocX Support]

I remember this one – somebody spotted this on your course.
Looks like my holiday weekend is all nicely mapped out!

[eadocX Support]

When the hyperlink jumps to the top of the document, that means that the hyperlink which eaDocX has created isn’t understood by Word i.e. its a link to something which doesn’t exist. (eaDocX error)
Just to confirm I’ve got this right before I try to reproduce it:
– In EA you are adding a link in the ‘Uses’ column of a scenario step, and adding a ‘Link to an existing element’.
– where the target element is printed Inline with the name in the heading, it’s ok.
– where the target element is printed in some other way, it doesn’t work ?

[eadocX Support]

I can reproduce this as well.
Thing is Jeff, nothing bad seems to happen afterwards: I still get a decent-looking list of documents! Do you get the ‘Documents in this model’ list ?
I will investigate.

[eadocX Support]

Any chance of sending a little XMI, to support@ ?

[eadocX Support]

Hi Jeff,
The Repository Setting for the location of the DM document data is just a way for you to set a sensible default e.g. ‘New Documents’. It’s so that, if you use all the defaults, eaDocX knows where in your repository to save the DM data.
I generally create all the first versions of my documents in the default location, then move them to other Packages.
I suggest having personal Packages, for each users’ work-in-progress documents, and ‘ready for review’ and ‘final’ Packages as well, and repeat these per-project for multi-project repositories. Moving the eaDocX Document element around does affect how eaDocX DM works: all versions of that document will be creates as children of that element, wherever you’ve put it.
So really, organise your eaDocX DM Packages however you want!

[eadocX Support]

Thanks Rick – I’ve backed-out v3.3.10.5, so current version is still 3.3.10.4

[eadocX Support]

Ah – thats makes more sense: it’s looking for T_OBJECT in a DB which contains only t_object, so it’s not just the t_objectproperties table which needs to be lower-case – it’s all of them.
This is a much more disruptive change: I need to change ALL the places where I issue direct SQL, to have lower-case table names, which is a load of calls, all of which need to be regression tested, and some of them only get used in some obscure situations.
As I can’t reproduce this on a local mySQL DBMS, I can’t then test it for you.
Do you think it’s become case-sensitive due to being implemented on a remote Linux machine? Have you tried with a local Windows mySQL?
Is this the kind of thing which Linux machines tend to do?
Any chance of you trying a schema change, to make a couple of tables upper-case, and check that EA doesn’t mind?

[eadocX Support]

OK Rick – done that. It’s on the website as 3.3.10.5. See if that does the trick.

[eadocX Support]

I’m as baffled as you.
I will add another fix, to change the table name to lower-case for mySQL, as my local mySQL implementation doesn’t seem to care whether its upper- or loer-case. This is all very odd, as eaDocX submits this SQL to EA, who sends it right off to the DBMS. eadocX uses the same style of SQL – upper-case table names – for all the direct-to-DBMS calls, so it’s surprising that just this one to t_objectproperties causes problems.

[eadocX Support]

I think I made everything upper case as that works OK with SQLServer and Oracle.
Can you manage to do a Quick Document, because that uses lots of other tables which are all addressed using upper-case table names.

[eadocX Support]

I’ve found the place where you’re having troubles. My test environment – which has mySQL running on the same Win7 machine as EA, doesn’t produce this error.
I’ve fixed it anyway, so the table no longer has a mixed-case name in the SQL. Hopefully this will fix your issue: I don’t have any way to tell!
Fix is built into v3.3.10.4 which is now available from eaDocX.com.

[eadocX Support]

Hi Heather,
Short answer – yes.
The only thing stopping me is finding an Microsoft Word API which tells me what the available dotx templates are. If anyone knows where to find this information, I’d code it tomorrow!

[eadocX Support]

There is still no work from Sparx about making the ‘split diagrams’ function available via the public API.
I have had a look at doing it manually (i.e. in eaDocX code) but it’s REALLY complicated: need to understand all the geometry of the whole diagram, and all the shapes and connectors.
So, until Sparx support it, this function will not be available.

Not that it helps you directly, but there’s lots of wisdom out there which suggest that any diagram which is so big that it needs multiple pages is possibly in need of simplification, into several smaller ones, which are easier for readers to understand.

[Author]

Posts