Getting started with App Connect Flow

[TomD]

you have your code wrapped in {{}}

Yes, but I didn’t enter them manually. It was all done via the UI.

[cdjackson]

It was all done via the UI.

Strange - I did everything through the UI and didn’t get the brackets. This is also why I tried to convert the working action to a flow as I figured it would remove any potential for me to get the wrong format.

[TomD]

That’s strange. Perhaps it’s a bug which will be resolved shortly. It might be worth reporting it as a bug.

as far as I understand I can’t have a conditional action

I didn’t answer this, thinking it wouldn’t be necessary as it’s easier to use a flow. However, you can have conditional actions, eg:
dmx-on:click="var1.value==1?modal1.show():modal2.show()"
… but you can’t do this via the UI.

[George]

as indicated earlier inline flows will be improved in the next update. It is also preferred to use separate page flows for complicated flows and not inline flows @cdjackson

[cdjackson]

So I confirmed that for me at least, editing a flow (adding an action into a flow) doesn’t add the {{}}. Removing the ’ that is added, and adding the {{}} works for the simple example of showing the modal, but

gives the following error -:

The action that was added before the modeal.show() is -:

{{parameter_query.set('parameter_id',tableRepeat1[0].id)}}

In the code, this is -:

<tr dmx-on:click="run([{run:{action:&quot;{{parameter_query.set('parameter_id',tableRepeat1[0].id)}}&quot;}},{run:{action:'{{parameter_edit.show()}}'}}])">

as indicated earlier inline flows will be improved in the next update.

Thanks - when is this expected?

It is also preferred to use separate page flows for complicated flows and not inline flows

Ok, thanks. Although I’m not sure what I need to do is too complicated - it just requires two commands to be run, but I’ll keep this in mind in future. In general, it’s a nice feature (once it’s working ).

[George]

This is because of a inline flow expressions bug that will be fixed tomorrow:

Inline flows generate wrong quotation

Found the problem - seems with inline flows we were generating a bit too much quotes Actually and single quotes and backticks - while the right syntax is just the backticks for expressions. Will be fixed in the next update. Anyway try using more page flows than inline flows for complex flows. Those can be also nicely reused.

[Teodor]

Guys please check:

Introduction to App Connect Flow

What is App Connect Flow With App Connect Flow you can create client side workflows with actions to be executed, data to be retrieved and much more! All actions nicely executed one after another. Use rich programming paradigms in your flow like repeaters, assign of variables and conditions. Make reusable flows as on your page as components, or inline flows as actions on your dynamic events. With the same ease as you are used to create Server Connect workflows - now you have all the powers cl…

[Akayy]

This thread might be helpful w.r.t your question about what to do after a wappler update - Wappler update and js/php library files refresh in individual projects

[Akayy]

@TomD

Perhaps viewing the console output might help. Clicking a button described above, I see:

Hi @TomD, I’m playing around with flows, and curious to know how you go this console output? I’m on mac & chrome is my browser, I can’t see anything like yours.

[George]

To get debug info in the dev tools console, you need to enter first:

dmx.debug = true