Globally defined eFORMz configuration options
Note: For a list of files and folders in the eFORMz install, consult the following: eFORMz default files and folders
Server defined eFORMz configuration options are detailed below. The loading/processing of these various files is also described in the following outline.
eFORMzCfg*.xml
- Files only load if this configuration file is present.
- The file
eFORMzCfg.xml
must exist and cannot (should not) be edited as it is part of the version distribution. The user instance can be edited:eFORMzCfg_User.xml
. - Everything is relative to the main eFORMz directory.
- The files may contain any number of “file” references for other configuration files.
- Configuration files are loaded the first time they are referenced.
- Conflicting definitions overwrite previous definitions.
- The order of auto-loading is as follows:
- The first file to load is
eFORMzCfg.xml
. - The next file to load (if present) is
eFORMzCfg_User.xml
. - The third place to auto-load is any files matching
settings/eFORMz*.xml
.
- The first file to load is
- Sample file reference:
<File Name="Preview/eFORMzCfg_Preview.xml"/>
FontSpecs*.xml
- Only two instances can exist:
FontSpecs.xml
and the user-editable version,FontSpecs_User.xml
. - The file
FontSpecs.xml
must exist and cannot (should not) be edited as it is part of the version distribution.
- Only two instances can exist:
Printers.xml
- Only one instance can exist.
Archives.xml
- Only one instance can exist.
Databases.xml
- Only one instance can exist.