Loading...
Loading...
Workspace agent notifications do not work for the Assignment Group field. Steps to Reproduce 1. Create two notifications in 'sys_notification' table for case table: Name - Case has been assigned to your group Table - sn_customerservice_case Inserted - checked Updated - checked Users in field - Assignment group Acive - true Name - Case has ben assigned to you Table - sn_customerservice_case Inserted - checked Updated - checked Users in field - Assigned to Acive - true 2. Create Notification content for both of these notification and choose Agent Workspace. 3. Open a case assigned to 'Hardware' group and impersonated with group member from Hardware group in one browser. 4. In another browser logged in with Database group member in Agent workspace. 5. As a Hardware group member change assignment group to Database. The Notification execution history always gets incremented with the change on case record. 6. Notice on the other browser, no notification appears from bell icon in Agent workspace for Databse group member. 7. Again, As a Hardware group member change assignee in same case and set it to that database group member who is logged on in Agent Workspace. 8. Notice on the other browser, one notification appears from bell icon in Agent workspace for Databse group member.
This is expected behaviour in the current design. Workspace notifications are intended to be sent to an individual agent or to a maximum of five users. They are not designed to notify a broad distribution list or a group.
PRB1418097
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.