This page is for application designers who need to configure functionality for components or events.
Overview
In general, there is no need to edit the actionflow properties as the configuration is done in the actionflow diagram. The 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. his is useful to reuse existing actionflows, or to refactor a complex workflow. 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.
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 the properties to add a description for the actionflow, or to change which users can run it.
Property Pane Toolbar
For information about the toolbar options, see the Common Properties page, Toolbars and Controls section.
Properties Tab
Parent Details
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.
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.