How to trigger notifications to Agent Workspace?

Anish Reghu
Kilo Sage
Kilo Sage

Hello all,

 

I could do my bit, but I am not able to find where I could post the Body of the notification.

 

Provider > Notification

 

I had referenced the event I created here and defined the Content on the related list, but not sure where to add the body. Do I need to create a Notification Flow Action?

 

Regards,

Anish

1 ACCEPTED SOLUTION

Anish Reghu
Kilo Sage
Kilo Sage
Provider > Notification > Create New > (Related list) > Content tab > New Provider Content (UI Action) > Next Experience (interceptor) > FEED THE BODY OF THE MESSAGE IN THE 'Message' box.

Trigger the event from Script Step in Flow (it works)!


Done!
 
The reason for this thread was - due to a silly mistake made, the gs.eventQueue() was not triggering the notification to the agent who is the assigned to on the case.
 
Instead of using the Workspace route, I chose Next Experience as advised by @Ankur in the previous thread. But still it was not working, when I happened to check that the scope of the step where I parse the JSON is written in Customer Service scope, but rest of the flow and the flow itself is in Global scope. That was causing the issue.
 
Regards,
Anish

The problem was that one of the flow inputs was defined in a scope while the flow was in global scope.
 
 

View solution in original post

5 REPLIES 5

Anish Reghu
Kilo Sage
Kilo Sage
Provider > Notification > Create New > (Related list) > Content tab > New Provider Content (UI Action) > Next Experience (interceptor) > FEED THE BODY OF THE MESSAGE IN THE 'Message' box.

Trigger the event from Script Step in Flow (it works)!


Done!
 
The reason for this thread was - due to a silly mistake made, the gs.eventQueue() was not triggering the notification to the agent who is the assigned to on the case.
 
Instead of using the Workspace route, I chose Next Experience as advised by @Ankur in the previous thread. But still it was not working, when I happened to check that the scope of the step where I parse the JSON is written in Customer Service scope, but rest of the flow and the flow itself is in Global scope. That was causing the issue.
 
Regards,
Anish

The problem was that one of the flow inputs was defined in a scope while the flow was in global scope.