Analysis Node

This page is for application designers who need to configure functionality for components or events. It explains the properties for the analysis node, which is part of an actionflow.

Overview

Use a  Run Analysis node in an actionflow to run analysis on tables as if they are analysis models. For more information about running tables, see Analysis Models for Batch Processing Data.

Analysis actions only allow transactional tables to be included to ensure correct model operation.

Example

In a weather application, a user can search for the weather data for any location using a form field connected to an actionflow.

The actionflow is set up as follows:

Each time the application user runs the action, the calculate node selects a number from a sequence to add the ForecastID identifier. When the subsequent analysis node runs, it saves the ForecastID to the tables that are being run.

The expressions in the tables can reference:

  • the ForecastID identifier. '_context.ForecastID'
  • The location provided by the user   '_context.Location'.

The location value is sent in an API call using HTTP collectors connected to a HTTP datasource, as shown in the following analysis model:

Using Context Parameters

Tables that are being run may rely on context parameters in their attribute expressions. Adding attributes with the same name as the context parameters to the analysis node will work in the same way. For example, if a table relies on the expression '_context.Name', an attribute called 'Name' can be added to the analysis node. The value for this can then be mapped to this attribute from any preceding connection.

 Properties Tab

Parent Details

If this item is within or belongs to another, its parent name is shown here. See the Parent Details section on the Common Properties page for more details.

Basic Settings

FieldDescription
NameEnter the name for the analysis node.
Description

We recommend that you always enter a description to explain the purpose of this item.

Tables

This section has a toolbar with standard buttonsThe grid contains a list of tables. 

  • To add a table, in the section toolbar click  List Tables to open a repository tab filtered to show tables by application. Drag a table from the list into the grid.
  • To remove a table, select one and in the section toolbar click  Delete.

Advanced

FieldDescription
Prioritise Throughput Over Ordering
When enabled, records are processed in parallel to optimise performance. This means the order records are processed is nondeterministic.

When disabled (default), records are processed in the order they are provided.

 Access and Audit Tab

 Security Tab

Access Permissions

See the Common Properties page, Access Permissions section.

 Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.

Sections on this page

Learn More

For links to all pages in this topic, see Understanding Actionflows


Terminology changes in progress

As part of the redesign of PhixFlow, we are changing the following terms:

dashboard → screen   
stream → table
stream attributes → attributes
stream item → record
stream set → recordset
stream view → view
stream item action → record-action 
stream action → table-action
driver class → database driver