Fix Bug with Alerts using Trigger condition "Not equal to" in the custom values.

thughes92

Hello.

I Recently opened up case # 543858 which was an issue with the advanced alerts configured properly not triggering true alerts based on a custom properties field having input.

for example.

In the alerts a field is set up like so -  field Comments is Not Equal to "Email"

When a Field is blank in the Database, Comments Field = NULL

i had only 3 nodes reporting on this alert because they happened to meet the rest of the criteria and had a Comment in the Comments custom property. therefore they did not  =  null and worked with the alert.

When field Comments is Not Equal to "Email" Was removed and email was catagorized in a different form i ended up with 50 active alerts that were not being picked up because of this bug.

I Believe if there is a custom field and a "Not Equal to" option they should work. please fix the bug.

My Tech Recommended i write my this feature request.

Thank you

Thughes92

mgaciarz

This very much seems like a bug and is still an issue 6+ years later *sigh*

Goal was to have a trigger condition be based on a node's custom property not equaling a specific value so I put that as a condition and that didn't work.  If I changed the condition to "is equal to", Show List displays all the nodes that match the criteria, but if I flip the condition to "is not equal to" (which sounds like the exact opposite), Show List displays no nodes, even though there are hundreds that meet that criteria.

I even tried to wrap the "is equal to" in a "NOT" block to see if I could get the desired results and that didn't work either...

I think Thughes92 is correct in that this is because the other nodes that are being ignored have that value set to NULL in the database.  While the current behavior may be technically correct from a SQL standpoint, it is definitely not the expected behavior for the SW administrator...

Is there a way to work around this currently?  Or any hope of this getting fixed?