Creating a Separate Email Notification for a Specific Catalog Item
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2024 09:33 AM
Hi everyone,
I'm looking to create a separate email notification for a specific catalog item. Currently, we have a single notification for all catalog services.
However, I need to customise the email notification text for one particular catalog item upon closing the RITM.
Could anyone provide the steps to achieve this customisation?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2024 09:34 PM
Hi @BobbyM
you can achieve this by make the condition the new RITM close notification where you need to trigger only for this and OOO notification should not trigger for this item's RITM
for custom one add condition in when to send
for OOO need to update the Condition like below
If my response proves useful, please indicate its helpfulness by selecting "Accept as Solution" and " Helpful."
Thanks,
BK

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2024 09:55 PM
Although this a good solution, it's not highly scalable as it'll require the modification of the base record for every override, e.g you'll end up with a lot of "item .is not. XXX" conditions.
Instead, leverage the 'weight' field to determine which notification takes precedence. KB0829694. For this explanation, I'll refer to the generic existing notification as 'base' notification.
- Notifications with a weight of 0 will always send so the base notification will need to be set to a weight of 1 in order to be considered.
- Create your new notification with an appropriate trigger condition to fire for this item, include the condition 'item is xxx' to ensure it only fires for that item.
- The recipients of this email need to be the same as the base notification
- Set the priority to higher than the base notification.
Both notifications will trigger and appear in the sys_email table, but the base notification will be set to send-ignore. This is handled by the 'ignore duplicates' business rule.