Actionflow to run analysis on

tables as if they are analysis models. For more information about running tables,

see Analysis Models

.

Worked Example

For 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

Basic Settings

Tables

This 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 show 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

Using Non-Transactional (Periodic) Tables

These 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

Insert excerpt
_property_tabs _property_tabs name access-h nopanel true