Topics to cover

• Start with screen with data on it - provided by us
• The Canvas
  • Tool bar options
    • Show Event Location
    • Close Screen
    • Hide Spinner
    • Origins
    • Instances
    • etc.
• Conceptual Overview
  • Inputs (for each instance)
  • Connection Points
  • Action Nodes 
    • "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 ) - having written that shouldn't double circle mean more than once and single circle mean once" -David
  • Mappings
    • 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)
  • Initiating 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.
  • Instances/Reusability
    • Concepts
    • Locating Instances
    • Opening Instances
    • Actionflows vs instances
    • Nesting actionflows
•  Connections
  • Inbound
    • No Data = On Click/On Enter
    • Data = Datasource
  • Outbound
  • Lookups (needs example content)
  • 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 (Nested Actionflow) (needs example content)
  • Open screen
  • View (needs example content)
  • Lookup (needs example content)
  • Calculate 
  • Gateway - map to output connection points (needs example content)
  • Open URL
  • Save
  • Analysis (needs example content) 
  • HTTP (needs example content)
  • Email (needs example content)
  • JSON (needs example content)
  • For Each (needs example content) (intermediate)
  • Loop (needs example content)
  • Funnel (needs example content)
  • Start Phase (needs example content)
    • Exercises to build each node in an actionflow
    • Separate app with completed build in
• Referencing additional data Start Phase 
  •  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 ) 
• Phases
• 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
• Working with structured data 
• Confirmation dialogues (intermediate)
• Security and permissions (advanced)
• Record throughput and behaviours 
• Exclusion Groups (advanced)
  • Concurrency?
• Where they can be initiated

Additional Topics (advanced)

• 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 (need example content)

• Counting records (lookups) (intermediate)
• Checking for duplicates (lookups) (intermediate)
• Checking a value is in a list (lookups)
• Setup an API end point (intermediate)
• Configuring a Validation Phase (or another example?) (intermediate)
• Verify a record is selected (validation)
• Configuring a Confirmation (intermediate)
  • Custom confirmation message and screen (advanced)
• Debugging guide (intermediate)
• Configure buttons
  • Pass data between screens
  • Populate a field
• Dragging and dropping on a kanban (tutorial)
• In grid editing Actionflows(intermediate)

Actionflow Course Plan

Content Structure

Remember that each chapter must work within the course but also as a standalone help page.

Objectives:

• Learn Theory (Diataxis: Explanation) - learn the concepts and develop an understanding
• Follow a Practical - follow along and build an Actionflow together, being guided by the Help
• Complete a Task - challenge the trainee to use what they have learn to independently create an Actionflow

Learn Theory.

Understand course structure.

• Short introduction to the course
  • What is covered
  • How the course works - explain levels (beginner, intermediate, advanced) and that each level = 1 day training
  • Explain where data and resources can be found
    • School Data - Learning Centre:
      • Departments
      • Class Rooms
      • Teachers
      • Courses
      • Students
      • Course Attendees
    • Resources:
      • Course Management Screen - include search bar, filter buttons, toggles,
        • Courses (Grid)
        • Teachers (Card Container)
        • Course Attendees
        • Classrooms
      • Course Form Screen
      • Teacher Form Screen
      • Student Screen?

Actionflow Basics

Learn Theory.

Understand what an Actionflow is.

Answer the questions:

• What is an Actionflow?
• How are Actionflows used in PhixFlow?

Provide a list of key principles/rules to follow when creating Actionflows.

Getting to Know Actionflows

Learn Theory.

Understand the elements that make up an Actionflow.

Include from Understanding Actionflows: Overview, Actionflow Page Layout, Connection Points, Actionflow Record Processing, Nodes, Node Connections and Mappings.

From Wiring Actionflows: Adding & Connecting Wires, Inserting Nodes onto Wires, Disconnecting Nodes, Removing Wires

Follow a Practical.

Understand and become familiar with the resources.

Create an Open Screen Actionflow with guidance.

Pre-Task Information:

• Open the Course Management ERD. Explain the data and relationships. View the data.
• Open the Course Management Screen. Explain items on the screen. Which table is backing what.
• Open the Course Form Screen. This is the form that we will later configure to add new courses to our Courses Grid and edit them.

Practical:

• This is the form that we would like to use to add courses to our Courses Grid and edit them. In order to do this we must create two Actionflows - one that gives us an empty form so we can add a new record, and one that gives us a form containing the data for the course that allows us to edit that information
• Walk through the Add and Edit Actionflows 
  • Mention that there is a wizard that can do this for us but it is useful to build one ourselves to see and understand the mechanics
• Demo both Actionflows working

Creating Save Actionflows 

Follow a Practical.

Create a Save Actionflow with guidance.

Practical:

• Walk through creating the save action on the form. 
  • Mention the wizard
• Demo Actionflow working

Follow a Practical.

Create a Calculate Action with guidance.

Practical:

• Walk through adding a calculate node to the Edit Actionflow that adds the string: "Editing " + course name, to the header
• Demo Actionflow working

Learn Theory.

Follow a Practical.

Understand the logic behind filter buttons.

Explain that we can create filter buttons to filter the records in our Attendees Grid by using a combination of Actionflows and background filters.

This works by creating a hidden string field that we populate with a CourseID, using a calculate actionflow. We can then use this string field in our background filter to only show Attendees matching the selected CourseID.

Learn Theory.

Follow a Practical.

Understand how event handlers work.

Create an Event Handler with guidance.

Modify an Event Handler independently.

Create an Event Handler independently.

Theory:

• Walk through the different types of event handler and common uses.

Practical:

• Walk through

Complete a Task.

Create a Delete Actionflow independently

Modify a Calculate Action independently

Modify an Event Handler independently.

Create an Event Handler independently.

Delete Action Task:

• Create the Actionflow for the delete action on the form
  • This is exactly the same as the save action but it uses the Delete node

• Expanding area - review completed Actionflow and demo
  • Recommend:
    • Did they get it right? Proceed
    • Did they get it wrong? Go back and review previous chapters or watch the Actionflow fundamentals video

Calculate Action Task:

• Modify the calculate node just created so that the string instead appears on the Course Name field

Event Handler Tasks:

• Modify the
• Create a