Thanks for replying. I guess what I've missed and want to know is:
The 'knta_notification_recipients' table holds the 'DISTRIBUTION_TYPE_CODE', which is either 'TO' or 'CC'. When I run my function to update the email tables the PPM SMTP service sends separate emails with the same content to both TO and CC individually, normally the TO and CC are on the same email. Now I have users complaining that they can't see who got the email.
Attached is my function. I really need to understand the link between the tables which places the same contents and subject to both TO and CC recipients? I run the function as follows:
Just to inform you that I have found the solution to the separate TO and CC issue. I broke up the function that populates the notification tables, this function was designed to send ‘TO’ emails only. This lead to a number of complaints about the TO and CC lists getting separate emails (same content), so the TO could not see from the email who was on the CC list and vice versa.
Due to other work it’s taken me a while to figure this one out. So I broke the function down so the TO list populates the main tables and the CC list gets added to the main ‘knta_notif_txn_recipients’ table under the same ‘NOTIF_TXN_DETAIL_ID’ with CC as ‘DISTRIBUTION_TYPE_CODE’, hence now for each PPM object I target for email sending all roles are sent on the same email under TO and CC accordingly, and within RFC email standards.