Email notification not being sent when "Send When" condition is set to "Record inserted or updated"

[sschleicher]

When setting up a new email notification, it would seem that I can configure an email based on two base conditions based on the options listed in the "Send When" drop down:

1) When an Event is fired
2) When a Record is inserted or updated.

While I know I could try the Event route, I would like to get the second option working based on a record that is already being logged into the syslog table.

Here are the steps I have taken.

1) Created an email notification that should send when a record is inserted into the Log Entry (syslog) table with a keyword in the message.

2) Validated that a business rule is creating a log entry with the keyword specified in the email notification condition by viewing the script log.

3) Validated that the email is not being sent by viewing the email log.

Shouldn't this be all that is needed to configure this type of email notification? I have not selected an email template (do I need one). The email populates the subject and simply contains the message value of the record inserted into the script log. Email notification is active.

[mduluk]

Two things,

1. do you have the inserted and updated boxes on the right checked? I know I have selected the 'Send when' and forgot to check the two boxes and it caused the message not to send.

2. On the 'Who will receive' tab, did you go into the advanced view and check the 'send to event creator' box. It might see that you are creating the event and not send you an email.

[sschleicher]

Yes I do have both checked (even though I only need the insert checked). I got really excited after seeing your second point because that would make total sense. After checking it though, it didn't log any email notification. Thanks for the options to try though.

[CapaJC · Accepted solution]

Okay, I did a quick test, and I think the issue is that gs.log("message") doesn't run GlideRecord's workflow or scripts/engines. This is probably a very good thing - imagine if someone wrote a business rule on syslog that wrote something to the syslog table? (shudder)

So Notifications don't get a chance to react to inserts/updates to the syslog table.

[sschleicher]

Perfect. Glad we at least understand there are exceptions to what tables can be used (makes sense). I'll just go with creating an event and basing the notification off of that.

[hpesata]

Hi!

I am also facing the task to be able to receive en email notification whenever an error record is inserted into syslog table.

were You able to manage this with the event approach ?

in all articles I read about this so far, it is strongly recommended NOT to use a business rule on the syslog table.

but this would be neccessary to trigger the event for the email-notification.

thanx for any information!

regards,

Hans