Versions Compared

Key

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

Insert excerpt
_Banners
_Banners
nameactionflow
nopaneltrue


Topics to cover
Excerpt
ConnectionsDragging and dropping on a kanban
name
  • Inbound
    • No Data = On Click/On Enter
    • Data = Datasource
  • Outbound
  • Lookups
  • Connection Point Types
    • Driving (one record)
    • Lookup (many records as a single dataset)
  • Driving vs Lookup connections
    • Driving connections (records are pushed one by one) 
    • Lookup connections (all records are pulled as a single block but only when the connection is referenced in an expression inside the node)
  • Nodes types
    • Actionflow
    • Open screen
    • View
    • Calculate 
    • Gateway - map to output connection points
    • Open URL
    • Save
    • Analysis
    • HTTP
    • Email
    • JSON
    • For Each
    • Loop
    • Funnel
    • Start Phase
  • Phases
  • Tool bar options
    • Show Event Location
    • Close Screen
    • Hide Spinner
    • Origins
    • etc.
  • Instances/Reusability
    • Concepts
    • Locating Instances
    • Opening Instances
    • Actionflows vs instances
    • Nesting actionflows
  • Event handlers
    • On click
    • On change
    • On blur
    • On enter
    • Double-click (This is when the actionflow is set as the default action on a view)
    • Default Action for auto save on a view.
  • Wiring
    • Mapping attributes In and Out
      • Input Parameters: These are needed if you want to use an attribute in a node.
      • Output Attributes
      • Passthrough
      • Mapping data into an actionflow for a specific instance
      • Mapping data between nodes on an action flow
        • Pass-through and Join nodes (only attributes common to all paths leading to the Join can be passed through)
    • Disconnecting
    • Inserting Items
  • Referencing additional data
    •  Lookups
      • Creating a Lookup
      • Returns a recordset
    • Views
      • Creating Views
      • Returns individual Records
    • Lookups vs Views:
      • The differences
      • When to use each one/ use cases
    • The difference between actions that run once per record (single circle around the node)  and those that run once per flow (e.g. open dashboard, start phase, open url ... double circle around the node ) 
  • Confirmation dialogues
  • Security and permissions
  • Record throughput and behaviours
  • Exclusion Groups
    • Concurrency?
  • Where they can be initiated
  • Additional Topics

    • List all Actionflow and Screen Actionflow. Showing actionflow associated to a screen that are not connected. This occurs when we create actionflows in a workflow.

    Scenarios to cover

  • Counting records (lookups)
  • Checking for duplicates (lookups)
  • Checking a value is in a list (lookups)
  • Setup an API end point 
  • Configuring a Validation Phase (or another example?)
  • Verify a record is selected (validation)
  • Configuring a Confirmation
    • Custom confirmation message and screen
  • Debugging guide
  • Configure buttons
    • Pass data between screens
    • Populate a field
  • FullPage

    Welcome

    Welcome to PhixFlow's Actionflow Courses, where you will get a deeper understanding of what an Actionflow is, how they are used and what you need to know to create and use them in your application(s). The courses provide both theoretical knowledge and practical exercises. 

    Course Prerequisites

    • Completed the PhixFlow Fundamentals 
    • Completed one of the Screen Building Courses, or have prior knowledge of building screens
    • A PhixFlow training instance or download the specified data from the Learning Centre

      Expand
      titleHow do I get a Training Instance?

      To obtain a training instance, contact support@phixflow.com

      To get the best experience on the course, we recommend using a training instance. 


    Course Structure and Objectives

    This course consists of 3 modules (Foundation, Intermediate, Advanced), with each module taking approximately 1 day to complete, but this is just a guide. 

    ModuleTopicsObjectives
    We explore creating simple Actionflows, gaining theoretical knowledge of the processing involved.
    • Good knowledge of the product
    • Ability to configure Actionflows for a simple application
    • Ability to assimilate knowledge from the Help

    We explore creating Actionflows that require sophisticated processing logic.


    • All of the above
    • Ability to configure intermediate-level Actionflows
    We explore Actionflows requiring advanced business logic and competently use all Actionflow features.
    • All of the above
    • Ability to use all Actionflow features to a high level