The OPrognose ZIP file is imported using the HUMBLE Exchange server. Below a description how the Exchange Server is handling the OPrognose XML file.
1 - ZIP File is extracted
The XML file and images are stored on the Exchange server
2 - <OPO> Building record
The OPO Record is read and a mapping is done as described below.
OPrognose XML tag | Type of mapping | HUMBLE Field | Description |
---|---|---|---|
n.a. | Fixed mappings |
| |
| Direct mapping |
| |
| Direct mapping |
| |
| Direct mapping |
| |
| Direct mapping |
| |
| Direct mapping |
| |
| Functional mapping |
| Converts the field |
| Functional mapping |
| This method will strip the field <obj_adres> into two Humble Fields |
| Functional mapping |
| See above |
| Functional mapping |
| Gets all the available and nit empty <obj_memoxxx> fields and concatenate them to one result. The remark length has a maximum of 512 characters in HUMBLE and the result will be truncated if necessary |
Functional mapping |
| A new code is generated by default for each location of type Building. Code like ‘G-000001’ | |
| Functional mapping |
| Integer value for the |
| Functional mapping |
| Remove all spaces from the field |
| Functional mapping |
| The original reference |
| Functional mapping |
| The original reference |
| Image mapping | Added as separate images within HUMBLE. Images are related to the location (building) |
3 - <OPE> Element record
Each OPE record is read and mapped (see description below) and related to the location (building)
OPrognose Field | Type of mapping | HUMBLE Field | Description |
---|---|---|---|