Want to trigger a workflow on change of an element’s value—Checkbox test—but I’m confused about the workflow execution bound to this event.
I want the value of Checkbox test to fire one of two events, so instinctively I’m trying to find some if…else analog. How do I do this in the workflow chain? I think the state change is happening before the evaluation—is that correct? Such that sequential actions might be cancelling out?
Or do I have to have two separate event triggers: on Checkbox test value change, checked and unchecked?
Without having the full picture, it seems like 2 separate event triggers is the way to go. You’ll find that there are many ways to accomplish the same thing in Bubble. The goal is to pick the most optimized.
Here it would be a task with multiple yes/no fields, eg finished, assigned, reviewed, billed, etc.
Presumably one conditional event can check for changes in multiple fields (a la: if…else if)? Otherwise it seems like a lot of workflows to debug or change… (I’m trying not to think too much about optimization right now, but its always on my mind).
Surely this a common use case?
Since my OP, I’ve looked into auto-binding; at first glance it seems like it could be the solution, as it would completely eliminate the need for workflows to handle the state changes. Thoughts?
Auto-binding is great for saving input values in database fields. That’s about it. Auto-binding doesn’t have much flexibility outside of that.
If you want to run additional actions as a result of a change, events is the way to go. Whether that’s 1 event with many conditional actions or many events with conditional actions, that’s up to you.
