XML is used widely in InterFormNG2 as both input and output payload in the workflow (and of course in the designer).

Please notice, that some workflow components are listed as accepting only XML as input, where they actually also accept an IBM i spooled file as input.

In general almost all workflow components can use XML as input, so a complete list of those is not included below.

There are however a few components, that should be mentioned when it comes to XML:

Transforming XML files

If you want to split up an XML file, then you should consider the Transform or split component. This example shows how to use this.

For transforming/converting an XML file you should consider the XSL tranformation component. The example also shows how this can be used.

Validating XML files

XML files can be validated in two ways: Either via a schemation, rule based validation or via an XSD validation.

Merging XML files

For normal simple merge of XML into the mostly used output formats you should consider these workflow components:

1. Create PDF email
2. Create PDF file
3. Print

The components above have in common, that they are merging the input XML with a template to generate an output. The output payload is the input file, so you can even use these component in sequence in the workflow.

A limitation is, that you cannot use merged result as it is not included in the payload. The merged result might be needed, if you want to process (e.g. digitally sign or restrict) a PDF file, that was the result of a merge. Some of these functions are listed here.

If you want the payload to switch from XML into the result of the merge, then you should consider these components instead:

1. Create EML with PDF
2. Create PDF document
3. Create direct protocol document
4. Create PCL document
5. Create ZPL document