eadocX Support

[eadocX Support]

As far as we know, the LSA does NOT run as a Windows service, as stated in the instructions (which we copied from the documentation for the Crypto framework which we use).
We will correct our documentation

[eadocX Support]

Could be lots of things. Without the document to look at, it’s hard to tell. if you’d like me to look, send it to support@eadocx.com

[eadocX Support]

Please can you re-try with eaDocX 3.8 and the new web server application (DDC 1.6+ required also)

[eadocX Support]

This function was shipped in version 3.7, but has been discontinued in v3.8, due to customer feedback. We don’t normally remove function form eaDocX, so i’ll explain why…

In Collaboration Edition, we allow you to email the reviewers of a document with a URL, which they can click to review the document.
In 3.7, this URL was document-version AND reviewer specific, so we built this email-sending function to make this easier.
Feedback from customers told us this this was too complicated: they were continually sending emails to each reviewer as each document version was issued.
So – using an idea from an early customer – in 3.8 we use the same URL for ALL versions of a document, for ALL users.
So, once you have sent users the URL for the document, they can bookmark it. Or, you can put the URL on to an intranet page, and it will be good for all versions.
We also added the capability to enable a document for ‘guest’ access, so people can access the document and add comment without being a named reviewer. This is good for documents which have already been approved, and where you’d like anyone who spots an error to be able to comment on it.
So, we no longer need this elaborate email-sending function (which was hard to set up anyway, as you are discovering).
We suggest you download v3.8 of eaDocX, and its new Web server.
Thanks

[eadocX Support]

There is no plan to make eaDocX – using the standard user interface – support elements which have multiple stereotypes.
You would need to use eaDocX scripting.

[eadocX Support]

Hi Doug,
I can’t reproduce this in Excel, UNLESS the Requirements (or any element type) don’t have an explicit EA sort order.
If you create a bunch of elements in EA, hey don’t automatically get a ‘sort order’ (TPos) attribute. So how Sparx manage to bring them back in the same order each time is a mystery.
To set the EA sort order for ALL the elements under a package, just move one of them up, then back down, using the green project browser up/down arrows. The EA PB doesn’t look any different, but in the database EA sets the TPos attribute, which Excel will preserve.

[eadocX Support]

it needs to be a 32-bit ODBC connection (we think this is because EA is still a 32 bit application).

[eadocX Support]

The solution is that I’m still trying to understand the postings in the above Sparx forum thread, which seem to say that Sparx don’t really know how this works, or if they do, they aren’t saying.
As this issue of Attributes/Operations being available for almost all EA element types (e.g. Use Case – what does a method of a Use Case mean??) then I guess people will use them.
So, reluctantly, we’re making a change to eaDocX so that any EA element can have attributes or operations. Should be in 3.8.4, which is being tested now.
Do you think this will solve your problem ?

[eadocX Support]

Can you try on a smaller model, to see if it’s something to do with a particular model, or something in your infrastructure.
(if you need more time for evaluation, send a mail to support@eadocx.com, and we’ll sort something out for you)

[eadocX Support]

There are lots of reasons why this might happen: Web server, ODBC, security, database…
For exactly this reason, we’ve tried to log everything that happens in the web server. So the place to look to find out more is in the logs files.
There are two, both in /Files/logs
1. logYYYY-MM-DD which is the general log, for all web server stuff
2. ODBCActivityLog, for finer detail on just the ODBC bits.
If you look in these logs, then you can see what happening. So far, we’ve always been able to figure out where the problem is using the information in the logs, even it it means Googling some stuff.

[eadocX Support]

The text inside the square brackets should be created in a Word paragraph style called ‘eaDocXSection’, which eaDocX makes ‘hidden’ (in word terms).
Selecting the ‘hide section marks’ option just toggles the Word option to ‘hide hidden text’: eaDocX normally makes hidden text visible, so that it’s easier to see where the sections start and end.
Something must be getting in the way of eaDocX creating that Word style: might be permissions in Word ?

[eadocX Support]

hmmm.
That’s big-ish.
I’ll beef-up our ‘big model’ test case, and see if that makes any difference.

[eadocX Support]

How many packages in your model? And which DBMS?
If you run out of time to evaluate eaDocX due to a bug in the code, then we will, of course, extend your trial for as long as you need.

[eadocX Support]

1. No. eaDocX only contacts eaDocX.com to see if updates are available, and to pass on urgent messages to users. The call also checks for the validity of the users’s key, to prevent fraud. Updates are never downloaded automatically – we don’t think it’s polite. If the call fails, the software continues to operate normally.

2. The eaDocX licence key is saved via Sparx, so it is physically located wherever Sparx choose to put it. The path you describe above looks right. Be aware that the the above path changes when you install new EA versions (hence the EA version number in the path), so users need to re-enter the eaDocX key when this happens. Again, a Sparx implementation.

[eadocX Support]

I’m sorry, but we don’t have any way to test eaDocX with Citrix, nor do we have any Citrix knowledge within the team.
The error you are seeing is passed to eaDocX by the Crypto sub-system, and, where they pass an unrecoverable error, we just just show it to you.

[Author]

Posts