webwildfire

Hi Abul! Thank you for taking the time to address my post.

Restrictions based on keywords work with comma-separated values. So, if you have multiple words, you would need to separate them with a comma.

You’re misunderstanding my issue. You’re thinking I’m saying I can only use 1 word in the restrictions list, which is not what I meant.

When I tried it, I just had the 1 word, and it would only block it if that was the only word used in the text box in the form itself. A user could submit a sentence with the word, and it’d pass.

I haven’t tried it again recently, but if you’re unaware of the issue, it probably needs to be looked at.

And how sensitive are those keyword restrictions? Case sensitive or case insensitive? Word matching like I was doing with regex or no?

There is no option to have “not contains” / “do not match” check in advanced form validation.

Also, it’s not possible to show a successful submission without actually processing the data.

Regarding adding conditions to the email notifications and integrations individually, this can be possible – you can set conditions there individually.

But as I said, the conditions for email notifications and integrations doesn’t work for me because I can’t say “don’t send it if it has this word” if I have to match with regex. So it sounds like I’m correct that the conditions are too limited for what I am considering.

So I would like to suggest adding more options to control these things. The existing conditions are not sufficient for full control.

The only thing is, if you do that, then the entries still get stored.

• This reply was modified 8 months, 1 week ago by webwildfire.