This page is for application designers who need to configure functionality for components or events.
Overview
UNKNOWN ATTACHMENT
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.
For details on how to configure actionflows; see Understanding Actionflows and Creating 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 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.
|
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
Delete.
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
Delete.
Refresh the actionflow diagram to reflect this change.
Child Actionflows
This section has a toolbar with standard buttons and the 
Actionflow List icon.
The grid contains a list of all the nodes in the actionflow.
Click
Actionflow List to show the list of nodes in the repository.Double-click a node in the list to open it's properties.
Description
We recommend that you always enter a description to explain the purpose of this item.
Security Tab
Access Permissions
See the Common Properties page, Access Permissions section.
Audit Tab
Audit Summary
See the Common Properties page, Audit Summary section.
Learn More
For links to all pages in this topic, see Understanding Actionflows.
Terminology changes in progress
As part of the redesign of PhixFlow, we are changing the following terms:
dashboard → screen
stream → table
stream attributes → attributes
stream item → record
stream set → recordset
stream view → view
stream item action → record-action
stream action → table-action
driver class → database driver