Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Overview
Use a an
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Basic Settings
Expect literal values or expressions encapsulated within ${} syntax, for example${in.MyValue}
. A worked example of the JSON Node is provided at the end of this page.Field | Description | Example Value |
---|---|---|
Name | Name given to the XML Node. This will be displayed on the actionflow canvas. | MyXMLReader |
Input Expression | The input expression provides the source of the XML data to be operated upon. Typically, this will be a simple expression pointing at an incoming attribute, such as, the body from a HTTP Node. | // Consists of the pipe name and the name of a mapped attribute
|
XPath | The XPath expression is evaluated against the XML document provided by the Input Expression and returns a list of XML elements. It determines which elements are extracted from the JSONXML. Note that the XPath determines the number of elements that are processed, which directly correlates to the number of records returned by the XML Node. For example, if the path returns the route element of the XML Document only one record will be returned. Whereas a path that returns children nodes will return one record for each child element. | // XML XPath /root/main/title |
Excerpt | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
XPath Syntax
A worked example is provided at the end of this page. |
Output Attributes
Contains a list of attributes returned by the node. In this node XML is converted into data objects that can be used by PhixFlow, this information is accessed using the syntax _result.
AttributeName
in an output attribute. To add an output attribute click the
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Image Added
Worked Example
Code Block | ||
---|---|---|
| ||
<root xmlns:h="http://example.com/schema"> <main page="PF Main Page"> <h:title name="PF Title">PF Title Text"> <h:datarow> <h:data h:initials="AA">Alistair Andrews<data> <h:data h:initials="BB">Bert Brown</data> </h:datarow> </h:title> </main> </root> |
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Input Connection Points
Can Accept a single
|
Output Connection Points
This section has a toolbar with standard buttons. The grid contains a list of all output connection points.
To add a new output path, in the section toolbar clickOutput Attributes
JSON is converted into data objects that can be used by PhixFlow, this information is accessed using the syntax, _result.
AttributeName.
Worked Example
Below is an example JSON object passed to the JSON Node:
Code Block | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
// Example JSON string.
{
"main_page": {
"page": "PF Main Page",
"title": {
"name": "PF Title Text",
"data": [
{"initials": "AA", "value" : "Alistair Andrews"},
{"initials": "BB", "value" : "Bert Brown"}
]
}
}
} |
JSON Path: $.main_page.title
This path will bring back all elements matching the JSON path including the parent/grandparents and all child elements. The path defines the starting point from which we reference the JSON nodes.
The following examples show how to reference the returned JSON data:
_result
.name
, returns PF Title Text_result
.^.page
, returns PF Main Page- The ^ traverses up the JSON hierarchy.
listToString(_result.data.initials)
, returns "AA, BB"- Because there are multiple JSON nodes under
_result.data.initials
, an array of data is returned. See Array Handling Functions.
- Because there are multiple JSON nodes under
Info | ||
---|---|---|
| ||
|
Learn More
For links to all pages in this topic, see Understanding Actionflows.