eadocX Support

[eadocX Support]

I’ve tried to reproduce this, but I can’t.
Have you tried getting eaDocX to create a Quick Document from a bit of your model? This will create Profile for everything it finds, and, if there is a diagram as a child of any element, it will add those diagrams to the default profile. You can then compare that Profile with yours.
Apart from that, I don’t quite know what to suggest.

[eadocX Support]

I’d still try the above steps, in case it really is a comms error.
Just as likely is that this is the systemic error in the LSA, which causes it to fail when maintenance is applied to the server it’s running on. Not the fault of the maintenance – crypto application just hasn’t kept up with changes to how Windows does things.
We’re seriously thinking of withdrawing floating licences altogether – they are >50% of the issues we see with eaDocX, which is really annoying, as we thought we were being smart in buying-in the crypto from someone else.
Plan B is to offer organisational licences instead, which is much simpler for users.
Plan C is to offer a free exchange of fixed licences instead of floating ones: 1:4.

[eadocX Support]

you can create a Model View in EA, then make a section from the Model View.
See the help for all the details.
https://store.eadocx.com/help/index.html?create_an_eadocx_document_usin.htm

[eadocX Support]

see https://store.eadocx.com/help/index.html?adding_dm_information_to_the_r.htm

[eadocX Support]

Di you find this in the help ? There are lots of parameters tou can add, both from Word-defined variables, and eaDocX ones as well.
You do it by changing the Profile for the DocumentInformation type.

[eadocX Support]

Hi Markus,
This is a really interesting question – I’d totally forgotten about the Word Master Documents idea, but it looks to be the right solution for your requirements.
So I went back and looked-up how Word Master documents work, and they just seem to ‘include’ other documents. Getting the heading levels to match-up is a problem, but I think I made it work.
What I did:

1. created a Word master document, (outside eaDocX), and added some hand-written content
2. added two Word sub-documents
3. opened each of the sub-documents in eaDocX, and added some EA content in eaDocX sections
4. generated each of the sub-documents
5. went back into the master documents, and I could see the non-EA and EA content in all the documents.

OK, so not a surprise – an eaDocX document is just a Word document, with your settings saved inside it.

Question is – will this change how you get to use eaDocX?
Here are some of the things which will happen if you follow this approach.
Key idea is that, when generating each sub-document, eaDocX will treat it as a stand-alone document. This is just based on knowledge of eaDocX – I haven’t tested each one:

1. you will only get cross-reference hyperlinks within a sub-document. There won’t be any hyperlinks between sub-documents. This will affect the readability and coherence of your document
2. Features like ‘cross reference reports’ will only work within a sub-document, so if anyone uses them, you may get duplication
3. You’ll need to make sure the heading numbering levels are consistent across the sub-docs, but that’s the case anyway, and at least eaDocX lets you control the top-level heading number
4. Figure and table numbering may not work. We create proper figure- and table-number tags in Word, so I’m hopeful that when Word merges the documents together, Word will resolve these correctly
5. Glossary will be per sub-doc, unless you make the master document into an eaDocX document, and give it a single section which is a glossary. Then it MIGHT detect all the contents in sub-documents, and create the correct glossary list. I’m not confident about this one

These are all the issues which come to mind – I have a feeling there will be more.
But overall, if you bear in mind these restrictions, then you should be able to make a Word master document from eaDocX sub-documents.
‘hope this help – if you do get this working, can ask you to please update this entry, so others can benefit form your experience. We might even include this idea in the help for the next version.
Ian

[eadocX Support]

Excellent answer Neil – thanks

[eadocX Support]

Are you using the latest version of eaDocX.
WE had a customer with this error a few weeks back, and we traced the issue to some content which had been deleted from the EA model, and eaDocX didn’t handle it well.
We fixed that in the latest release, so, if that is the problem (which fits if you have other documents which are ok) then please try the latest version.

[eadocX Support]

I just tried this again, and I can seem to create Conditional Formatting rules for missing attributes (ones which have a value of ‘n/a’ because they are not present) for both table and inline formatting. Is this what you are doing ?
My rules were both ‘text, same as’ ‘n/a’ ‘MISSING VALUE’ (color red)

[eadocX Support]

Ah – my mistake -I uploaded the wrong file. See new version 3.9.4.4.
Sorry!

[eadocX Support]

OK – fixed in version 3.9.4.3. There were also problems in fetching details of Model Views, and existing relationship matrices, so I fixed those at the same time. Also re-tested with Oracle and EAP files, and all OK. All stuff which requires different SQL for the different DBMSs. I really wish that Sparx could fix this in their SQl API.

[eadocX Support]

ah – I have just run the ests using a Postgres Db, and they failed 🙁 I will fix today.

[eadocX Support]

eaDocX looks in the t_script table in the EA model, whether that is in the EAP file, or in a shared database.
Ah – an idea – which DBMS are you using? This uses some SQL, and maybe that’s broken?

[eadocX Support]

eaDocX treats the cell contents as a simple string, for the purposes of Conditional Formatting. How you have managed to make it the ‘many-end of a 1-to-many relationship’ is beyond me.

[eadocX Support]

eaDocX is usually quite good at detecting when a Tagged Value is really the GUID of something else. I’ve just checked, and eaDocX tries to match these GUIDs with GUIDs for elements, attributes, methods and packages. If it finds one, it prints the Name of the ‘thing’.
Is this what you want ?

[Author]

Posts