Emails
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-09-2023 09:13 AM
why we use event is fired over record is inserted or updated in email notification"
what is the importance of event is fired
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-09-2023 09:18 AM
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
‎11-09-2023 09:19 AM
Events let you trigger the notification from any server side script.
Even events that don't use an event still technically do they just use one that evaluates the insert/update condition. However that isn't as easy to call from a server side script. You can just insert the event.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-09-2023 09:21 AM - edited ‎11-09-2023 09:27 AM
There are times in a workflow or automated process that you may want to force a notification, when there isn't any CRUD (create/read/update/delete) operations performed on a record -- events are useful in this instance. This is the primary use of events, in triggering an email notification. For instance, if you want a reminder of something to go to someone at some point in a workflow step -- I suppose technically that would be an "update" (CRUD) to a workflow context record, where you could base the email notification on that table and build rules around what to watch for in the update to that record...but seems like sending an event in that instance would be less of a headache and easier to maintain.
You may also want the recipient of an email (notification or otherwise) to be someone in specific, but dynamically set/determined by a variable or other lookup table/list/function. You can pass the recipient details to the notification record via event parameters, and usually when you are generating/firing an event, it is from a scripted location, so you can incorporate code that will retrieve or otherwise gather that information, to ultimately be the recipient of that notification. This functionality would also be available in a mailscript, but events work nicely here too.
Also -- be careful when searching for information about "Events" in the context of the Now Platform, "Event Management" is a specific process that is separate from "managing events" -- one is an ITSM process related to incoming emails and/or other methods of discovery, which then trigger actions like creating records and other associated processes, etc...and the other is an object (record) in the db (platform) which facilitates various functions specific to the platform.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-09-2023 09:21 AM
Hello @RaviSankar54 ,
Event is fired means when you generate event via server side objects ( e.g business rule, script includes).
Triggered means when it's triggered by action in flow designer.
Please refer: https://docs.servicenow.com/bundle/vancouver-platform-administration/page/administer/notification/ta...
@RaviSankar54 , Please mark my answer as "Accept as Solution" and "Helpfuls." If it works for you.
Thank You!
