- Created by Anthony George , last modified by Zoe Baldwin on Jan 12, 2024
You are viewing an old version of this page. View the current version.
Compare with Current View Version History
« Previous Version 12 Next »
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.
- Tool bar options
- 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.
- Event handlers
- 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)
- Inbound
- 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 )
- Lookups
- 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
- Mapping attributes In and Out
- 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
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
Chapter | Level | Page Name | Objectives | Content |
---|---|---|---|---|
Parent page | Actionflow Course | Learn Theory. Understand course structure. |
| |
1 | Beginner | Actionflow Basics | Learn Theory. Understand what an Actionflow is. | Answer the questions:
Provide a list of key principles/rules to follow when creating Actionflows. |
2 | Beginner | 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 |
3 | Beginner | Creating an Open Screen Actionflow | Follow a Practical. Understand and become familiar with the resources. Create an Open Screen Actionflow with guidance. | Pre-Task Information:
Practical:
|
4 | Beginner | Creating Save and Delete Actionflows | Follow a Practical. Complete a Task. Create a Save Actionflow with guidance. Create a Delete Actionflow independently | Practical:
Trainee Task:
|
5 | Beginner | Adding a Calculate Action to an Actionflow | Follow a Practical. Complete a Task. Create a Calculate Action with guidance. Modify the Calculate Action independently | Practical:
Trainee Task:
|
6 | Beginner | Understanding and Creating Filter Buttons (Calculate Actions) | Learn Theory. Follow a Practical. Understand the | 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. |
Beginner | Understanding and Creating Event Handlers | Learn Theory. Follow a Practical. Complete a Task. Understand how event handlers work. Create an Event Handler with guidance. Modify an Event Handler independently. Create an Event Handler independently. | Theory:
Practical:
Trainee Task:
| |
Beginner | Creating an Open URL Action | |||
Intermediate | ||||
Advanced | ||||
- No labels