I have come across a couple of use cases where there is a need to send notifications from a workflow that is triggered to run on current and extended tables. This is something that works when testing the workflow in App Engine Studio using records created in the extended tables but not after Activation where you get an error:
It seems that unlike the other Core Actions the Send Notification Action only works with the parent table. The advice from ServiceNow is to create multiple notifications. This gets very messy in a single flow.
Notification not triggering based on conditions when applied to parent table - Support and Troublesh...
The workaround that I have deployed is to use the Lookup Record action to look up the record from the parent table and then use this record in the configuration of the Send Notification Action. After doing this I am able to use one notification for the parent table and all the child tables in my application. The strange thing is that when I check the runtime value for the Send Notification action it shows the child table record and not the parent.
I hope this is helpful to anyone else who has faced this issue. I would also hope it will be possible to update the product so that this is not necessary in the future.
Hi @EugeneS , I have tried the same logic but facing the same error.
The notification on the parent table is not sent to child tables.
Could you help me here.
