Components
Each outbound deliverable is made up of these components:
| Component | Notes |
|---|---|
| Application BODs | This component is not always present. All Localization Services
application BODs are identified with LCL in the name of the noun. Note: These BODs need
to be imported into the ION Desk Object Schemas. See KB #1594828 for more
information.
|
| Custom BODs | These components are delivered in a ZIP file that contains one folder for each noun. |
| Format file | This component contains the code lists that contain the proprietary format names
for each noun. Note: GEMS supports documents that use the encoding that ION supports. An
Infor standard is that all XML documents use the UTF-8 encoding. See the message
content section of Infor ION Development Guide–Cloud
Edition.
|
| Workflows | These components consist of detection values and data completion to add value directly to the BOD. It has no detection and error notifications. |
| File format template | This component contains the file type of the proprietary format. |
| Document flows | These components contain the logic for the electronic messages, and are made up of file templates, file connection points, and all the mappings. |
Each inbound deliverable is made up of these components:
| Component | Notes |
|---|---|
| Custom BODs | These components are delivered in a ZIP file that contains one folder for each noun. |
| File format template | This component contains the file type of the proprietary format. |
| Document flows | These components contain the logic for the electronic messages, and are made up of file templates, file connection points, and all the mappings. |