thanks @zach8 . The problems I’m running into are these:
When I create a workflow based on Elements > “an input’s value has changed” - it does NOT fire until I hit tab/enter. The simple act of typing “F” does not trigger the workflow.
If I instead create an identical workflow based on General > “do when condition is true” and I make my Only When condition that INPUT’s value is not empty: this worflow DOES fire immediately after I type “F” but subsequent letters “argo” do NOT re-fire the same workflow. The result is that if I slowly type “Fargo” my state’s query remains with a value of “F” until/unless I hit enter/tab. (And I have the workflow set to “Every Time”)
You could probably modify that workflow with “do when condition is true”. Make the workflow count how many characters are in the input, and then make it update the state when the count changes?
Alternatively: maybe a search input solves this better than a text input? If users are searching for entries in your DB, the search input may simplify everything.
@zach8 thanks for the suggestion! I now have it working.
Interestingly, while the “when input # of chars > 0” workflow would only fire once, when I changed it to compare input’s length to the length of the custom state, it fires every time/with every keystroke. I then added a less-than workflow as well, in case someone hits backspace. And a clearing one too - though this may be unnecessary. Will have to test.
I’m not sure if anything changed since this solution was posted, but today it seems it’ll trigger only once too, like the other conditions mentioned earlier in this thread