Wiki source code of FileToXML
Version 10.1 by Assala Chmiti on 2022/03/02 11:02
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | == **__Introduction:__** == | ||
| 2 | |||
| 3 | This connector is used to transform a file. It is a connector allowing to transform a file of another format (CSV, PLAT, - EDIFACT...) to an XML file based using a file called « **format **». | ||
| 4 | |||
| 5 | |||
| 6 | == **__Icon:__** == | ||
| 7 | |||
| 8 | |||
| 9 | [[image:1646134524824-934.png||height="112" width="126"]] | ||
| 10 | |||
| 11 | |||
| 12 | The connector exists in the scenario panel: | ||
| 13 | |||
| 14 | [[image:1.png]] | ||
| 15 | |||
| 16 | == **__Configuration:__** == | ||
| 17 | |||
| 18 | |||
| 19 | [[image:1646134567096-508.png]] | ||
| 20 | |||
| 21 | |||
| 22 | - To create or modify a transformation connector, you should be on a scenario (new or existing). | ||
| 23 | |||
| 24 | |||
| 25 | - __//Configuration ~://__ | ||
| 26 | |||
| 27 | FILE_TO_XML is a transformation connector used to set up the connector, you should click on the blue button above the connector and fill in the properties displayed : | ||
| 28 | |||
| 29 | * //**Name **//: To give a name to the processing step (connector). It is very useful to give meaningful names . | ||
| 30 | * //**Format **//: The XML file allowing to transform the input or output file to XML format or vice versa. We have several existing standard formats (EDIFACT, X12..) | ||
| 31 | * //**FileName **//: To give a name to the output file of the current step. This step is very useful for the monitoring of the platform. | ||
| 32 | * **//Input & Output Charset//** : to precise the encoding for the files. The default encoding is UTF-8. | ||
| 33 | * **//Condition //**: This field allows you to add a condition to execute the processing step only if the condition is met. | ||
| 34 | * //**Add boundary OnError**// : It is checked only to add an additional treatment in the case of an error on the treatment step. | ||
| 35 | |||
| 36 | == __**Le fichier Format:**__ == | ||
| 37 | |||
| 38 | |||
| 39 | The format file is mandatory for the connector to work. The iXPath file formats are described in XML and stored in the client environment's format directory. | ||
| 40 | |||
| 41 | The XML format represents the actual hierarchical structure of the file. | ||
| 42 | |||
| 43 | The XML output file will strictly use the tag names and structure defined in the XML structure file. | ||
| 44 | |||
| 45 | In this chapter we will go through all the possible cases of the format file. | ||
| 46 | |||
| 47 | 1. ((( | ||
| 48 | ==== __**Format Edifact**__ ==== | ||
| 49 | ))) | ||
| 50 | |||
| 51 | //__**Introduction:**__// | ||
| 52 | |||
| 53 | The Edifact format allows the user to transform an edifact fifile to an xml file respecting. | ||
| 54 | |||
| 55 | XML documents must contain one root element that is the parent of all other elements. This element should exist once in all the document. In general it is a node called "ixDOC". | ||
| 56 | |||
| 57 | |||
| 58 | __//**Elements of the file format:**//__ | ||
| 59 | |||
| 60 | Any group of information (even those that are not delimited by characters, a line break or other) must be represented in the document (e.g. groups of EDIFACT segments, Messages, etc.). | ||
| 61 | |||
| 62 | **Attributes **are considered one of the important elements in the format xml file. | ||
| 63 | |||
| 64 | They tell the translation processor what actions to take when reading the document. | ||
| 65 | |||
| 66 |