Forum Replies Created
-
AuthorPosts
-
eadocX Support
ParticipantHappy days.
I have updated our ‘system requirements’ to warn people off of 64-bit office 2013. I think I used 32 bit when I did the testing, but I’ll have to look at the VM to make sure….Very odd.eadocX Support
ParticipantIf I understood correctly, you’re creating a table, one line per element, then in one cell printing an attribute of (some) related elements.
I’ve just tried this, and in a table it prints as a newline-separated list. If printed Inline, the lists will be comma separated.
…so I guess I don’t understand your question…:-)eadocX Support
ParticipantAh – you want the bit of 3.4 i’m just finishing-off: it will let you write mini-eaDocX generators using simple EA Scripts, so you can use all your imagination when creating new formatting styles. If you send an example of what you want – to enquiries@eadocx, then I’ll use it as another test case…
eadocX Support
ParticipantThis is a good suggestion, but one which would have far-reaching implications inside of eaDocX.
We introduced the capability to copy the Profile of one stereotype to another, in the last release, and it’s too late to get this into 3.4, but its a requirement which we’d love to deliver.eadocX Support
ParticipantSee https://store.eadocx.com/index.php?option=com_content&view=article&id=56:system-requirements&catid=41:faq&Itemid=405 for system requirements.
eadocX Support
ParticipantSorry about this. Our plan is to fix in v3.4, which should have a beta available in a couple of weeks. Sorry for the delay, be we’re now also regression testing with EA V11 as well….
eadocX Support
ParticipantAh – that sounds like you EA model has some data in it which eaDocX doesn’t like. Usually fixed by just doing an EA Project Integrity Check, which cleans up most dangly bits in your model.
eadocX Support
ParticipantWhat did the error say? Was it an eaDocX, and EA or a Word error ?
eadocX Support
ParticipantHi Paul,
Printing the notes of a diagram is currently enabled/disabled globally, not per-diagram or even per-diagram-stereotype.
A future release (not 3.4 – sometime after that) may allow for more elaborate customisation of diagram options, but it didn’t make it into 3.4 – just too much to do.eadocX Support
ParticipantOh yes – it’s a bug.
Fixed in 3.4.
ThankseadocX Support
ParticipantHi Phillip,
have you tried exporting the Profile, and importing it into the new document ?eadocX Support
ParticipantWhat is the symptom? Does eaDocX produce anything in the Trace ? Can you send a (sanitised) document & XMI and I will try to reproduce your issue.
eadocX Support
Participant…
-
This reply was modified 11 years ago by
eadocX Support.
eadocX Support
ParticipantThis has been fixed in eDocX 3.4 – please see website to check when the Beta is available
-
This reply was modified 11 years ago by
eadocX Support.
eadocX Support
ParticipantIt sounds like you have done the hard part! – defining the relationships between the UseCase and the Requirement, and printing the Alias of the Requirement.
To get a hyperlink to the Requirement, just edit the ‘Attribute of Related Element’ to print ‘Alias – Hyperlinked’ instead of ‘Alias’ which yo have at the moment: it’s at the top of the list of ‘Standard Attributes’. -
This reply was modified 11 years ago by
-
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