- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2023 07:54 AM
Hi everyone,
I have no idea what the issue here might be, but we started setting up provider notifications (to get rid of mails for our agents) and all of them are working fine when they'll be send to one user (e.g. mentioned by, additional comment/work note added to record etc).
What we now want to have is the simple notification when a new record arrives in one of their groups but is unattended. I used the exact same parameter as for our email notification, and added "Recipients listed in field" > Assignment Group.
Content Class is set to Next Experience.
However, no notification is to be shown by the bell. The trigger is somehow successfully working it seems, as far as I can see in the log.
We're getting the following in the logs for the execution:
For Synchronous Providers: Loaded 1 recipients and 0 destinations and delivered to 0 destinations in 4ms
For Synchronous Providers: 'INC: Assigned to group' do not have any associated Common Content or Provider Content or Default Content for the Provider 'Workspace', this provider will not be initialized.
For Asynchronous Providers: Loaded 1 recipients and 0 destinations and delivered to 0 destinations in 4ms
Can someone help me out?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-31-2023 05:49 AM - edited 10-16-2025 12:15 AM
Update: Zurich
Thanks to @mukesh_adh for pointing out that this appears to have been sorted in Zurich. Now you can just set the provider notification up the way you would expect by picking a group reference field.
As you can see above the notification is set to target recipients listed in fields, and the field selected is a group reference field (assignment group)
Result:
You've also got the option of picking groups via a related list at the bottom, though obviously this is static.
Old pre-zurich solution:
(function executeRule(current, previous /*null when async*/ ) {
gs.eventQueue('testEvent', current, getGroupMembers(current.assignment_group), current.number);
})(current, previous);
function getGroupMembers(groupID) {
var groupArr = [];
var groupMemberGR = new GlideRecord('sys_user_grmember');
groupMemberGR.addQuery('group', groupID);
groupMemberGR.query();
while (groupMemberGR.next()) {
groupArr.push(groupMemberGR.user.sys_id.toString());
}
var stringArray = groupArr.join();
return stringArray;
}
Have a go with the above, this is the business rule script (just replace the eventname "testEvent" with your own). The condition I set was just when assignment group changes.
The event log looks like this when triggered:
(note all the user sys_ids, comma separated in parm1).
Looking at the logs above it looks to be working
Let me know if any luck/still issues. This is for the notification bell notifications right? (workspace experience > administration > notification triggers)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
I have a question regarding the delivery verification of provider notifications in Microsoft Teams. In the provider notification logs, I can see that the notification was triggered and that a certain number of recipients were selected. However, the issue is that the notification does not appear in the MS Teams instance.
I am trying to identify a way to debug such cases, as there are no errors logged and no additional notification logs attached to the event or the provider notification itself to confirm successful delivery to MS Teams.
Is there any method to validate whether the message was delivered successfully? Please let me know if you require any additional details.
