...
Systems that interface with eLandings can generally continue to use an outdated schema if they do not use data elements contained in a newer schema. While the eLandings development team recommends that all interfacing systems keep up to date on schema versions, we recognize that it can be difficult or inconvenient to update interface code in a timely manner. The eLandings system supports the use of legacy versions of the schema. The system upgrade incoming data to the current version of the schema automatically.
| Warning | ||
|---|---|---|
| ||
In the schema has been changed to add a new required field then that field will still be required, even if data is imported using an older version of the schema. The use of legacy versions of the schema does not relieve the user of the requirement to honor all business rules in the system. |
For interfacing systems that receive exported XML documents from eLandings, the user export feature on landing and production reports automatically downgrades the schema version to version 1.0, the original version. In the Spring of 2009 the system will begin exporting reports using the current version, but the user profile will be enhanced to allow users to specify a legacy schema version to use. This will allow users to continue to receive reports created with an older version of the schema while their system developers are enhancing their system to use the newer version of the reports.
| Note | ||
|---|---|---|
| ||
In the schema has been changed to add a new required field then that field will still be required, even if data is imported using an older version of the schema. The use of legacy versions of the schema does not relieve the user of the requirement to honor all business rules in the system. |
XML Usage Documentation
The eLandings documentation on the Confluence website includes a system interface guide that describes the main XML documents, their elements, and how the elements are used.