The Welcome page is the first page shown.

Runtime Considerations with InfoPath

At runtime, and when the Data Event wizard has been used in conjunction with InfoPath Integration the following features are supported.

There are a number of data mapping options which enable different types of extraction and outcome which differ depending on the requirements and levels of extraction from different formats for example XML (repeating and simple structures) and XSLT, used to transform documents from one form into another.

Data Manipulation | Transfer Data

This option enables you to identify the data source and its destination. The data source would typically be an XML document that contains data fields which have been populated from either a human to machine or machine to machine process interaction.

The XML document is shown in the content browser, and can be accessed using the ellipses command on the right hand side of the field box. The content browser will assist you to locate your XML documents, but these must exist to begin with.

What is XSLT ?

Definition: Extensible Stylesheet Language Transformations (XSLT) is an XML-based language used for transforming XML documents. XSLT files are used to transform XML files to XML files or into other formats like HTML or formatting objects (FO) for generating PDF files.

The Data Manipulations step enables you to assign source locations for the data and destination locations where the data will be stored. The source can be an XML document or XSLT when the data needs to be transformed from one document to another.

Select Data Source

This portion of the wizard is more detailed and includes a number of pages that need to be stepped through and settings that must be configured.

Data Manipulations	Description	Sample Value
Source	The source is the location of the XML data source	Click on the ellipse button to load the context browser. Use the context browser to locate the XML data source.
Data Structure Preview	Displays the Data Structure preview	Displays the Data Structure preview
Repeating Section	Displays the repeating section	Select the section to repeat

Mappings | Data Source

The step below requires that three individual items be configured

1. Identify the source
2. Identify the elements or repeating section to be returned
3. Configure the manner in which the element or repeating sections are returned

Data Mappings
Source	The data source; the source is an XML schema that surfaces in the context browser
Schema	Use the schema to describe and validate the data source; selecting the data element or repeating section that must be returned from the data source
Include Data	Configure the items / elements that need to be included

Select Data Destination

The destination is the location where the data is stored once it has been manipulated. The data destination can only be an XML data field. This step in the wizard also enables you to configure the outcome when there is existing data in the destination fields.

Field	Description	Sample Value
Destination	This field holds the destination location for the data that has been manipulated.	The field must be populated with a destination, and if no field has been added the wizard prompts you for a destination. Adding a destination is completed by clicking on the Context Browser button and locating the destination.
Data Structure Preview	Displays the structure of the XML data field.	Once the destination has been selected, the schema associated with the XML data field is used to display the data structure. From the XML listing, you are required to select their Destination XML data field.

The previous step enables you to map the incoming data to the parent or root node. This step in the mappings process has a number of considerations before you are able to deploy your project. Create node mappings by dragging lines from the Source XML data to the Destination XML data nodes. To access the Line Properties, click on one of the lines created to enable the Line Properties button.

XML Mapping Properties

Data Location	Description	Sample Value
Outer	Enables you to select the outer XML from the incoming source data field	Click on the drop down and select this option from the list. The selection applies to the source or incoming XML. Selecting this option will the take the entire XML structure, i.e. the root node, child nodes and the values contained therein.
Inner	Enables you to select the inner XML from the incoming source data field	Click on the drop down and select this option from the list. The selection applies to the source or incoming XML. Click on the drop down and select this option from the list. Selecting this option will ignore the outer XML taking returning only the inner XML structure.
Value	Disregards the XML data structure and selects the Value within the field	Click on the drop down and select this option from the list. This selection enables you to return from the incoming XML structure the value held by the XML structure as opposed to the data and the structure that holds it.
Destination
Outer	Enables you to select the outer XML from the incoming source data field	Click on the drop down and select this option from the list. The selection applies to the destination or location to where the Data wizard will write the XML data. Selecting this option will the take the entire XML structure, i.e. the root node, child nodes and the values contained therein and write it to the specified destination.
Inner	Enables you to select the inner XML from the incoming source data field	Click on the drop down and select this option from the list. The selection applies to the destination or location to where the Data wizard will write the XML data. Selecting this option will ignore the outer XML taking writing only the inner XML structure to the destination.
Value	Writes the XML data value to an existing field within the XML data structure	Click on the drop down and select this option from the list. This selection enables you to write to a destination XML structure the value to be held by the XML structure as opposed to the data and the structure that holds it.

Mapping Node Behavior

These define how the combinations of mappings are performed in the ‘Line Properties’ window. 

Destination -> Source V	Inner XML	Outer XML	Value
Element to Element
Inner XML	Direct Set	Copy children of source to parent of destination, then delete original destination	Direct Set (Inner Text)
Outer XML Value	Direct Set	Direct Set	Direct Set (Inner Text)
Outer XML Value	Direct Set (Inner Text)	Direct Set (Inner Text)	Direct Set (Inner Text)
Attribute to Attribute
Inner XML	Not Possible	Not Possible	Not Possible
Outer XML Value	Not Possible	Not Possible	Not Possible
Outer XML Value	Not Possible	Not Possible	Direct Set
Element to Attribute
Inner XML	Not Possible	Not Possible	Direct Set
Outer XML Value	Not Possible	Not Possible	Direct Set
Outer XML Value	Not Possible	Not Possible	Direct Set
Attribute to Element
Inner XML	Not Possible	Not Possible	Not Possible
Outer XML Value	Not Possible	Not Possible	Not Possible
Outer XML Value	Direct Set	Direct Set	Direct Set (Inner Text)

XML Example

The following diagram explains how the scopes work. The element scopes are in relation to the customer element and the attribute scopes are in relation to the regionid attribute.

Scope	Element	Attribute
Inner XML	<firstName>Frank</firstName> <lastName>Jones</lastName>	Not Valid
Outer XML	<customer regionid="100">    <firstName>Frank</firstName>    <lastName>Jones</lastName> </customer>	Not Valid
Value	Frank Jones	100

The element value is therefore the concatenated text (without the XML tags) that the element contains. In the following example, the value of the element would be FrankJones. This is because there is no white space between the “firstName” and “lastName” elements.

<customer><firstName>Frank</firstName><lastName>Jones</lastName></customer>

The W3C XML Specification draws a distinction between “Inner Text” and “Value”. The two were combined into “Value” in the Data Event wizard because “Inner Text” cannot be used on an attribute, and “Value” cannot be used on an element.

Once you have mapped their data requirements, the final page displays. The wizard is now complete.