I’ve been trying to build a simple internal tool for my team to track project requests, and I started using a visual development platform. It feels like I’m 90% of the way there, but I keep hitting this wall where the logic for approvals just doesn’t behave the way I expect. Has anyone else gotten really close with one of these builders only to feel stuck right at the finish line?
I have been there too. you are almost done and the approvals logic stubbornly refuses to stay in line with the rest of the workflow. that last step can feel personal.
From a systems view I would try turning the approvals into explicit states pending in_review approved denied with clear entry and exit rules. separate the decision tree from the UI.
I once assumed it was the UI but the real issue was a race in how events fired the moment someone hit approve. sometimes a tiny delay or a lock solved it.
Maybe the platform is not the blocker perhaps the mental model is too rigid for a no code builder.
Reframe the goal what problem are you solving with approvals speed auditability or escalation changing the frame might reveal a simpler path.
One trick I use is add a tiny override flag for edge cases so the common path stays clean yet we can handle the rare case without breaking rules.
Idempotence is a concept that helps here making sure a repeated approve does not wildly change state.