How to stop triggering notification twice when people are same which are from two different tables??

[Manikantahere]

I have a business scenario where i am transfering comments from ritm to sc task and sc task to ritm and need to send notifications to requested for and to the watch list when ritm/sc task comments are updated.

but the problem here it is when it comes to requested for and watch list there is a chances that people may different in watchlist and requested for is same in both levels.

when I commented on ritm as it also updating comments in sc task so two notifications are triggering to requested for saying comments updated.  I need to stop this happening as he is same  for both levels.

even if watchlist is same then it has to send one notification and if it differs has to send two notifications.

need guidance to achieve this??

[Manikantahere]

is there any other way by keeping both level notifications i.e on sc table and ritm ??

[Mark Manders]

You can keep them on both levels, which means they both get triggered for the same change and both get send, causing some of the recipients to receive the notification twice.

You could add a 'Copied from task' line to the copying of the comments, use my solution to trigger one notification to people on both tasks and if necessary, create another one on the RITM, but only if the comment does not contain 'copied from task'.

If you use notifications from 2 tables to send out the same information, you run the risk of people receiving it twice. You can't go around that, because you can't validate if someone already got that information from another task.