Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Excerpt |
---|
Overview
Analysis Node PropertiesUse a
|
Actionflow to run analysis on tables as if they are analysis models. For more information about running tables, |
see Analysis Models |
Live Search | ||||||||
---|---|---|---|---|---|---|---|---|
|
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Example
In a weather app a user can search for the weather data for any location using a form field and actionflow.
The actionflow is set up as below:
Each time the action is run a ForecastID is generated using a sequence in the calculate node. This is saved in the tables that are being run in the subsequent analysis node and is referenced using '_context.ForecastID'. The location that is provided by the user is also used in the tables in the analysis node using '_context.Location'. This value is sent in an API call using http collectors connected to a http datasource. The below analysis model is run as a result.
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.. Worked ExampleFor an example of how to set up an Analysis node, see Analysis Action Configuration.
Basic Settings
|
|
Streams
TablesThis section has a toolbar |
with standard buttons. The grid contains a list of |
tables.
|
|
|
Using Non-Transactional (Periodic) TablesThese are the important considerations that must be made when using non-transactional (periodic) tables in Analysis actions.
|
Advanced
|