Versions Compared

Old Version 1

changes.mady.by.user Anthony George

Saved on

compared with

New Version 2

changes.mady.by.user Anthony George

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Insert excerpt
_Banners
_Banners
nameactionflow
nopaneltrue

Overview

Image Removed

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.

    Tip

    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.

    Insert excerpt_property_toolbar_property_toolbarnopaneltrue Insert excerpt_property_tabs_property_tabsnamebasic-hnopaneltrue Insert excerpt_parent_parentnopaneltrue

    Basic Settings

    FieldDescriptionNameEnter the name for the action node. Insert excerpt_actionflow_properties_actionflow_propertiesnameshow-namenopaneltrue Insert excerpt_actionflow_properties_actionflow_propertiesnameshow-textnopaneltrue

    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_deletenopaneltrue.
    Refresh the actionflow diagram to reflect this change.     Insert excerpt_description_descriptionnopaneltrue

    Insert excerpt_access_accessnopaneltrueInputs.pngImage Added

    Actionflows can use data displayed on screens. This data can be manipulated within an actionflow and can be saved onto tables. Sometimes an actionflow does not require any data from the screen from which it is initiated. In this case, use the event as the input for the actionflow. An event is triggered by mouse-clicks (On-Click, Double-Click)  or keyboard presses (On-Enter). Connecting an event to an actionflow means the actionflow runs in response to the event, regardless of any data supplied.

    Input Connection Points

    Input Connection points are the interface to the actionflow. They define the inputs the actionflow is expecting, and allows values from the incoming inputs to be mapped onto these.

    For example, an actionflow may expect an Area Code to calculate a distance. One screen passes the actionflow a Postcode this is mapped into the actionflow using the Input Connection Point mapping.

    Image Added


    A second screen can reuse the actionflow (this is referred to as a different instance) and pass in a Zip Code which is mapped into the actionflow using the Input Connection Point mapping. 

    Image Added


    Input Connection Point Setup

    When a new input is connected the mapping wizard will appear. To reopen the mapping wizard:

    1. Right-click the input Connection Point
    2. Select 
      Insert excerpt
      _mappingConfigure
      _mappingConfigure
      nopaneltrue
      .

    Data to be Used

    Data NameDescription
    Selected RecordsRecords selected in the Input. For example multiple records selected on a grid.
    Edited RecordsRecords that have been edited on the input. For example, only records which have been edited on a grid.
    PageAll records on a page. For example a single record being edited using a form.
    Dragged RecordsSelected records that have been dragged onto a drop target.
    Drop Target RecordsRecords Dropped onto a drop target.

    Mappings

    1. Drag a record from the left (input) onto a corresponding record on the right (Input Connection Point)
      1. If no corresponding record exists in the Input Connection point one can be added by dropping an incoming record into the empty space on the right, this causes a new record to be created.
    2. This input is now mapped correctly into the actionflow. 
    3. Repeat for all required inputs.
    4. Click Confirm Mapping.


    Insert excerpt
    _audit
    _audit
    nopaneltrue


    Live Search
    spaceKey@self
    additionalnone
    placeholderSearch all help pages
    typepage

    Panel
    borderColor#00374F
    titleColorwhite
    titleBGColor#00374F
    borderStylesolid
    titleSections on this page

    Table of Contents
    maxLevel3
    indent12px
    stylenone


    Learn More

    For links to all pages in this topic, see Understanding Actionflows. 


    Insert excerpt
    _terms_changing
    _terms_changing
    nopaneltrue