What's the point of App Flows if you cannot pass values into them?

Is anyone using them in mobile apps, or are you facing the same issue?

Just because you deserve being acknowledged I came to say that unfortunately I don’t have your problems because of two things:

  1. I don’t use client flows.
  2. I don’t use the mobile part of Wappler.
1 Like

Thanks for nothing @JonL! :stuck_out_tongue:

1 Like

I’ll add that I use page flows a lot, but never use app flows…mainly because you can’t easily bind things, pass values, etc. It always felt like a feature started, but not quite finished. Maybe that has changed since I last checked (many months ago).

Sadly, it has not so setting up one Flow to use across the entire app is not possible.

How are you trying to pass params to app flows?

When defined like this:

params just comes as options when used:

Hi George, not sure how it's showing for you. The Input Parameters are blank everywhere for my App Flows. It doesn't show in the main properties panel of the App Flow or in the Actions Editor (this is the more important area that it's missing in).

Are you doing this in a web server project or a mobile project? It seems like a web server based on your image above showing “Server Actions”. Could you test on a mobile project?

Het was indeed on a web project, will check mobile

1 Like

well tested on mobile as well and the input params, appear always.
On index pages, on content pages, even on run flows:

check with capacitor, electron, and bs projects. All working fine.

Did you saved the app flow before usage? Also do you have an App ID key on your pages?

image

Try maybe on different pages or projects and see what is the difference to isolate the case

Thanks George! For some reason the src is pointing one directory up when I select in the UI. src="../app/flows/gmail_copy.json" instead of src="app/flows/gmail_copy.json". After I manually changed it, the param showed. :relaxed:

1 Like