Notifications based on blank entries

In a form we can use {BLANK} as a value in the quick search fields and it is working as expected. Using !{BLANK} also works as expected. When I create a notification with {BLANK} or !{BLANK} as the criteria for the same fields, I don't get the expected results - and the variation depends on other factors, like using a custom template for the message.

I want to handle new entries differently, based on whether certain fields have a value or not.

If I use {BLANK} as the criteria instead of all entries, I get a notification whether the field is blank or not. This is true whatever set for the template (none or custom)

If I use the default template, I get a link to the proper entry.

If I use a custom template, I get the values for the 1st entry that has a blank in the field

If I use !{BLANK}, the notification doesn't trigger.

If I check for a specific value in the field (I'm using a checkbox field for all this), the notifications come out properly. But, they may check 1, 2, 3 or all 4 options and that has limitations in the current state.

I tried tracking this through to sendNotificationToEmamil, but it is a rather complex function.

Thanks. Steve

Comments

In the better late than never category...

Hi Steve, sorry this one got missed...so what is the situation you want to cover here? You have a new entry in a form, and you want a notification when certain fields have a value...if it's a checkbox, you need to be careful to use LIKE instead of = because checkboxes do not have a single discrete value necessarily. They could have two or more values, so LIKE gets you a pattern match instead of a literal match.

I wonder if that is the entire solution for you?

I'm surprised there is a difference depending on whether a template is in effect or not...the conditions are evaluated separate from the templating of the message, or so I thought.

Just checked the code...it looks like custom notifications did have a bug that if there was more than one entry you were being notified about at a time, them it would use the same data for the templates for all entries, rather than re-getting the data for subsequent entries. But not sure if that was the issue you faced. This has been changed in this recent commit: https://github.com/jegelstaff/formulize/commit/39543eebeaa7319f55c481ca5...

My guess is that you should be able to use "notify when there's a new entry" and only when field X is LIKE Y and that should work?? You may need to merge the recent commit to get your custom template working, if multiple new entries are being made at the same time...but I can't think how multiple new entries are being made at the same time, that seems odd.

Access to a system to recreate the issue, or steps to recreate, would help of course.

--Julian

Notifications based on checkbox value

Hi, Julian, the basic situation is this - I have a checkbox on a form and want 2 different notifications. One when no option is checked and a different one when any option is checked. For this particular application, there are 4 options for the checkbox.

Using the {BLANK} value in the quick search properly filters the entries, so I was making use of that in my notification criteria.

The verbose criteria are:
IF [new entry] AND nothing in [fieldA] is unchecked, notify me using templateA
IF [new entry] AND anything in [fieldA] is checked, notify group using templateB

When there is only 1 option, using LIKE [a portion of fieldA] does work. But, when there are more options, specifying all those criteria is cumbersome.

The commit you mention might do it - what I was seeing that even though only 1 entry was new, it was not using the entry ID to limit the remainder of the result set. I'll test and let you know.

Steve

Still unable to use {BLANK} in notification criteria

I tried making the changes in the commit you posted, Julian - the notifications using


When a new entry is created send a notification to me, only if Interests = {BLANK}.

and


When a new entry is created send a notification to me, only if Interests NOT {BLANK}.

aren't triggering now, even when I make entries from another browser and not logged in as 'me'.

I'll see about getting you on an install with a similar form.

Steve