I wanted to ask you if it is possible to add more routing rules options to the switch node
since at the moment we only have:
Boolean
Equal
Not Equal
Number
Smaller
Smaller Equal
Equal
Not Equal
Larger
Larger Equal
String
Contains
Equal
Not Contains
Not Equal
Regex
I think, as an improvement, the following routing rules would be of use:
Has key
is between
is null
is not null
is of type
is empty
is not empty
head
index between
tail
JSONata expresion
My use case:
For example, if I have a flow that receives a value from an endpoint and I want to easily determine if that value is empty, I could use the “is empty” matching rule to process this information.
Hi @BramKn ! sorry, I’m new to the community and didn’t quite understand how it works. I wanted to check how I can see the status of my request, more than anything to know if it will be considered sorry for the inconvenience
We typically base new features on the amount of votes a feature has from the community, This request is not something that I have seen anyone mention internally yet but it looks like some of those options would make sense to add.
I suspect some of this will happen but it is likely to be something that would happen in months rather than days or weeks.