$sequence numbers$

If either one of those conditions are not met, you can simply reset the input.

With those two lists in place, it isn’t difficult to have workflows that check to see if a number the user has entered is an allowable number (i.e., does the first list contain the number) and that the number hasn’t already been used (i.e., does the second list contain the number). One of those lists holds the allowable numbers (which are added to the list when rows are enabled), and the other list holds the numbers a user has already entered (which are added to the list when the user enters numbers in the sequence inputs). My example is centered around having two custom states, both of which are lists of numbers. I’m sure I could play around with it some more and get that use case working, but I’m far enough down a path that I figured it couldn’t hurt to throw some stuff out there as food for thought.

Hi there, this post looked like a fun challenge, so I put some time into it, and I have a working example that does everything I think you would want this feature to do with one exception… it doesn’t handle the situation where a user has a number in a sequence input, and the user removes that number.

Sequence numbers