Wildcard characters can be helpful when testing for text in field conditions. The alternative could mean that many many field conditions would need to be developed.
Also, distinctions in text testing (for field conditions) may include whether case sensitive tests are performed; lowercase text, uppercase, or any variation.
Howdy John,
Thank you for this feedback!
We've recently released the first part of "Contains" conditions for both Android and iOS. The new functionality includes the ability to do "contains," "starts with" and "ends with." The ability to do the opposite ("does not contain," etc.) will be coming soon as well.
Release notes with further details can be found here.
At this time, we don't have an ETA for case-sensitive Conditions for the 'Contains' functionality. We are continuing to collect and provide feedback to our Development team for their consideration, so we would love to hear from other users who want to see case-sensitivity for the 'Contains' Conditions!
I would recommend upvoting this related Feature Request on case-sensitive Conditions:
Please sign in to leave a comment.
Comments
1 comment