Other low code tools like Retool allow you to specify an onSuccess and onError callback function that runs after the query. This would assist people who are non programmers to assign actions to queries after they run like setting variables among other things. This feature would also allow chaining queries using the GUI which would also assist less technical users.
Current solution:
Call the query in a JS file and run some JavaScript after the query returns.
Example:
I want to set a global variable called lastRefresh to the current time after a query runs by simply selecting the getCurrentTime() function that was previously defined.
Why should this be worked on?
The purpose of a low code tool is to offload work from the dev team to less technical team members. This feature would make it easier for non technical editors to utilize query call back functions and reduce dev team involvement.
Thank you for this feature request. While it is not possible to get to it immediately, we have added it to our backlog, and will post any updates here.
Is there an existing issue for this?
Summary
Other low code tools like Retool allow you to specify an onSuccess and onError callback function that runs after the query. This would assist people who are non programmers to assign actions to queries after they run like setting variables among other things. This feature would also allow chaining queries using the GUI which would also assist less technical users.
Current solution: Call the query in a JS file and run some JavaScript after the query returns.
Example: I want to set a global variable called lastRefresh to the current time after a query runs by simply selecting the getCurrentTime() function that was previously defined.
Why should this be worked on?
The purpose of a low code tool is to offload work from the dev team to less technical team members. This feature would make it easier for non technical editors to utilize query call back functions and reduce dev team involvement.