Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Trigger an Email when multiple incidents are created within a short period of time.

Tfnhodgi
Tera Contributor

Trigger an Email when multiple incidents are created within a short period of time.

Example multiple incidents created within 30 mins with the keyword in the short description "network"

I am guessing there are multiple ways to handle it just trying to see what people think is best.

12 REPLIES 12

Hi @Tfnhodgi 

 

If you clear requirements only then we can help you.  What do you want to achieve exactly? 

 

If I say from my experience, SN can do alot and alot, but that is only possible, if have a clear set of requirement or ask.

*************************************************************************************************************
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]

****************************************************************************************************************

My requirement. 5 incidents created with the same keyword explaining the incident in the short description. within the last 30 mins to email a group of people. This is because the defined triggers for a major incident do not work for how our business runs. We would want this as our first step to define a major incident. We use the major incident plugin, but we want this to help automate a major incident since our help desk does not notice multiple calls unless they are the one who received multiple calls.

Hi @Tfnhodgi 

 

Thanks for more details now. 

1. By just on the basis of keywords in last 30 mins, doesn't mean it is a Major incident.

2. First, we need to define the process of MI and definition of MI , steps to detect the MI, criteria  which say , Yes it is MI.

3. SN will powerful here, this detection is not possible standalone which means, it is collaboration of AI + PI +ML all together.

4. We can use these techs which are help us to get a pattern and then with that pattern you can log an incident as MI. 

 

 

 

*************************************************************************************************************
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]

****************************************************************************************************************

This is just our own first step in identifying the MI nothing more nothing less. Triggers an email for a few people to take a closer look at the tickets. But from the sounds of it you are saying what I am trying to do is not possible. I assumed we could write a business rule or email trigger or something. 

Thanks for your time.

That's good.

 

Please accept the answers as a solution and close the thread.

 

*************************************************************************************************************
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]

****************************************************************************************************************