I am not sure to follow.
If you want to send an email whenever the email fields are submitted, then you want exactly what I outlined:
sending an email whenever the field is not submitted empty.
If you delete the email in that field, and submit the form, you still want a notification?
Meaning, you want a notification in any case, wether the field is populated or not?
Then you do not need such a condition at all on the field.
If you want it to be sent only when it's changed (for example, it was previously empty but now has a value) you can set that so with the checkbox next to it.
I think you wan an email whenever the user changes the value.
So, you can set the comparison as empty (just delete that custom email value you have right now, a@a.com, from there, leave that empty)
Check the Checkbox "only when field changed" and compare with <>
This will now check if the field is not empty, and the value did not change from before, the email is not sent
If it has changed, and is not empty, its sent.
If you remove the checkbox, you will get an email all time the form is submitted, with any field value, but not when that field remains empty.
In Relation to:
Why do I need to create a new user field when I have already created that? Is there something am missing out? Also The notifications used to work before, so thats why am confused on why it stopped working.
I never said you should - these are the steps I did follow in my local test, that I made, to test the issue you describe and be sure, I do not tell you something read off the books but from first hand:
That works great with the latest Toolset Versions.
1. Create a Custom Email User Field
2. Create a User Form to edit users
3. Autocomplete the Form
4. Set a Notification to be sent when the form is submitted and the field (nominee email) is not empty (<> comparison to nothing)
5. Email receiver is the field as well
6. Submit this form with no email in that field > No email is sent
7. Submit this form with an email in that field > Email was sent
Can you try with the suggested steps?
==> If everything fails, the first step is always to try the suggested steps on for example a fresh form, or the same form with the same fields, of course, you do not need to re-create it.
It's meant to be a test, a confirmation that we speak about the same process and that this is not solving anything on your end.
The notifications where not working fine before, actually they where not working nice at all.
We mace several updates, fixing them lately.
It may be that this is a cause of that update.
It is however, if working the way I suggest (which it does locally) solve by adjusting that setting (and eventually, re-saving the form and connected field)
Please let me know if that helps