Forum Replies Created
-
AuthorPosts
-
eadocX SupportParticipant
We don’t recommend one, but we test with Oracle, SQLServer and MySQL, as well as .EAP
eadocX SupportParticipantEA / Extensions / eaDocX / Help / Enable Technical logging.
Also, we don’t do any testing with PostgreSQL database – you are the first eaDocX customer to use it, so it’s not something we plan to support.
- This reply was modified 10 years, 6 months ago by eadocX Support.
eadocX SupportParticipantAre you by any chance also using other EA Add-ins as well as eaDocX? This is currently causing problems for other users (e.g. EANavigator or Screen Architect?)
eadocX SupportParticipantNorman,
Thanks for the sample data: at least we’re both looking at the same model now 🙂
I have tried to reproduce the error (with eaDocX v3.4) but so far it all seems to work.
Are you using 3.4 as well?
I can make it work with the back-hyperlink from Use Case to Requirement printed either as simple inline attribute, like
Realizes Requirements: Requirement1, Requirement2, Requirement3
or as an inline table, which produces much the same result, only with the three hyperlinks in a table separated by line-feed/CR.So I can only think it’s because we’re using different code versions?
eadocX SupportParticipantLooks like there are only the default elements in that list. eaDocX has failed to read your database to find all the element types which you have used!
What DBMS do you use, or is this from an .EAP?
Also, there is a technical trace: please can you enable this, and try again to do what you want, then send me the trace results – this lets me look into what eaDocX is doing.eadocX SupportParticipanteasiest way is to put the diagrams into different packages.
eadocX SupportParticipanton the Profile tab, click ‘Add Element’, then choose Actor from the drop-down.
All the eaDocX drop-down menus which list element types look into your model, and list only those element types which are in your model, not all the ones which EA allows.
So it can’t find any Actor elements.- This reply was modified 10 years, 6 months ago by eadocX Support.
eadocX SupportParticipantI tried to replicate this issue:
- Created the three requirements and the use case, linked them with a Realization connector
- Created a QuickDocument from the package, which made both the Use Case and the Requirements in tables, with correct hyperlinks, as per your ‘working’ example
- Change the Profile of the Use Case to be inline. eaDocX copied the profile across from table to Inline, so i didn’t change anything
- re-generated – hyperlinks were present
What are you doing that’s different from this ?
eadocX SupportParticipantAll of these issues are described in detail in the help, which is available either from the application, from the eaDocX.com website or in a downloadable PDF>
eadocX SupportParticipantWe don’t know of any problems with eaDocX 3.4 and Windows 8 at the moment.
The information in the System Requirements section was put there when Windows 8 was first available, before we had chance to regression test it.
Have you tried it on your Win8 configuration ?eadocX SupportParticipantWhen eaDocX accesses the EA repository directly – which it has to do because there aren’t the required APIs in EA – it uses upper-case table names. This works OK in all the major DBMSs, when they are configured normally. We’ve tried it with SQLServer, Oracle, MySQL and EAP files.
BUT, we know that it is possible to configure some DBMSs so that they are case sensitive, so, we issue SQL to look at T_OBJECTS, and it only has a t_objects table.
We have so far not found a pattern to when this happens, and it would be a MAJOR change to eaDocX to allow for case-sensitive SQL, as we will have to parse the results in mixed case as well.
So, have a look at the case sensitivity of your DBMS.
Also, EA itself seems to be OK with this, it’s just SQL issues via EA which has the problem.- This reply was modified 10 years, 6 months ago by eadocX Support.
eadocX SupportParticipantI can’t reproduce the issue.
– I created a document, with Requirement elements printing in a table, in normal Portrait format
– generated it OK
– changed the profile to print the table as Landscape
– generated ok
– exited the document
– re-opened it
– generated again – came out correctly in Landscape
Is this what you’re doing?eadocX SupportParticipantNot at the moment.
eadocX SupportParticipantHi Szymon
To print the contents of a diagram, just select the diagram in the eaDocX Preview, and select ‘Diagram Options’, ‘Diagram and all contents’.
This will print both, using the formatting which is defined in the profile for the document.eadocX SupportParticipantHi Simone,
Sorry for not answering your question – we’ve been out of the office for a few days, and I missed this posting. Glad that you have fixed it – we’ll try to do better next time 🙁 -
AuthorPosts
Download a free trial
Download eaTeamWorks today for several free for life features, plus no obligation, 30-day trials of all the products: eaDocX, ea Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why we sell the world’s best-selling Enterprise Architect extension.
Download