OverviewAnalysis Node Properties
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, see Analysis Models. Note |
---|
Analysis actions only allow transactional tables to be included to ensure correct model operation. |
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 SettingsField | 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 |
---|
| to open a repository tab filtered to show tables by application. 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
AdvancedField | 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 |
---|
|
|