This topic is for application designers who want to know how to configure understand the concepts of actionflows.

...

For each instance of an actionflow, you specify which data the actionflow takes using the by wiring to connectors. This means you can connect to attributes with any name.

Illustration

The picture below shows an actionflow that validates the format of data to ensure it is a valid area code. It's input connection is called Area Code.

...

• Postcode data in the Contact App
• Zip Code in the Asset Manager App. 

This illustrates shows that an actionflow can take its input from an attribute with any name. It also illustrates the 2 instances of the actionflow:

• Instance 1 is the actionflow with input from Postcode 
• Instance 2 is the actionflow with input from Zip Code.

Actionflow

...

Creating an Actionflow:

1. Right Click on any button on a dashboard and select Add Actionflow.
   1. This will create the Actionflow and assign it to the button.
2. In the repository browser go to Actionflows expand tree and click Add New.
   1. This will create the Actionflow, which can then be dragged onto the required button.

Actionflow Window

The key concepts of an Actionflow are illustrated below:

...

Window

The following illustration shows the layout of an actionflow diagram. The numbered areas are explained below.

Image Added

1. Toolbar
   The toolbar contains icons that you drag onto the actionflow canvas to create the different nodes, such as a calculate action.
2. Source
   If the source is empty, you are editing the actionflow.
   If the source contains a name, you are editing an actionflow instance.
   The source indicates what triggers the actionflow. This can be:
   • the name of the component, such as a button
   • an event, such as a double-click If this is empty then the user is editing the Actionflow directly.
3. Options:
   These are options that relate o affect the entire workflow, such as hiding the loading spinner. 
4. Inputs: There are two kinds of input that can be connected / mapped into a Actionflow DRIVING AND REQUEST?
   1. Event: This is a user or system triggered action such as a user clicking on a button. Event information can be used to start an Actionflow. This event node has information available to the user such as where the click came i.e. which button was clicked.
   2. View (of he data): This is the data available to the Actionflow, specifically the data bound objects e.g. grid or form fields. The event calling the Actionflow e.g. a button click, has access to data in the same area as itself or to areas embedded within the same area.  
   Input Connection Points: These define fixed data and events that are expected by the Actionflow. They remain consistent for all instances of the Actionflow. Each instance of an Actionflow then define what data is mapped onto these connection points. Connection points
   Inputs to an actionflow  todo - check - driving and request?
   • Event starts the actionflow. Events can be:
     • either a user-triggered action, such as a mouse click on a button
     • or system-triggered action such as todo.
       
   • View provides data to the actionflow. The event acts upon data in the same area, or nested within the area.  A view is a combination of:
     • a stream (table)
     • related attirbutes
     • sorting and filtering of records
     • data display, such as  grid or form fields.  
5. Connectors
   These specify the data and events that the actionflow requires. All instances of the actionflow require appropriate inputs to be wired to these connectors.
   Connectors collect data, pass data back to the calling object and perform lookups on data.This will be covered in    todo - more detail later on this page 
6. Action Nodes: The Action Nodes are used to carryout the actions against the information passed in from the connection points or to perform lookups to other sources of data.

Image Removed

The pages in this topic are:

...

1. 
   The nodes on the diagram represent individual action that pass or process the data from the connectors. Nodes can also look-up data from other sources, for example to add parameters to a calculation.