Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
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. OverviewImage Modified 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. 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
For a worked example, see Analysis Action Configuration. Using Context ParametersTables 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
Basic Settings
|
TablesThis section has a toolbar |
with standard buttons. The grid contains a list of tables.
Advanced
|
|
Live Search | ||||||||
---|---|---|---|---|---|---|---|---|
|
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Learn More
Understanding ActionflowsFor links to all pages in this topic, see Understanding Actionflows.