SNC.LiveFeedApi().addMessage(message, id) not working for non-admin users - Known Error

SNC.LiveFeedApi().addMessage(message, id) not working for non-admin users Description In Madrid instance, the message inserted into connect support conversation while clicking on a connect action using SNC.LiveFeedApi().addMessage() API works for admin users but not for non-admin users.

Below table explains the difference between different methods:

Steps to Reproduce

Hop to any OOB Madrid instance Navigate to connect actions and open any action say "create incident" In the script field add below addMessage API call: var id = conversation.document.group; new SNC.LiveFeedApi().addMessage('Test Connect message 123', id); Save In an incognito window impersonate to end-user and navigate to a (or any queue)Connect Support queue. https://INSTANCE_NAME.service-now.com/nav_to.do?uri=chat_queue.do?sys_id=4bc7a3f3c31331001c845cb981d3ae44 In another incognito window impersonate a group member (having admin role )of the assignment group of that support queue (For example David Loo) As end-user type an initial message and click 'send' to initiate a new support conversation. As admin user accept the chat and click on the "create incident" connect action. Observe that both end-user and admin would get the message "Test Connect message 123" Now remove the admin role from the agent"David Loo" and test out the same steps from step 7 Observe now the message doesn't get displayed for both end-user and agent.

Actual behavior: The message inserted using SNC.LiveFeedApi().addMessage(message, id) doesn't work for non admin users Expected behavior: The message inserted using SNC.LiveFeedApi().addMessage(message, id) should work for non admin users Workaround This is working as expected.

As part of the design, the live feed API allows the insertion of a message only if the user passes the ACL checks.

To turn off this feature create/set the system property "glide.live_feed.acl_check_enabled" value to false.