- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-14-2024 04:41 AM
Why does a new Publication notification get inserted to notification table each time a test publication is created and an email notification is sent. This is captured in update set. What business rule is responsible for this and how can it be switched off?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2024 11:26 AM
Yes, if thats how platform update sets behave, then it is an expected behavior. Targeted communications is an application built on top of core platform. All metadata is captured is update sets. If this update set contains notifications for test publications, which you dont want to move across instance, you can ignore the update set entry based on your use case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2024 10:33 AM
This is per design, Notification record is created per publication. On the publication publish date, publication notification will be sent to users in recipient list, we are shipping a Publication notification template.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-15-2024 10:04 PM
Hi @Goodness Ngodig,
Every publication is associated to a notification. The target audience is defined in the recipient list. So each time a publication is created and recipient list is associated, email is sent on the publication published date to the recipient list users.
Please review this - https://docs.servicenow.com/bundle/washingtondc-customer-service-management/page/product/customer-se...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2024 03:36 AM
In my case it inserts a new publication notification record on the notification table and this publication notification is captured in my update set when I'm testing. Is this an expected behaviour?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2024 11:26 AM
Yes, if thats how platform update sets behave, then it is an expected behavior. Targeted communications is an application built on top of core platform. All metadata is captured is update sets. If this update set contains notifications for test publications, which you dont want to move across instance, you can ignore the update set entry based on your use case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-19-2024 02:32 AM
Thank you so much for taking your time to reply to my query. I do have one doubt, if it is an expected behaviour for a publication record to create a new Publication notification each time a new record is created, why then do we have a default publication notification called "Targeted Communications Publication Notification"?