EDI Configuration Schemas
Whenever you make a change to a configuration file, it is important to validate it against its applicable XML schema. The schema is available in the directory C:\Program Files\Altova\MapForce2022\MapForceEDI and it can be one of the following:
File | Purpose |
|---|---|
EDIConfig.xsd (version "3") | This configuration schema is valid starting with MapForce 2011, Release 2. If you have configuration files that are using a schema prior to version 3, they must be upgraded to use this schema (or a newer one). For more information, see Upgrading Older Configuration Files. |
EDIConfig4.xsd | This configuration schema is valid starting with MapForce 2011, Release 3. It contains multiple enhancements to the original EDIConfig.xsd schema, including the ability to define custom recursive hierarchies which might be necessary when you map data to or from X12 or HL7 formats. |
EDIConfig5.xsd | This configuration schema is valid starting with MapForce 2017. It introduces the ability to define a data element that has incomplete validation rules. With this schema, it is possible to define advanced field validation rules at character level (see Configuring Character-Level Validation). |
EDIConfig6.xsd | This configuration schema is valid starting with MapForce 2018. It introduces the ability to map data to or from NCPDP SCRIPT format, see NCPDP SCRIPT . |
EDIConfig7.xsd | This configuration schema is valid starting with MapForce 2021. It introduces the ability to map data to or from SWIFT MT. |
The EDI configuration schema will also offer information about the structure of any elements that may be present in the configuration files. For example, below is a representation of an EDI Data Element structure as it appears in the EDIConfig4.xsd schema:
Structure of the Data element (Schema view of XMLSpy)