How to Hide OOB "Discuss" and "Follow" UI Actions in Omni-Experience Standard Feature SetI'm trying

[Marvin Antonio]

I'm trying to hide the out-of-box Discuss and Follow UI actions in the Omni-Experience Standard Feature Set.

I’ve already checked:

• UX Form Action Layouts – couldn’t find any option to disable them.
• System Definition > Dictionary – no relevant entries found.
• UI Actions – these buttons don’t appear here, likely because they’re OOB and not exposed for direct modification.

Has anyone successfully hidden or disabled these actions? Any guidance or workaround would be appreciated.

since is OOB.

[mattmm]

 @Marvin Antonio - I tested this in a Developer instance with the CSM Workspace as an example- 

• Go into the Action Layout Item that relates to the buttons you want to deactivate.......Do not deactivate Global buttons unless you are happy for this to disappear from everywhere.....
• so in filter navigator go  to sys_ux_m2m_action_layout_item.list ,
• Show Matching on the UX Form Action Layout Item "Discuss" , then look for the ones that relate to the Table you are wanting to hide this on (example CASE[sn_cusomterservice_case] and
• change Active to false.
• You can do similarly to with Follow on the same above table.

[Ankur Bawiskar]

@Marvin Antonio  

please share screenshots

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Marvin Antonio]

Hi, your instructions did not help, but I got a recommendation from ServiceNow support team and that

Most Probable Cause:
Sidebar was enabled in global settings.
Link to global settings: sys_cs_collab_settings.list and change application scope to "Omni-Experience Standard Feature Set

find column "Enabled" and change value to "false"
reload the page to confirm that settings changed.
check up your records.

This proposed solution worked for Discuss UI action Globally.

[mattmm]

Good to see this work Marvin, just noting for anyone else that may read my solution, it applied specifically to my testing of CSM workspace, and it's Interactions alone and not globally.