Reminder notification
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2025 01:05 AM
Given a Policy exception is 90, 60, 30, 15 days before valid to date, then every day for 7 days before the valid to date a notification should be sent based on the details captured in the attached notification spreadsheet.
User Story | Domain | Notification Name | Trigger | Recipient(s) | Subject | Content | Comment | Updated Language (if needed) | Deactivate? |
Policy Exception | Policy exception valid to reminder | Policy exception is 90, 60, 30, 15 days before valid to date, then every day for 7 days before the valid to date | Requester cc: Watchlist, Exception Manager, Division Cybersecurity Lead, securityriskexception@abbott.com | Exception Expiration: Policy Exception [Policy Exception Number] will expire and close on [Valid To] | Dear [Requester], This is a reminder that the policy exception titled "[Policy Exception Name]" is set to expire in [number of days] days, on [Valid To]. Upon expiration, the exception will automatically close. Details: Exception Number: [Number] Policy Exception Type: [Type] Policy Exception Name: [Name] Policy Exception Reason: [Reason] Policy Exception Justification: [Justification] Valid from: [Valid from] Valid to: [Valid to] Requested By: [Requester] Click here to view the GRC tasks page: [Link to GRC tasks page] Click here to view the exception record: [Direct link to Exception] If the policy exception is needed beyond [Valid To], please submit an extension request as soon as possible. Failure to do so will result in automatic closure, and for user-based exceptions, access will be revoked. Next Steps: If the exception is no longer needed: No action is required, the exception will auto close on the expiration date. If the exception is still needed: 1. Navigate to the policy exception record in ServiceNow. 2. Click "Request Extension". 3. Enter the new expiration date, reason for extension, and justification. 4. Submit the request for review Thank you for your prompt attention to this important matter. | Notification needs to go out to the Exception requester and CC Watchlist, Exception Manager, Division Cybersecurity Lead, securityriskexception@abbott.com for 90, 60, 30, 15 days before valid to date, then every day for 7 days before the valid to date |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2025 01:10 AM
Thanks for sharing the entire story with the community. This is actually quite simple to implement. You can explore the out-of-the-box (OOTB) bifurcation options, or use the Flow Designer, which is a low-code tool. I'm sharing a link that shows how this can be done. Break this requirement into smaller pieces (epics), and then build the notification using Flow Designer.
https://www.servicenow.com/community/developer-forum/send-reminder-emails-through-flow/td-p/2752851
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
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/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2025 01:52 AM
Olá @Nikhitha Gandhi,
this can be achieved either by a Flow or a Scheduled job.
In the Flow, you set the trigger conditions and then you apply the thresholds (90, 60, 30, 15 days and then every 7 days until it is handled).
In the scheduled job, you will be checking all the records daily and if there are any records matching the conditions, there will be an event and the notifications will be triggered based on the event.
Example : event.90.days, event.60.days, etc. so you will also have overview in the event logs to track this.
Let me know what do you prefer and where do you feel more comfortable or what is preferred option in your instance (you should stick to the solutions that already exist and do it similarly to simplify the maintenance).
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */