Perhaps I can clarify how we think you might use eaDocX
“I need to create a document for each use case…” – this would be a very strange way to use eaDocX, especially as you have 1000 Use Cases!!
What you can do is create a document, and design an eaDocX Profile for Use Cases, which prints them in the way you want them to look. Do the same for Systems, processes, Requirements etc. Then choose a Package which contains some use cases etc, and generate the document. All the use cases/Processes/etc will then print in the same style.
So you can print 10, 100 or 1000 use cases, all in 1 document, and they will look the same.
If you save this document as a Word Template, then the eaDocX Profile will save with it. To create a new document containing different EA content, create a new Word Document, tell eaDocX which is your new EA Package, and generate. Or just save the document with a new name, and similarly specify the new EA Package.
You are correct that the definition of the document is not kept in the EA model: that way, a user using eaDocX does not need write-access to the model.
However, if you use the Document Management feature of eaDocX Corporate Edition, each time someone generates a document, you can keep a reference to that document in the model (this does need write-access) so that everyone can see what documents have been produced, and, if they are all saved on a shared drive, can open and copy them to create new ones.
I hope this helps!
