eadocX Support

[eadocX Support]

Hi Andreas,
The simplest solution to this is to use all upper-case table names. This issue seems to happen when we install MySQL onto Linux servers, which seem to default to lower-case names AND also case about the case of any SQL which they receive. On Windows MySQL implementations – which is how we test MySQL – everything is OK, as the Windows implementation seems to be relaxed about the case of table names.
Are you using Linux?

[eadocX Support]

If your Requirement elements are of the same stereotype the you could write a little script to output some raw HTML, which eaDocX will include.
You can even make it use your chosen style e.g:

element.name

element.notes

[eadocX Support]

Short answer – no.
With Linked Documents, all that eaDocX can do is to save the document as an RTF, then embed that document into Word. It was a choice of 1 on both sides: it’s the only ways EA will deliver the Linked Document, and the only way Word will allow it to be inserted.

[eadocX Support]

Sorry chaps – but nothing we can do. Must be a change within Word 2013. WE haven’t changed this bit of eaDocX for years.

[eadocX Support]

I’ll have a look at making a diagram-specific option.

The other point about the UI is to make sure we don’t end up with a UI which is cluttered up with every little twiddly requirement which anyone has ever asked for. Hence introducing scripting support in v3.4, so the serious eaDocX-er can create wild and wonderful output, if they have the time & skills.
Doesn’t mean no more new stuff!

[eadocX Support]

You can already do the last bit.
There’s a setting in the Document settings, Diagram Settings, Word style for Diagram Picture.
If you create a new word paragraph style which is centered, left or right justified, then this will be applied to the image.
As for the first bit, I’m still trying to persuade Sparx to open up the diagram API to let eaDocX use some of the features which they use in the RTF generator, like splitting large diagrams. I’ll have a look a simple scaling, but it’s yet another addition to what’s becoming a crowded eaDocX UI.

[eadocX Support]

Hi Igor,
I’m not surprised you’re have problems understanding this: it’s one of the more complicated bits of EA, and also of eaDocX!
Most Element types can have what eaDocX calls ‘sub-elements’. Sub-elements are the things which are like an element, but are children of the parent element. Examples are Scenarios, Internal test cases, Internal Risks etc. You can see these in the Element Browser window in EA.
You’ve found the sub-element ‘Change’ hidden in EA under the ‘Maintenance’ folder in the Element Browser, along with ‘Defects, Issues and Tasks’. These used to be called ‘Issues’, so that’s what eaDocX still calls them, and they are all 4 saved in the same way in EA, so eaDocX treats them as sub-elements called ‘Element Issue’ (we say ‘ELEMENT issue, so they don’t get confused with the first-class ‘thing’ called Issue – which is what I always use)
So, if you create a profile for your element – e.g. ‘Class’, then go to the ‘sub-elements’ page of the Profile, one item in the drop-down list is ‘Element Issues’, which is where your Change sub-elements will be.
As you add this to the Profile for ‘Class’, eaDocX will create a default Profile for ‘Element Issue’, which you can then edit.

[eadocX Support]

No.
If you change the setting in the eaDocX Repository Settings, then the Profile Auto-generate WILL be restricted to just the elements in the package. Plus a couple more like ‘Term’.
Anyway, I’m not sure why you care about this so much. If the Auto-generate creates a Profile made from ALL the elements in the Model, the document will look EXACTLY the same! It’s just the Profile will have a few more things in it, which don’t get used by the document.

[eadocX Support]

Maintenance releases are every few weeks.

[eadocX Support]

In my version, checking this box creates an error, and I can see why!
It SHOULD create a file, in the same place as the source file, called _saved_profile.xml.
I will fix for next maintenance release.

[eadocX Support]

Sometimes you want to make sure that the profile being imported will totally replace the existing one: sometime you might want to add to it. This option lets you choose which one.

[eadocX Support]

For reasons we can’t quite remember, there’s an additional override on this option in the eaDocX Repository Settings: ‘Use Metamodel for Package’ = true.
We think this was to ensure backwards compatibility at some point, but that was a few releases ago.
The option is really used when you create a Quick Document, to determine the scope of the auto-profile-generation.
Sorry to mislead you !

[eadocX Support]

No promises, but I assume you’d like this to be an option on any attribute of any element/stereotype? Not sure where this would go in the UI.

[eadocX Support]

OK – I understand, but sorry, that’s the way eaDocX does things. No possibility to change, this as it would be impossible to make it work for existing customers

[eadocX Support]

When you say ‘Attribute’ do you mean it in the EA sense -and Attribute of a class – or in the eaDocX sense, which is any piece of data about and EA Element?

[Author]

Posts