Is script action required to trigger notifications asynchronously?

[akshay parekar1]

So, i had requirement where i wanted to trigger notifications on click of ui action and that should be asynchronous call.

In brief, we had task table and for each task there will be multiple assessments assigned to different users stored in assessment instance table. There was a ui action on task and on click of that we just wanted to send notifications to assignees.

    for that, i just fired event from ui action script only which triggered notifications to be sent.

I thought its an asynchronous call only as notifications will be sent parallelly  to respective assignnes on click of button.

 But i was  asked to fire event from script action only so that it will be an asynchronous call.

I just wondered whether script action was required here or not. 

Let me know something that will resolve my doubt, thanks!!

[Peter Bodelier]

The way you were doing it, is already asynchronous. If you start doing it through script actions, it will be asynchronous times 2.

[Manmohan K · Accepted solution]

Hi @akshay parekar1 

Two points here 

1. A script action in servicenow is triggered by an event. So it involves firing an event first, which then triggers the script action. Subsequently, another event needs to be fired from the script action to trigger the actual notification. This approach creates a roundabout process that consumes system resources unnecessarily.

2. Both methods of triggering notifications in ServiceNow rely on events and events are handled in an asynchronous manner in servicenow. Events are placed in a queue for processing, allowing the system to handle multiple events concurrently without blocking other tasks. This asynchronous nature enhances system scalability and efficiency.

So there is not need to configure script action in the existing solution design