Comma Separated List/Difference in "is" and "contains" in Workflow Conditionals
under review
B
Brandon Grosso
Right now when you use an if/else in the workflow conditional you need to add an "or" for each different conditional. Sometimes this is not ideal. For instance, wanting to condition based on post codes. It would be great to be able to use a comma separated list of all the possible post codes, instead of adding each as an "or". It would be great if the "is" operator can include a single variable and the "contains" operator can include the possibility of a comma separated list so there is a larger difference between the two.
Log In
K
Karim Bel Hadj Soulami
100%, I'm wasting so much time on this when building solutions for my clients
A
Alex Hisen
Being able to use a regular expression would be even more flexible
M
Michael Romrell
yes please! I'm currently adding If actions based on State and I have to have 100 separate conditions (ex: one for AZ and one for Arizona). Comma-separated values would make this MUCH easier.
Core Platform
under review