Trigger a Notification relative to create time that goes to dynamic Groups and Assignees...

Robert_Cartwrig
Tera Expert

Hello Servicenow Community,

I'll keep this open ended:   I'm trying to figure out the best way to kick off an Email Notification to the Assigned To and Assignment Group of the task after a task has been open too long (notice I didn't say the SLA has been Breached).

Yes, we have defined SLAs and we have the default SLA workflow - but the Notifications in Workflow do not seem to provide this functionality as they are defined using a statically defined group and user.

An email Notification seems to require an Insertion or Update to kick off rather than just firing when the criteria are met, which doesn't work in this situation.

I have some ideas about how to do this (having to do with a scheduled job kicking off a registered event, which calls the Notification, or triggering the same from a workflow), but am frankly surprised that this functionality apparently isn't available OOB as a simple configuration and can't shake the feeling that I'm missing something.   It just seems overly complicated for what should be a simple OOB fiunctionality.

This has to be a common need and should warrant a straightforward solution (IMHO).   Who can provide one?   Ideally, this will be accomplished from an Email Notification (not the Workflow).

Thanks,

Robert

1 ACCEPTED SOLUTION

I agree and I have worked with several of these systems as well having been a customer for many years.   To ease the creation of scheduled jobs, ctomasi created a Scriptless Scheduled Jobs solution that automates the script creation for you based on condition builder.   This is certainly another option for you too:


Scriptless Scheduled Jobs


View solution in original post

9 REPLIES 9

Michael Ritchie
ServiceNow Employee
ServiceNow Employee

Inactivity monitors may help you.   They are a platform feature to make sure records are updated within a certain period of time:


Set an inactivity monitor


Hi Michael,



Neat idea, but it looks like any user update on the ticket resets the timer.   I'm looking for "Created + x."   Example:



  • Access Provisioning Request: 24 Actual hours from Creation if still Active (to be sent dynamically to the Assignment Group and Assignee, not static values)
  • Access Deprovisioning Request (Standard): 16 Business hours from Creation if still Active (to be sent dynamically to the Assignment Group and Assignee, not static values)
  • Access Deprovisioning Request (Sensitive): 1 Actual hour from Creation if still Active (to be sent dynamically to the Assignment Group and Assignee, not static values)


That being said, thank you for pointing out a method I didn't know existed.   Kinda the point of this.



Thank you,


Robert


As I consider your proposed solution, it occurs to me that I could use this, but have it Wait an hour and set one of the conditions to Created Relative x hours ago.



That might work. Every hour it would re-evaluate, so User action becomes less of a factor...



Any other bright ideas?



,


Robert


This should work.   Only other option is a scheduled job that runs periodically evaluating a script.