How do I route forms with nested dropdowns in a workflow builder?

[Emily_R]

I’m trying to build an internal tool for my team to manage project requests, and I’ve hit a wall with the logic for routing forms based on multiple dropdown selections. The visual workflow builder in my platform just doesn’t seem to handle these nested conditions cleanly. Has anyone else run into this specific limitation when designing complex forms?

[PaisleyPC]

Yep, I ran into this too. The visual workflow builder would choke when two or three dropdowns started steering the path. We moved the logic into a tiny rules service that builds a key from the selected values and returns the destination. It wasn’t elegant, but it kept the UI from collapsing under complexity. Latency rose from about 20ms to 40–60ms per decision as the rule set grew beyond a few dozen combinations.

[DanielL]

I tried wrapping it with a big backend if-else block, but every UI change meant flinging in new branches and tests started failing. We ended up tagging requests with a profile per project type and feeding that into a small decision engine instead of chasing the UI logic every time.

[Luke.J]

Could be the real issue isn’t the nested conditions but the data model. The form fields didn’t map cleanly to what teams actually need, so the engine kept misrouting after a tweak.

[Zachary.R]

Off topic for a second, I spent a week arguing about what to call 'stage' versus 'status' and which dropdown should drive what. By the time we got back, the nesting felt even more pointless, so we punted to a lighter approach, but there are still edge cases that nag at me.