| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
This page is for application designers who need to configure functionality for components or events.
Overview
The actionflow diagram comprises three areas:
on the left: configureOverview
In general, there is no need to edit the actionflow properties as the configuration is done in the actionflow diagram. The diagram comprises two primary areas:
- Connection Points: on the left define the input, lookups and outputs for the actionflow.
- Inputs: Configure the component or event that will trigger the actionflow.
- PhixFlow lists the inputs in the Properties tab → Input Connection Points section.
An actionflow node can be another actionflow. PhixFlow lists any actionflows that are nodes in the Properties tab → Child Actionflows section.
- Lookup: Configure the retrieval of information from the component or other items from the same source e.g. a screen.
- Output: If an Actionflow has an output as a result of running, configure what to do with the outputs.
- PhixFlow lists the inputs in the Properties tab → Output Connection Points section.
For more details on how to do this see Understanding Actionflows.
| Tip |
|---|
Remember that the actionflow shown in the centre of the actionflow diagram can be reused. An actionflow instance is the unique combination of:
|
- Canvas: In the centre add the actionflow nodes to create the required functionality.
An actionflow can be nested within another actionflow (see Actionflow Node). This is useful to reuse existing actionflows, or to refactor a complex workflow.
Example
TBCFor details on how to configure actionflows; see Understanding Actionflows and Creating Actionflows.
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
|
Basic Settings
Expect literal values or expressions encapsulated within ${} syntax, for example ${in.MyValue}. A worked example of the JSON Action is provided at the end of this page.
| Field | Description | Example Value |
|---|---|---|
| Name |
Input Connection Points
| Name given to the actionflow. | MyJSONReader | |
| Description | ||
| Show in Repository | ||
| Exclusion Group | ||
| API End-Point | ||
| Allow Anonymous Connections |
Actions
Input Connection Points
This section has a toolbar with standard buttons.
The grid contains a list of the inputs that can initiate this actionflow instance.
- To change an input connection point, use the actionflow diagram's left panel.
- To edit the properties of an existing input connection point, double-click it's name in the list to open its properties; see Input Connection Points.
- To delete an input connection point from the properties, the actionflow diagram and the repository, select it in the list and in the section toolbar, click
Insert excerpt _
delete _
delete nopanel true
| Live Search | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Learn More
- todo
- .
Refresh the actionflow diagram to reflect this change.
Output Connection Points
This section has a toolbar with standard buttons.
The grid contains a list of the outputs from this actionflow instance.
- To change the output connection point, use the actionflow diagram's left panel.
- To edit the properties of an existing output connection point, double-click it's name in the list to open its properties; see Output Connection Points.
- To remove an output connection point from the properties, the actionflow diagram and the repository, select it in the list and in the section toolbar, click
.Insert excerpt _delete _delete nopanel true
Refresh the actionflow diagram to reflect this change.
Learn More
For links to all pages in this topic, see todosee Understanding Actionflows.