The workflow page is where we “code” and where most of us spend most of our time. A little organization improvement would really enhance our productivity.
This is the hot mess I have to deal with. Grid is not good UX. It’s not a great way to browse, and since search is lacking, this isn’t a great experience:
This is brilliant! I try to use color coding to have the same effect, but that’s only as good as I am at maintaining it and besides, who says the color blue relates to page loading? Way easier to group by type and then optionally one can use color coding for other things such as specific functionality within a component.
This. For a quick short term UX update, some sorting and some basic hide/show would be great. Example: There are a bunch of workflows i have that are just for showing/hiding popups… I’d love to hide those workflows. They take up space and distracts from the big ones.
Another great insight! I’d love to be able to completely customize what’s in that box. I have so many conditionals on some workflows that I can’t read it.
I love this thread as it’s geared toward making our lives as developers easier along with speeding up our development.
Totally, that’s my biggest issue, this view is unusable. Currently I need to find the element and click on “Start/Edit Workflow” to find the workflow node. It’s not a view that can be used easily to review one’s code.
I’m excited however, to see enthusiasm by some in the Bubble team. It’s been a long time since we’ve had any productivity improvements to the way we code. Sure, the new engine is god-sent, but it’s the day to day laying down of workflows that needs a little boost.
IMO, the Bubble UI, generally speaking, is needlessly laden with text. As one simple illustration, why should we have to name an element to indicate its type? I mean, every element already has an icon associated with it in the left panel of the design tab. Why doesn’t that same icon also appear in the elements tree, in the properties panel when an element is selected, on the workflow, etc?
More than once, I’ve used the “replace with a different type” feature but forgot to change the element’s name to reflect its new type and was then momentarily confused at some point because it wasn’t the type I thought it was. Totally avoidable with an automatic visual indicator of its type instead of me having to tell Bubble what it already knows by manually labeling it.
Having said all that, to be fair (and perhaps you already know this), the workflow view does have both a list view and search/quick find…
I don’t actually use the list view much (although I might if it had sorting and filtering), but the search in the top menu bar is super handy if you have a good naming convention.
Not sure how easy or difficult this would be to reliably pull off but it would be neat to accurately show the sequence in which steps within the workflow are executed.
For those who have been around here a while, we know that just because it’s Step 1, Step 2, etc doesn’t mean that these actions are fired in that order, and can fire earlier if there are no dependencies in earlier workflow steps.
I also have lots and lots of tiles on many of my elements.
I try yo use some kind of Color coding for certain kinds of events, try to make some hierachy, but everything is just to combersome. I also find really difficult to do “similar code”…
Some times I have events that must perform “almost the same”, but not the same.
Sometimes I copy paste all the workflow, but then it is an hassle to change, more often I try to do the workflow from scratch but then I can’t remember all the steps and need to go between workflows many, many times… some times they don’t have a similar name and are “randomly” placed on the page.
There should be some kind of “export” representation where one could see all the workflow (do search parameters, and inner :filter, advanced:…). This is a “no-code” platform, so “import” would be almost out of the picture… although I would really enjoy be able to write stuff instead of just going “drag&drop”.
Even more cool would be the hability to program workflows within workflows… sometimes I do “trigger” element events from workflows and it would be great to be able to edit them “in place”, instead of jumping to a completly different workflow to “tune up” a minor change. If there is some kind of “visual condition branch tree”, even better.
Finally… just asking… Multi-parameter parameters on triggers… At the moment an workflow can only receive one object. Sometimes it is enough, others, it isn’t… I’m not keen on creating data structures to support one peticular workflow. Multi-parameter would be a great improvment.
