Hi
I just searched a lot in the scripts and BR of the Targeted Communication and found out the following for the Event you are referring to (Event = "sn_publications.addBCC").
This Event is fired in one Script Include called "RecipientsListApi" in the function "_getNewRecepients()" (which is called internally, when the public Function "refreshRecipients()")
The public function "refreshRecipients()" in turn, is called from (e.g.) the Scheduled Job called "Targeted Communications Recipients Refresh" (running daily at midnight).
However: This function fires the Event just in case, you added NEW Recipients to the Recipient List AND the "EMail Account" configuration record for your "SMTP" Account is having either a "FROM" value, OR a "User Name" value. If that is EMPTY, the "addBCC" Event will not be fired.
For Reference, see screenshots below:
a) The SMTP EMail Account config
b) here comes the code snippet reading the SMTP Account (Script Include "RecipientsListApi"):
c) Here is the CODE Snippet to fire the event (Script Include "RecipientsListApi")
So, finally, can you check your SMTP Account Config?
For me, the Event was fired, when I manually executed the Scheduled Job (see screenshot below):
Reviewing the EMail Log, I was able to see the new Notification created...
In the "Bcc" List (in the Header of the EMail), I was able to find exactly the two NEW added Users to the Recipient List.
As a result. "Refreshing" a Recipient List (not inside of a Publication, but JUST the configuration of the List itself), will fire the "missing" emails to the new recipients - for all affected Publications in one shot. That is quite cool!
BTW: How many answers do you expect me to send to you until you at least click once on "helpful" (which gives me extra points in the community and keep me motivated here)?
Thanks for answering
BR
Dirk
