Just a heads up that I'd like to verify others are seeing. In some of my alert logic definitions I have something like the following:
Trigger Condition:
Alert on all objects where:
All child conditions must be satisfied (AND)
Transaction Custom Properties - AlertTransactionCustom - is equal to - 0
Transaction Custom Properties - CustomerName - is not equal to - <customername>
But we realized today that alerts weren't triggering for almost any transactions and I discovered that because I have that CustomerName property condition in there, if any transactions didn't have that property set, it was excluding those as well. I had to change the logic to the following to get them included again (the original alert logic above has been in place for years).
Trigger Condition:
Alert on all objects where:
All child conditions must be satisfied (AND)
Transaction Custom Properties - AlertTransactionCustom - is equal to - 0
At least one child condition must be satisfied (OR)
Transaction Custom Properties - CustomerName - is not equal to - <customername>
Transaction Custom Properties - CustomerName - is empty
I'm now scouring through my hundreds of other alert definitions to see if this is an issue across the board. Anyone else notice this? Or was this change documented somewhere that I missed?