Consideration for 4.0 - Server Action/App Flows selection

I am switching between projects to work on a desktop app and modify the API actions that feed it. A small(ish) annoyance that has crept in since adding the App Flows section to Workflows is that it remembers the last one used which in many use cases is ideal. What it means, though, is when switching between App project (where Server Actions aren’t available) and API is that it always starts on App Flows and you have to then click through to Server Actions. Could remembering the selection be project specific to account for this?

Add a vote Ben!

:slight_smile:

1 Like

Done - sorry, didn’t see that one…

1 Like

Cheers Ben and no worries. Like yourself when switching Projects its a bit annoying as Server Actions are far more relevant and no doubt used a lot more than App-Flows…

1 Like

I totally agree but have only noticed it since working on an App project - I suspect most Wappler users are using it for web projects and don’t notice it! Hopefully it will be improved for 4.0

1 Like