FIND Query in LoginNotification Rule

syndeo

3508 | Derby | Windows 11

What I did…

The the LoginNotifcation rules I set to find a particular record in a BO. If that record didn’t exist (or if SEARCH_COUNT was equal to zero), then create another BO.

What I expected to happen

System would find an object and if found to not proceed.
I expected SEARCH_COUNT to = 1

What happened

SEARCH_COUNT = 0. This is not correct. I’ve a saved a screen shot of the log.

aware_support3

Can you share the rules in the LoginNotification please.

syndeo

FIND IPRange WHERE IPRange.IP = LoginNotification.RemoteAddress
IF SEARCH_COUNT = 0 THEN
CREATE AccessLog WITH AccessLog.DevicePlatform=LoginNotification.DevicePlatform,AccessLog.ReferringURL=LoginNotification.ReferringURL,AccessLog.RemoteAddress=LoginNotification.RemoteAddress,AccessLog.SessionId=LoginNotification.SessionId,AccessLog.UserName=LoginNotification.LoginName,AccessLog.isGuest=LoginNotification.IsGuest,AccessLog.isNativeMobile=LoginNotification.IsNativeMobile,AccessLog.Timestamp=CURRENT_TIMESTAMP

Can I ask why the rules would make a difference? My question relates to why the system proceeded if it found 1 object? Why did it evaluate the IF statement to true?

I’ve since change the rule to the below and it works.
IF NOT ( EXISTS IPRange WHERE (IPRange.IP=LoginNotification.RemoteAddress)) THEN CREATE...

aware_support3

syndeo Can I ask why the rules would make a difference? My question relates to why the system proceeded if it found 1 object? Why did it evaluate the IF statement to true?

For the fuller picture.

Not sure why that would be happening with the rules you’ve provided. To investigate we’d need a BSV with instructions as to how to replicate the issue.

It may be a Derby issue

syndeo

aware_support3

iprange.bsv

50kB

View the AccessLog BO and you will see that is is still recording a record in the AccessLog BO when it shouldn’t.

aware_support3

syndeo

Thanks we’ll have a look into this.

aware_support3

syndeo View the AccessLog BO and you will see that is is still recording a record in the AccessLog BO when it shouldn’t.

Thanks.

Notification rules act like a special type of Business Object and as such the rules associated with them act in a similar fashion to Business Object Rules, ie they execute in no particular order. Unlike Business Objects Notification Objects cannot be passed to a Process.

To make your rules operate in a specific order you can push them into a Process, but as you cannot use a Notification as an input to a Process, you have to collect all of the relevant attributes and put them into a Non Persisted Business Object and pass that to the Process.