Do Notifications on Task table fire on extended tables?

[The SN Nerd]

I've noticed that when I set 'Table' to 'Task' on any given notification, it is never fired when triggering from a table that

Even the OOB notification "Task approved" is not firing (tested on an Incident record, OOB).

As soon as I change the notification to use the Incident table, sending to the Assigned to field, it works.

Yes, the user has an email record, the user is not me, and send to even creator is checked. It works if the table is set to Incident.

This seems inconsistent with the way the rest of the tool works. Also, why do they provided OOB notifications if they don't even fire?

I've testing on an OOB Fuji system and a customized Eureka system. The issue occurs in both systems.

Aren't Notifications on Task table supposed fire on extended tables? Why not?

[The SN Nerd]

From the ServiceNow dev team:

The notification code is set up to run off of the specific table inserted or updated. If you want to have notifications trigger from the business rules being run, you can create an event in the business rules and trigger the notification off of the event."



So this is an expected behavior for outbound notification by design.

We can configure "Send when" to "Event is fired", but then you try to save the change, you will see the following message:

"changes operator in notification condition cannot be used with event based notifications

invalid update

A documentation request has been made to update the wiki with this information.

I have created a document enhancement request <DOC13919> to document this behavior under this wiki page [http://wiki.servicenow.com/index.php?title=Email_Notifications].

As part of the base build, a condition based task notification is provided. In light of this task issue, the notification does not work. Because of this, I believe it should be treated as a bug, but this has not been acknowledged.

It looks like it is not going to be fixed, although there is a workaround to use events instead of conditions.

[Mike McCall]

Thanks, Paul! I ultimately gave in and went with the event approach, though it would be great to use the condition-based approach for tables that are extended.

One thing I've noticed is that you can successfully include conditions in addition to the selected event (as long as you don't use the "[field] Changes" condition).

[The SN Nerd · Accepted solution]

Notifications with 'Changes', 'Changes to' and 'Changes from' will not be triggered if the conditions are met on any extending tables.

This is by design.

Workaround

Use Events instead of conditions.

[peterraeves]

I created a notification without any condition and that does not even work... Which is very strange, because there is an OOTB notification on the task table, so you would assume that to work right?

[The SN Nerd]

That's what I thought!

But support confirmed that is not the case.