- workflow where items flow from one role to another
- less "code" for things like dependent drop-downs...where one field drives the drop-down choices in another field. Excel can do this, but with fairly complex macros
On that last one, I imagine there's more examples where Excel stops being "low code" because you're using complex macros. It's more flexible, but that's the tradeoff.
It is incredible in some teams how difficult it can seem to be to get from "we need a 1-page website" to "ok, it's online and you can update it simply without any more of my help. Here"
And with the difficulty going up, the likelihood that you'll do this when it's needed and makes sense to do goes down. I can't tell you how many times I said "I need a website" and didn't end up posting one, because we didn't have a ready answer to this question, and nobody could be bothered to go out and build one.
Just a simple one page website. I can think of at least three "easy" ways to do it (and that's my whole problem in a nutshell, thanks for coming to my TED talk.)
- role-based rules about views, edit rights, etc
- workflow where items flow from one role to another
- less "code" for things like dependent drop-downs...where one field drives the drop-down choices in another field. Excel can do this, but with fairly complex macros
On that last one, I imagine there's more examples where Excel stops being "low code" because you're using complex macros. It's more flexible, but that's the tradeoff.