eadocX Support

[eadocX Support]

You’re quite right – at least we rembered to document what actually got implemented.
This feature was added in response to a specific customer request, but it looks like you want even more!
Just so I’m clear – you’re talking about the hyperlinking which can go into a description field, which can point to elements, packages, diagrams etc, and you need to be able to say, for example, “see diagram42” where diagram 42 is a hyperlink to the referenced diagram.
Do you need all the different hyperlink types to work, or just diagrams ?
Ian

[eadocX Support]

well done!

[eadocX Support]

You’re right!
Someone has stolen Attribute.Type !
..but no fear, I’ve found it again, and put it back into 3.2.5.2, which is now on the website.
Sorry for the error
Ian

[eadocX Support]

Sorry I missed your last update.
I’m still not clear what you want your document to look like.
Can you say (1) what is the structure of this part of your model and (2) what do you want your document to look like.
Thanks

[eadocX Support]

Not sure this is a version-specific problem, but you should probably upgrade to V3.something anyway.
I tried opening the Word document outside of eaDocX, then un-ticked Word Options | Display | Show hidden text.
This seems to get respected, even when eaDocX opens & re-generates the documents.
We always make the hidden bookmarks visible, as that avoids people trying to add sections inside other sections.

[eadocX Support]

Admin rights are needed

[eadocX Support]

They certainly SHOULD work – that’s the same config I have on my machine!
If the installation has worked, then you should see a new option on the EA ‘Add-ins’ menu for eaDocX: if not, the install didn’t work.
If you can see this option, choose ‘Add-ins’ (‘Extensions’ for later EA versions) then eaDocX | Help | Check Installation.
This will run some simple checks to make sure eaDocX can talk to (1) EA and (2) Word.
If that fails, please let me know, and we’ll investigate further.
Problems like this are usually because of some security restrictions on how Word can be used, and are difficult for us to detect as we’re installing eaDocX.

[eadocX Support]

Whilst I agree with most of what you say, I think perhaps you’re asking the wrong people: we’re eaDocX, and we print whatever is in EA: perhaps you should direct your comments to the EA ‘feature request’ forum.
..but thanks for taking the time anyway!

[eadocX Support]

This may be an example of a known problem.
When EA first creates items in a Package, it doesn’t put them into the database with sequence number (1st, 2nd etc). Somehow, the EA UI seems to make it all OK.
Elements only get a sequence number when you change the order.
So, just move one item up the list, then back again, and EA will create an explicit sequence in the DB, which eaDocX can pick up.

[eadocX Support]

Sounds like a Friday panic- send an email to support@eadocx.com, and we can converse by some more efficient mechamism and get you moving again

[eadocX Support]

Can you enclose a close-up of the part of the Project Browser which shows your model structure, and I will investigate

[eadocX Support]

Just to summarise our offline conversations.
This looks to be a problem with the installation and/or security settings of you machine.
You quite rightly ran the Installation Verification test from the eaDocX Help, which fell-over when it tried to talk to Word.
This means eaDocX can’t talk to Word at all, via the Word API, so eaDocX just can’t work.
One possibility (which we’ve since discounted) is that you’re using one of the Word products which just downloads bit of Word as you need them. This is fine when the user uses Word via it’s UI, but doesn’t download the API function when eaDocX tries to call it.
So, it must be some other local security setting which is stopping eaDocX from talking to Word. Which is a shame, as they usually play so nicely together….

[eadocX Support]

Just tried this with v 3.2.3.4 and it seems to work ok, for both inline and table formatting.
I created the profile for the element type, then added Conditional Formatting, on both the relationship name and stereotype.
Can you send an example XMI and word document to Support@eadocx, and I’ll have a look.

[eadocX Support]

You can print ‘nested use cases’, though I personally never use them – not sure what it means for one use case to be ‘inside’ another.
Just get use cases to print their Children.

[eadocX Support]

I’m about to start doing some changes to the relationship matrix (due to some up-coming changes in EA) so I’ll add this to the list – sounds like a very sensible requirement 🙂

As for the diagram-only report, how would you want this to work? Search for elements of type ‘diagram’ (not really elements, but you get the idea I think), according to some criteria ? I’ll think about this – more complicated than the first requirement… If you think you know exactly what you want, then send me some more details about where you’d expect this extra function to be shown.

Ian

[Author]

Posts