Parent-Child Notification Inheritance (Case/Case Types)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello Community,
I am working with Case Management (CSM) and have several custom Case Types (child tables, e.g., sn_customerservice_case_mytask).
I have configured several OOTB and custom email notifications directly on the parent Case table (sn_customerservice_case).
My question is:
If an email notification is defined on the parent Case table, should it automatically trigger for all child Case Type records when those child records meet the notification's condition?
Currently, my child Case Type records are NOT triggering notifications that are set up on the parent sn_customerservice_case table. The emails are being skipped, and I don't see any explicit customization on the child tables to block parent notifications.
Is it required to redefine every notification (or duplicate the email events) specifically on the child Case Type tables for them to work?
Any insights or best practices on how notifications should work with Case/Case Type inheritance would be greatly appreciated!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
18 hours ago
Notifications that are defined with trigger as 'Record is updated or inserted' will fire only on the defined table and do not automatically apply to child tables.
Notifications that are triggered with either 'Triggered' or 'Event is fired' can be extended to child tables, as their trigger logic is outside the notification setup and would depend on the logic,
for instance you may trigger a notification from a Flow, however flows have a setting to be triggered on base table and/or its extended table, then in that case the notification, by association will also fire on extended table
