
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-01-2015 07:42 PM
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?
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-14-2015 12:59 AM
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.
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-01-2015 07:59 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-01-2015 08:03 PM
UPDATE: The notification fires if triggered by an event.
If triggered by conditions it does not.
Have raised this with ServiceNow. Was wondering if anyone else is having this issue.
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2015 01:39 AM
Even if the event also fires with same condition.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-12-2015 09:26 AM
I'm currently in the process of building a custom table to extend going forward (sort of a "lite" version of the Task table), so I ran into this odd behavior pretty quickly. I'd love to hear anything more you find out!