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: configure the component or event that will trigger the actionflow.
PhixFlow lists the inputs in the Properties tab → Input Connection Points section. - in the centre: add the actionflow nodes to create the functionality you require.
An actionflow node can be another actionflow. PhixFlow lists any actionflows that are nodes in the Properties tab → Child Actionflows section. - on the right: if the 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.
Remember that the actionflow shown in the centre of the actionflow diagram can be reused. An actionflow instance is the unique combination of:
- inputs
- actionflow
- outputs.
Use an 
Actionflow action node to add another complete actionflow within this actionflow. This is useful to reuse existing actionflows, or to refactor a complex workflow.
Example
TBC
Properties Tab
If this item is within or belongs to another, it's parent name is shown here. See the Common Properties page, Parent Details section for more details.Parent Details
Basic Settings
| Field | Description |
|---|---|
| Name | Enter the name for the action node. |
| Show in the Repository | An application can have many actionflows, and an individual actionflow can have many nodes. This can lead to many items being listed under Actionflow in the repository. Use this option to omit the node from the repository. |
Input Connection Points
TBC
We recommend that you always enter a description to explain the purpose of this item.Description
See the Common Properties page, Audit Summary section.
Audit TabAudit Summary
Learn More
- todo
For links to all pages in this topic, see todo