2019.2

If the current job file isn't JSON or XML (depending on the type of conversion requested), or if
the conversion fails for any reason, the task raises an error and the current job file and
metadata remain unchanged.
JSON to XML conversion
When a JSON source file contains a single JSON object, that object's key will be used as the
root node name in the resulting XML file, and the root node will be populated with the data
inside of the JSON object. In all other cases, a root node named 'root' will be added to the XML.
It has the property "OL" with the value "RootObject" to define it as an array container. This
property will be ignored when converting from XML to JSON.
Note
In addition to being valid, the JSON should follow naming rules for XML elements. For example,
"adress_line_1:" is a valid key name in JSON, but it cannot be converted to a valid element name in
XML because the colon is reserved for namespaces. For XML naming rules and best naming
practices, see: XML elements on W3Schools.
Output
The output is the modified job file, which replaces the input job file. The metadata are reset.
Task properties
General tab
l
Automatic detection: By default, the format of the job file is detected automatically. If the
source file is a JSON file, it will be converted to XML. If it is an XML file, it will be
converted to JSON.
Uncheck this option to limit the task to one type of conversion.
l
JSON to XML: the task only converts JSON files to XML.
l
XML to JSON: the task only converts XML files to JSON.
On Error Tab
Miscellaneous Tab
The Miscellaneous tab is common to all tasks.
Page 475