| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Overview
Use a
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Basic Settings
Expects literal values or expressions encapsulated within ${} syntax, for example ${in.MyValue}.
| Field | Description | Example Value |
|---|---|---|
| Name | Name given to the action node. This will be displayed on the actionflow canvas. | MyJSONReader |
| Input Expression | // consist of the name of the pipe and the name of a // mapped attribute.
| |
| Use Strict JSON parsing | A template that computes to the URL of the request. Expects literal values or expressions encapsulated within ${} syntax, for example | |
| Path | The JSON Path expression is evaluated against the Input Data and returns a list of JSON nodes Items. It can be used o specify which objects are extracted from the JSON. | // JSON Path $.main_page.title |
Input Connection Points
Can Accept a single
| Insert excerpt | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
The grid contains a list of all input connection points and their type.
- To add a new input connection point, in the section toolbar click
to open a new input connection point and set its properties; see Input Connection Points.Insert excerpt _add _add nopanel true - To edit an existing input connection point, double-click it in the list to open its properties.
- To remove an input connection point, select one and in the section toolbar click
Insert excerpt _
delete _
delete nopanel true
- .
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 click
Insert excerpt _
add _
to open a new output path and set the expression; see Output Connection Points.add nopanel true - To edit an existing output path, double-click it in the list to open its properties.
- To remove an output path, select one and in the section toolbar click
Insert excerpt _
delete _
.delete nopanel true
Output 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 Action 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 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 items against
_result.data. initialsan array of data returned. See Array Handling Functions.
- Because there are multiple items against
Note the use of:
^traverses up the hierarchy 1 layer.- . tranverses down the heirach 1 layer.
Learn More
For links to all pages in this topic, see Understanding Actionflows.