Actionflow Intermediate Module

Overview

Welcome to the Intermediate module of the PhixFlow Actionflow course. In this module, we'll explore Actionflows requiring sophisticated processing logic, such as using HTTP actions and understanding phases. By the end of this module, you'll have all the tools and knowledge to configure intermediate-level Actionflows

Prerequisites

Resources and Data

All of the data used in this course is preloaded into the Actionflow Intermediate Application on your training instance. To obtain a training instance, contact support@phixflow.com.

If you would like a copy of the Retail Data, it is available from the Downloads section of the Learning Centre.

Pre-Built Application

The pre-built application, Actionflow Intermediate Application, can be found on your training instance. It contains an ERD with data and a number of screens that are referenced throughout the course. 

Application Overview

Before we dive into the course, let's first become familiar with the data and screens we have provided for you. Remember to not delete any tables or screen components as this may cause the processes to fail.

The data provided is for a clothes shop and contains orders and stock data, as well as the shop's customers and staff members.

  • Spend some time studying the ERD diagram to understand the data and the relationships between each table
  • Review the list of screens we have provided to see how the data is presented on each screen

Module Tips and Troubleshooting

Here are our handy tips and tricks for success in this module.

Tips for Success on this Module

  • Use the names we provide - When naming certain components, Actionflows, buttons, etc. if we have provided the names to use, we recommend you use these to ensure that when these objects are referenced later in the module, you can easily find them 
    • Likewise, avoid renaming the objects we have provided in the application
    • Where we have not provided a name, use the guidance at the start of each example to give your components a suitable name
      • We recommend the names you create clearly indicate the functionality and could be understood by a user seeing them for the first time; this includes the names used for action nodes
  • Work through the chapters in order - The chapters have been carefully constructed to ensure they follow a logical order, build on the topics covered previously and level of difficulty. Any links on the page should be considered as further reading once the module is completed to ensure a full understanding of the topic
  • Build your own test screens - When you have completed the module, use the test data (or import your own data) to build your own screens or change the ones we have provided. Use your new knowledge and skills to practice the concepts you have learnt

Troubleshooting

  • If you go wrong at any point and alter your data in an unexpected way, you can roll back your test data to its original state - see Rolling Back Test Data
  • Contact PhixFlow Support via the  ChatBot, available in  Design Mode from the system controls in the top right of PhixFlow. Our team is happy to assist you with any questions you may have.