Communication Task- MIM work bench

[nitindub]

Hi Team,

Post washington upgrade, the communication task doesn't loads in workbench, can see these being created in backend though.

Can advise or suggestion why it is so.

Thanks

[Dr Atul G- LNG]

 Hi @nitindub 

Yes OOTB it is not showing now.

We can create manually if required.

[bindu214301]

Hi, 

  We are facing the same issue after upgrading from Washington to Xanadu. This is a high priority. Communication tasks are created at the backend but they doesn't show up at the front end in sow and mim workbench.

[Dr Atul G- LNG]

Did you try to repair the MIM plugin? 

https://www.servicenow.com/docs/bundle/vancouver-it-service-management/page/product/incident-managem...

https://www.servicenow.com/docs/bundle/vancouver-employee-service-management/page/product/sn-teams/t...

[bindu214301]

After upgrading to Xanadu, data in Communicate tab is not loading for major incidents in SOW.​

STEPS TO REPRODUCE/OBSERVE BEHAVIOR:

1. Workspaces Service Operations Workspace
2. Lists Major Incidents All
3. Open an major incident and click upon "Communicate" tab

Notice the error " Communication(s) data fetch failed"

MOST PROBABLE CAUSE:
We noticed that the Script Include "global.NotifyJSTelephonyConferenceAPI" seems to be corrupted

NotifyJSTelephonyConferenceAPI:

SOLUTION PROPOSED:
We have noticed that upon repairing the below plugins, the communicate tab now loads fine in the crocsdev instance
Notify (com.snc.notify)
Collaboration Services (sn_tcm_collab_hook)

Steps:
All System Definition plugins Search for (com.snc.notify and sn_tcm_collab_hook) Repair

sn_tcm_collab_hook

com.snc.notify

If you find my response helpful, please consider marking it as "Accept as Solution" and "Helpful." This not only supports the community but also benefits me. Thank you! 😊