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 

Example

In a weather application, a user can search for the weather data for any location using a form field connected to an actionflow.

The actionflow is set up as follows:

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:

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.

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
  HELP100:_table_listHELP100: _table_list nopanel true

   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 

  Insert excerpt
  HELP100:_deleteHELP100: _delete nopanel true

  .

Insert excerpt

_property_tabs

_property_tabs name access-h nopanel true