Document Management Settings |
  
|
Document Management Settings |
|
The main way you can control how eaDocX creates your document is by adding sections and configuring the Profile.
But there are also some settings which are not part of the profile, but which also affect what your document will look like.
These settings at three levels:
1.Document-level. These just apply to a single document. If the document is copied, then these settings will be copied to. Document-level settings will ALWAYS override Repository- or Application-level settings, but if you don't specify a setting value for a document, it will inherit it from a Repository- or Application-level setting.
Examples are:
▪the location where a document is saved. This is unique to each document, but for new ones, eaDocX will use a Repository- or Application default
▪roles played by particular people in this document.
2.Repository level. These are saved with your EA repository, and so may be inherited with each document which is created from that repository.
Examples are:
▪Location where eaDocX Document elements will be saved
3.Application level. These are settings which you'll probably want to keep the same for all repositories and documents.
Examples are:
▪Role names. These will tend to be company- or national-language specific.
Some settings may be defined at each level, for example, whether Document Management is enabled.
Setting |
Explanation |
Document-level |
Repository-level |
Application |
eaDocX Document Management Enabled |
If DM is enabled for a document, eaDocX will prompt you to up-version the document each time you re-generate |
•Enabled •Disabled If value is Disabled, user may set value to Enabled.
|
•Enabled •Disabled If value is Disabled, user may set value to Enabled. |
(none) |
Document File Location |
Where documents are to be saved - a file location on your computer. |
Specific setting for each document. If no Repository- or Application default is available, then user will be prompted for a location. This will then become the Repository-level default. |
Default may be specified at repository level |
(none) |
Save documents Internally |
Lets you save your eaDocX DM document inside your EA model. |
Specific setting for each document will over-ride Repository setting |
Default= false, that is, store Word documents as files on your file system, as normal. |
|
EA Document Package |
EA Package where eaDocX will save eaDocX document- and version-elements. |
(none) |
Always specified at repository level |
(none) |
Document Approval types |
This the set of names for approval status, which you may use for a document. May be different from the built-in defaults of 'Approved' etc, which you may translate to suit your project or national language. |
(none) |
(none) |
Always specified at Application level. |
EA Roles Package |
EA Package where eaDocX will look for lists of people who may assume roles in a document |
(none) |
Always specified at repository level |
(none) |
Document role types |
This the set of names of roles, which you may use for a document. May be different from the built-in defaults of 'Approver' etc, which you may translate to suit your project or national language. |
(none) |
(none) |
Always specified at Application level. |
Roles for a document |
Exactly who is playing what role in a document |
Always document-specific |
(none) |
(none) |