Versions Compared

Version Old Version 16 New Version 17
Changes made by

Zoe Baldwin

Zoe Baldwin

Saved on

Key

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

Insert excerpt
_Banners
_Banners
nameactionflow
nopaneltrue

What is an Actionflow?

A diagrams that represent

An Actionflow is a diagram that represents a sequence of actions and data flows within an application

control

. It controls the interactions users have with an application and its data, e.g. opening a new screen to edit data

belong to an application or package, and can be reused in multiple locations within your application but with different inputs, e.g

.

address cleansing/finder

Actionflows are composed of individual

actions 

actions (represented as action nodes) that each perform a specific task, e.g. opening a screen or saving data

, and have input and output connections to screens, buttons or tables.

  • are designed to be composable, e.g. can be combined and are "data agnostic"

    • Actionflows belong to an application or package and are represented by the Image Modified icon

    COMPOSABLE DEFINITION: Composable architecture is a microservices approach to building your tech stack, combining a constellation of different reusable technologies to create one unified system that can communicate via APIs

    .

    This breaks down complex ecosystems into more manageable chunks for better oversight, flexibility, and adaptability

    Example Actionflow

    This is an example Actionflow where a user clicks to save data. All images in this course can be clicked on to make them larger.

    Why are Actionflows used in PhixFlow?

    Actionflows make PhixFlow applications interactive. They convert a static screen into a user interface, combining simple individual actions into complex functionality. This enables the application user to interact with the screens and data.Reusability ..

    Actionflows are reusable across an application but with different inputs, making Actionflows flexible and efficient, and ultimately saving time and effort.

    Actionflows are composable and interchangeable. This modularity allows for the creation of dynamic and adaptable Actionflows, that are "data agnostic".

    Add infographics - AG to provide updated diagram

    The Principles of Actionflows (put in own page)

    1. All Actionflows require an input, this can be data or an input action (user interaction or scheduled task/task plan)
    2. To use data within an action node it must be mapped into an input parameter for that node
    3. Action nodes return data to the Actionflow as Output Attributes
    4. Actionflows only require minimal data to be mapped in for it to run, e.g. just the primary key, because we can look the data up using a unique identifier (UID)


    21.3 Getting to Know Actionflows