How to prevent all Problem internal notes from updating related cases and incidents
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5 hours ago
Hi Everyone,
Currently, we have an Internal Notes field on the Problem record.
Whenever a comment is added to this field, it is automatically posted to all related records (Incidents / Cases) via a custom Business Rule.
There is now a requirement not to post every internal note to the related records. Instead, users should be able to selectively choose which comments get propagated.
One approach we are considering is:
Add a Boolean (true/false) field on the Problem table
Display it on the form
Update the Business Rule so that comments are only synced to related records when this field is true
Before proceeding with customization, I wanted to check:
Is there any out-of-the-box functionality or recommended ServiceNow pattern to control or selectively propagate internal notes to related records?
Any guidance or best practices would be appreciated.
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5 hours ago
Hello @RohitD027682673
If my response helped mark as helpful and accept the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5 hours ago
Thanks, @kalanidhikr , for the clarification.
Since customization is required, what would be the recommended approach / best practice for this use case?
Would it be better to:
Add a separate Journal field (for example, “Problem Internal Notes – Not for Propagation”) to capture notes that should not be pushed to related Cases/Incidents
ORAdd a Boolean field (e.g. “Propagate to related records”) and modify the existing Business Rule so that internal notes are synced only when this flag is set
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5 hours ago
The journal will be larger. A good reason for this is that you could use this field—if you create it on the Task table, you could also use it in other related tables. However, this will increase double effort and add technical debt. From a process perspective, it’s better to keep what you have, as adding technical debt now could be harmful in the future. Still, if help is needed, the first option can be considered.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/dratulgrover [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5 hours ago
Hi @RohitD027682673 ,
one alternative approach I can think of is to create a UI Action and move the logic of the BR to UI action
when it's clicked post the notes and users can choose when to click.
the boolean needs to be checked by the users manually anyway why not an UI action instead.
Please mark my answer as helpful/correct if it resolves your query.
Regards,
Chaitanya
