- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2019 10:04 AM
Hi all,
I'm trying to setup a communication plan for our change request. The communication plan has 1 communication task definition and 1 communication contact definition.
The communication contact definition is set to the type of 'Recipient list' referencing a recipient list which is dynamic and when refreshed contains 7 users:
When I create a change request which meets my communication plan condition the communication plan is creating and it is creating the communication task and has added the recipient list to the plan:
However when I go to the communication task and select the 'send updates' related link, the email pop-up is not populating the 'To:' field with the users from the recipient list:
Am I missing some additional configuration, or is my understanding of how this should work not the case?
If on the communication plan I add a user in the related list this does get added to the 'To' field as I would expect?
Thanks
Sam
Solved! Go to Solution.
- Labels:
-
Best Practices
-
Notifications
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2019 06:16 AM
I managed to hunt down the issue. I had a look in the UI action 'send updates' on the communication task and this calls the script include 'CommunicationManagementUtilSNC'. Within this there is the function '_getContactsForEmail'. I noticed in here that it was only adding the users from the recipient list to the 'to' field if the recipient_list.type was 'internal'. I had set my recipient list type as external.
I've amended the extended script include for this function so it does the same for recipient list type of external and its now working as I was expecting.
I'm not sure that recipient lists are only for use for targeted communication as the communication plan has the option to create a communication contact definition with the type as 'recipient list' so from what I can tell this is OOB functionality.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2019 02:51 PM
You might be confusing the intent behind Recipient List. It's more intended use is Targeted Communications in the Customer Service space.
You may want to entertain leveraging the Watch list instead.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2019 06:16 AM
I managed to hunt down the issue. I had a look in the UI action 'send updates' on the communication task and this calls the script include 'CommunicationManagementUtilSNC'. Within this there is the function '_getContactsForEmail'. I noticed in here that it was only adding the users from the recipient list to the 'to' field if the recipient_list.type was 'internal'. I had set my recipient list type as external.
I've amended the extended script include for this function so it does the same for recipient list type of external and its now working as I was expecting.
I'm not sure that recipient lists are only for use for targeted communication as the communication plan has the option to create a communication contact definition with the type as 'recipient list' so from what I can tell this is OOB functionality.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2019 06:51 AM
Great find!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2022 05:32 PM
I just recently troubleshooted this same issue for a client. Since this is the only thread I found when researching this issue, I just wanted to add that if you create your own email template for the publication, make sure you add the following mail scripts to the Message HTML field on the template:
${mail_script:publication_attach_links}
${mail_script:publication_content}
${mail_script:add_users_to_bcc_list}
These are on the OOB publication email template and was the reason none of the users on the recipients list were being added to the BCC field, as well as why the publication content and attachments were not showing up when they tried to use their own custom template.