Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
What is a JSON Action?
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
For the full list of JSON action
, see JSON Action Properties. Insert excerpt _property_settings _property_settings nopanel true
Creating JSON Actions
- Click and drag the
icon from the toolbar onto the canvasInsert excerpt _action_json _action_json nopanel true - Enter a name for the JSON action, then select Create Action
- In the JSON action
on the right, populate the following details:Insert excerpt _property_settings _property_settings nopanel true
Field | Description | Example Value | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Name | Name given to the JSON Node. This will be displayed on the Actionflow canvas. | MyJSONReader | ||||||||
Input Expression | This field is mandatory. The input expression provides the JSON 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 name of the connector and mapped attribute
| ||||||||
Use Strict JSON parsing | Defines the parsing of the JSON. Disabled is lenient and enabled is strict. Lenient parsing relaxes validation allowing the following to be present in the JSON data:
| // Leaving the default option
| ||||||||
Path | The JSON Path expression is evaluated against the data provided by the Input Expression and returns a list of JSON elements. It determines which elements are extracted from the JSON. The path starts at the root element represented by $ and each element in the path is separated by a full stop. The ^ traverses up a node and a . traverses down the node. Note that the path determines the number of nodes that are processed, which directly correlates to the number of records returned by the JSON action. For example, if the path returns the root element of the JSON, only one record will be returned. Whereas a path that returns children nodes will return one record for each child element. | // JSON Path $.main_page.title |
Tip |
---|
Use literal values or expressions encapsulated within ${} syntax, for example |
4.
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Path Syntax
Expression | Description |
---|---|
| symbol refers to the root element. |
@ | symbol refers to the current element. |
. | is the dot-child operator, which is used to denote a child element of the current element. |
[ ] | is used to select a child element of the current element (by name or index number). |
* | a wildcard, returning all elements regardless of their name. |
^ | symbol is used to traverse up 1 element in the JSON hierarchy from child to parent. |
Output Attributes
JSON is converted into data objects that can be used by PhixFlow, this information is accessed using the syntax, _result.elementName.
_out.attributeName
.Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
HTML Comment | ||
---|---|---|
| ||
ZB I think the references to elements on this page should be replaced with references to "keys". JSON comes in key/value pairs in the syntax "key":"pair" - see https://www.w3schools.com/js/js_json_syntax.asp. Need to read up on this and make changes to this page. |
HTML Comment | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Extracting Data Example
Below is an example JSON object passed to the JSON action:
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 | ||
---|---|---|
| ||
|
Retrieving Field Names
Code Block | ||||
---|---|---|---|---|
| ||||
{ "a": "1", "b": 2, "c": "xxx", "d": { "x": 1, "y": 2, "z": 3 } } |
To retrieve the field names held in element d:
Code Block |
---|
do( $json = jsonToItems(in.JsonIn), $fields = getFields($json.d), $fields[1] ) |
Returns the first field name of d which is “x” - see getFields.
Worked Example
Note |
---|
This example is taken from HTTP Action Configuration. If you have already completed this chapter as part of the Actionflow course, ensure you are familiar with the content before moving onto the next chapter. |
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|