I’m glad you found the problem. I expect I’ll prefer to use the flow component anyway - the code is easier to read apart from anything else.
When you say flows can be ‘reused’, I imagine you only mean on the page - eg from different buttons or events, sending different parameters perhaps. Is it possible to store a flow externally, and call it from different pages?
Also, I see parameters can be sent to flows from buttons, which will be a very useful feature - but I’m not sure of the process. Perhaps after a bit more fiddling with it I’ll understand.
I think you were right when you said this could be a game-changer
You can do this now. I wouldn’t have thought the problem converting dynamic events is relevant. You first add a flow component, with whatever conditions you need, and then attach it to a button. The button can optionally pass parameters to the flow, which might be used in relation to the conditions. I’ve only tried passing single parameters but it seems you can also pass multiple parameters - I imagine as arrays or perhaps JSON; hopefully some documentation will cover this at some point. No conversion is involved at any stage.
My understanding of the new flow feature is pretty minimal - I don’t think it’s quite what I imagined it was going to be - but I think the above is correct.
Yes, that’s what I’m trying to do, but it requires flows to work, right? That’s why I want to use a flow - as far as I understand I can’t have a conditional action? Or is that wrong (sorry - I’m quite new to using Wappler - just 1 week).
No - I agree. I was simply using that as an example of the fact that flows aren’t working. I’ve taken a standard, working, dynamic event, and pressed the Flow button so Wappler converts it to a flow with just this same single event, and it no longer works.
I totally agree that I could have done this without starting from a dynamic event - and I also tried that, but I figured that starting with an event that worked, and then having Wappler convert it should also work and it should have removed any possibility that I screwed something up?
Thanks. I’m totally in agreement with you - but it just doesn’t work for me at all. I also removed all my server side components and reloaded them thinking that maybe Wappler hadn’t updated to the latest 2.6.0 files, but that also didn’t help.
Unfortunately until I get this resolved I’m a bit stuck .
Initially I wanted to check the branching by displaying the value of $param.id. However, it seems the scope of these variables is local to the flow (which makes sense). You could assign these variables to other variables if you need to display them etc.
It’s not a very useful example, but hopefully it will clarify matters.
Ok, thanks. I’ve fundamentally done something similar, when that didn’t work, I reduced it to the simple one line action I presented above, but that also doesn’t work.
Short of updating Wappler itself, is there anything else required to ensure the runtime files are also updated to the latest version? I assume Wappler updates local files (eg all the Server Connect PHP files) when updating the application?
I expect you have the right versions of App Connect - 1.9.0. I’m not using much else on this page - jquery-3.3.1 and the Table Generator and Modal extensions (and the current version of Bootstrap).
I think Wappler updates local files when relevant components are used. There is the odd issue with this however. You could delete this folder:
and restart Wappler or reinstall from scratch. I’ve never needed to do either of these.
Perhaps viewing the console output might help. Clicking a button described above, I see: