Configuring Schema Options
This topic describes the configuration options available for managing and defining schema files.
Overview
Associating a schema to a document is required. By default, three schema files (xsd) are
supported by the solution.
- ExpereTxn: The base schema for the majority of documents and the default schema.
- VMPMISMO: The VMP Mismo schema is used primarily for documents supporting the Mortgage lending line of business.
- QuickDoc: The QuickDoc schema is used in conjunction with documents that are processed through the QuickDocs component to render eForms documents.
The configuration file contains records that define the available schema. The configuration
file is located in the default installation path. The configuration file is located in the installation
path. The default location (which can be modified) is:
C:\Program Files
(x86)\WKFS\Expere Administration Tools\RequirementsAdmin.exe.config
C:\Program Files\WKFS\Expere Administration Tools\RequirementsAdmin.exe.config In the
command line version of the tool, the config file is located:C:\Program Files
(x86)\WKFS\Expere Administration Tools\ReqAdmin.exe.config
C:\Program Files\WKFS\Expere Administration Tools\ReqAdmin.exe.config
Both configuration files are located at the same installation path.
You can modify this setting to add support for custom schema files. In this example, a custom schema is defined, along with the three packaged schema files, and are available as options when creating a new document.
<section name="transactionSchemaSection" type="PTR.TransactionSchemaSection,
PTR" />
<Schemas>
<Schema name="ExpereTxn" default ="true" displayName ="ExpereTxn" rootElement="Txn"
targetNamespace="http://schemas.bankerssystems.com/2004/ExpereTxn"
location="http://schemas.bankerssystems.com/ExpereTxn/ExpereTxn.xsd"/>
<Schema name="VMPMISMO" default ="false" displayName ="VMP MISMO" rootElement="LOAN"
targetNamespace="http://schemas.bankerssystems.com/2005/VMPMISMO"
location="http://schemas.bankerssystems.com/Mortgage/VMP/VMP_Expere.xsd"/>
<Schema name="QuickDoc" default ="false" displayName ="Quick Docs" rootElement="QuickDocs"
targetNamespace="http://schemas.bankerssystems.com/QuickDoc"
location="http://schemas.bankerssystems.com/QuickDocs/QuickDocs.xsd"/>
<Schema name="custom_schema" default ="false" displayName ="CustomSchema"
rootElement="CustomSchema" targetNamespace="http://schemas.bankerssystems.com/custom_schema"
location="http://schemas.bankerssystems.com/custom/custom_schema.xsd"/>
</Schemas>
</transactionSchemaSection>
Attention: Adding a schema through the Admin Tool makes that schema available; it
does not, however, imply the schema is valid. All schema files should be tested to ensure
compatibility with Expere prior to being added to the solution.
| Attribute | Description |
|---|---|
| name | The name of the schema, this must match the last part of the targetNamespace. |
| default | Define this as true to establish the schema as the default schema for the system. |
| displayName | The schema name as you want it to appear in the list of available options and within the application. |
| rootElement | The name of the root to use as a starting point for finding other elements. |
| targetNamespace | Specify the namespace that the schema targets, or validates. |
| location | The location, HTTP or file system, of the schema file (xsd). |
Support for Predefined Packages
You can generate a document data requirement SCHEMA file when a predefined PKG file is present in the source repository. The SCHEMA file contains all the data points referenced by all the document package selection rules for each document referencing a given package. Packages correspond to phases defined in the phase group PHAS file.