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 a worked example, see Analysis Action Configuration.

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

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  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.

Using Non-Transactional (Periodic) Tables

These are the important considerations that must be made when using non-transactional (periodic) tables in Analysis actions.

• All Recordsets must be contiguous with no gaps and overlaps

  • If you need to Rollback 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

 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.