Questions around client side logic, aka "Inline Flows", "Page Flows" and "App Flows"

I try to get my head around the client side of scripting, aka “Flows” with Wappler and want to confirm if I understand the concept correctly. I would appreciate if you, as experienced users, can chime in and either confirm or correct me where I went wrong.

For me, it looks like we have four ways of scripting “complex” logic in Wappler:

1. Actions
2. Inline Flows
3. Page Flows
4. App Flows

Actions and Inline Flows are available on dynamic events on specific page elements.
(On “static events”, I can’t do anything except entering something, no Actions Editor or Inline Flow Buttons available?)

1. Actions

• Not reusable as they are attached to specific event of a specific element
• Call methods (“Actions”) on components that are available on the current page
• No input parameters
• No return values

2. Inline Flows

• Not reusable as they are attached to a specific event of a specific element
• Accept input parameters, can’t figure out why (bound to a element?) and how to use them
• Call methods (“Actions”) of globally available components
• Supports a “run” step which utilises the Actions Editor (as in “1. Actions”)
• Has a “Enable Output” toggle on steps, but how to access this result?
• Supports conditions

Page- and App Flows are globally, either for the page or the app

3. Page Flows

• Unlike Actions and Inline Flows, Page Flows can be called from different events of different elements across the current page
• Return values (“output”) are avaible via data binding
• Auto Run works perfectly, but how to call Page Flow from a dynamic event, as a button click?
• Again, can’t figure out how to pass params, are this query params?

4. App Flows

• Separate Flow Editor in Workflow Tab
• Globally available to all pages
• No access to components like Capacitor or SQLite (why? Espcially SQLite would make sense here?)

Questions in general:

• Where to find documentation about the steps / actions, like the Data Sources (Assign var, Set Global, Set Session/ Remove Session, No read Session? / Set or Remove Storage, no read?), what are Data Sets? Columns? (to name a few…)
• How to run subsequent flows, e.g. branching after conditions? Run Flow step seems to support a Flow attribute, but what to enter here? Do I have to import all flows, including subsequent flows into the page and name them identically as in the Workflow tab?

Observations / bugs found while writing this:

• None of the steps that require external JS work, Toast, Bootbox, Capacitor… (JS not found, as it’s not added to the page)- Inline Flow editor randomly didn’t save changes OR emptied the editor (while the script was still visible in code view)
• Added Capacitor to the flow (Wappler had to install the package first), the flow editor closed on save and was empty afterwards
• On the Inline Flow editor, Framework7 have been availble even if the framework wasn’t available / added to the page/project (Bug?)
• App Flows: Params not working (emptied after re-opening the editor, bug)
• App Flows: Data Binding for return variables not availble in data picker, only data, had to add name of the variable manually