Adding data bindings to runJS in a flow will break the flow & flow editor

Wappler General Bugs
#1

Wappler Version : 4.7.1
Operating System : Windows 11
Server Model: NodeJS
Database Type: MySQL
Hosting Type: Custom

Expected behavior

Using data bindings in the arguments section in runJS within a flow should work as expected and not break the format.

Actual behavior

The flow will break as weird formatting is applied. The flow can no longer be edited in the flow editor as it is not detected as a flow, and the browser console will produce the following: Error: Lexer Error: Unexpected token 's' at column 145 in expression [run([{runJS:

How to reproduce

  • Create a follow attached to a success event on a form (assuming this occurs everywhere, though).
  • Add “Run JavaScript” to the flow.
  • Enter a name and function.
  • Add arguments. In one of the arguments, add data bindings along with text and the flow will break.

Gif:

Wappler_mwn9Xk46lr
Wappler_mwn9Xk46lr1799×982 1.1 MB

#2

Had the same thing recently. George explained that more complex flows should be within a page flow. So you can set up what you want in a page flow component, and then start the page flow from that action

#3

I haven’t tested it on page flows, but this isn’t really complex and it was working in the past so I’m hoping for a fix soon as it’s a huge inconvenience to have a bunch of page flows instead.

#4

It is caused by a rogue apostrophe in the code that’s produced for the function’s arguments and has been reported here:

You can remove the ’ before the first backtick as a workaround until @george and the team fix it in the UI

1 Like