Overview

Image Added

Use a 

There are three types of supported looping:

1. Polling, repeating the same operation multiple times with the same parameters until a desired result is obtained and then generating a single output record. Output results are only generated at the end of the iterations. For example, polling an HTTP API until the results are available.

2. Accumulation, repeating the same operation multiple times, where each iteration accumulates the progress results and triggers the next iteration with the updated result. Generates a single output record. For example, calling the DB to get the parent record, and repeating with the parent until the root has been reached.

3. Paging, repeating an operation multiple times with different parameters and generating the next parameters with a set of output records for each iteration of the loop. For example, reading from a paging API, where each iteration gives you the link for the next iteration, and a set of output records.

Insert excerpt
_property_tabs _property_tabs name basic-h nopanel true

Basic Settings

Field	Description	Example Value
Name	Name given to the action node. This will be displayed on the actionflow canvas.	MyJSONReader
Input Expression	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 an HTTP Action or the body from an API request.	// consist of the name of the pipe and the name of a // mapped attribute. in.body
Use Strict JSON parsing	Defines the parsing of the JSON, disabled will be lenient and enabled will be strict. Lenient parsing relaxes validation allowing the following to be present in the JSON data: Use of single quotes, for example: {'name': 'Some “quotes” in a string'} Unquoted field names, for example:  {name: “value”} Unescaped control characters, including literal new lines to appear within a string. Allow trailing commas {“name”: ”value”,}	// leaving the default option Disabled.
Path	The JSON Path expression is evaluated against the data provided by the Input Expression and returns a list of JSON node items. It can be used to specify which nodes are extracted from the JSON.	// JSON Path $.main_page.title

Input Connection Points

Can Accept a single

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 

  Insert excerpt
  _add _add nopanel true

   to open a new input connection point and set its properties; see Input Connection Points.
• 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 _add nopanel true

   to open a new output path and set the expression; see Output Connection Points.
• 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:

// 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"}
            ]
        }
    }
}