| Insert excerpt |
|---|
| _Banners |
|---|
| _Banners |
|---|
| name | actionflow |
|---|
| nopanel | true |
|---|
|
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
Analysis Node Properties Image Modified
Use a | Insert excerpt |
|---|
| _action_analysis |
|---|
| _action_analysis |
|---|
| nopanel | true |
|---|
|
node in an |
Actionflow to run analysis on tables as if they are analysis models. For more information about running tables, |
| Note |
|---|
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. 
Image Removed
The actionflow is set up as follows:
Image Removed
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:
Image Removed
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. Worked ExampleFor an example of how to set up an Analysis node, see Analysis Action Configuration. | Insert excerpt |
|---|
| _property_tabs |
|---|
| _property_tabs |
|---|
| name | basic-h |
|---|
| nopanel | true |
|---|
|
| Insert excerpt |
|---|
| _parent |
|---|
| _parent |
|---|
| nopanel | true |
|---|
|
Basic Settings| Field | Description |
|---|
| Name | Enter the name for the analysis node. | | Description | We recommend that you always enter a description to explain the purpose of this item. |
TablesThis section has a toolbar |
with standard buttons. The grid contains a list of tables. - To add a table, in the section toolbar click
| Insert excerpt |
|---|
| _table_list |
|---|
| _table_list |
|---|
| nopanel | true |
|---|
|
|
- the available tables in the Repository
- Drag a table from the list into the grid
|
- To remove a table, select one and in the section toolbar click
| Insert excerpt |
|---|
| _delete |
|---|
| _delete |
|---|
| nopanel | true |
|---|
|
| Note |
|---|
Care should be taken when running analysis on tables with a non-transactional Period set. The non-transactional table periods are Daily, Monthly and Variable. See Table. |
Using Non-Transactional (Periodic) TablesThese are the important considerations that must be made when using non-transactional (periodic) tables in Analysis actions. All | Insert excerpt |
|---|
| _recordsets_icon |
|---|
| _recordsets_icon |
|---|
| nopanel | true |
|---|
|
Recordsets must be contiguous with no gaps and overlaps- If you need to
| Insert excerpt |
|---|
| _rollback |
|---|
| _rollback |
|---|
| nopanel | true |
|---|
|
a run in a variable table, it rolls back all the runs after to maintain contiguous recordsets, whereas rolling back on a transactional table only rolls back the specified run
- Two recordsets will not be generated at the same time
- If a recordset is already being created, any requests run while it is completing will get the same results, e.g. if the 11am data is generating, then in 30 minutes a users starts the 12pm data generation, they will get the 11am data
When an Actionflow runs an analysis model it uses the toDate from the Actionflow, i.e. now(), therefore, it only runs once if non transactional
Advanced| Field | Description |
|---|
| Prioritise Throughput Over Ordering | | Insert excerpt |
|---|
| Actionflow Properties |
|---|
| Actionflow Properties |
|---|
| name | PrioritiseThroughputOverOrdering |
|---|
| nopanel | true |
|---|
|
|
| Insert excerpt |
|---|
| _property_tabs |
|---|
| _property_tabs |
|---|
| name | access-h |
|---|
| nopanel | true |
|---|
|
| Insert excerpt |
|---|
| _access |
|---|
| _access |
|---|
| nopanel | true |
|---|
|
|
| nopanel | true |
|---|
| Live Search |
|---|
| spaceKey | @self |
|---|
| additional | none |
|---|
| placeholder | Search all help pages |
|---|
| type | page |
|---|
|
| Panel |
|---|
| borderColor | #00374F |
|---|
| titleColor | white |
|---|
| titleBGColor | #00374F |
|---|
| borderStyle | solid |
|---|
| title | Sections on this page |
|---|
|
| Table of Contents |
|---|
| maxLevel | 3 |
|---|
| indent | 12px |
|---|
| style | none |
|---|
|
|
Learn More
For links to all pages in this topic, see Understanding Actionflows.
| Insert excerpt |
|---|
_terms_changing | _terms_changing