Ability to Auto-Record/Transcript Major Incident Teams Conference Calls and Retrieve Logs?

[Ian72]

I am working on configuring and integrating the Notify connector for MS Teams, and use it's functionality to power the Collaborate tab with teams conferences.

What I am interested in, is having the conference be recorded and transcribed, as well as sync'ing the OnlineMeeting chat logs back to the major incident like you can with 1 on 1 agent / user chats.

Thus far, I have found that the teams graph API does have an option when creating the OnlineMeeting to set auto-recording, but the script includes used by ServiceNow are read only and I cant simply add that key/value pair.  I do not see a way within the UI to enable this option.

Related to the above, I have not been able to locate any reference in the graph API to pulling the meeting logs.  You can pull conversation logs easily enough, but nothing related to the online meetings.

Has anyone had success performing the requirements above?  

[tijohnson]

I was able to successfully accomplish my goal.

Here is what I had to do:

• I created a REST Message called GraphAPI_GetChatMessages
• This uses the OAuth profile that was created called Microsoft Teams for Notify Self-configured app (you can name your bot whatever you want)
• This has an endpoint of https://teams.microsoft.com/l/chats/${chat_id}/messages
• In turn this has the HTTP method of GET named "default"
• I created a new Business Rule called (mycompanyname)-import MS Teams Meeting conversation
• This will run on the Notify Recording [notify_recording] table (this is the key table that stores the url field)
• This will run async with the filter conditions of URL field is not empty and Notify conference call.Service provider (another key table) field is "Microsoft Teams"
• I have this as Insert as a new notify_recording record is created each time a Microsoft Teams Meeting is initialized and then "Ended". That means this will work if you have multiple meetings on one Major Incident. Each meeting is treated as its own interaction. 
• The script has the hierarchy of notify_recording > notify_conference_call table >incident_alert_task > incident_alert >incident. (these are very important tables to know)This has a lot of paths to go to get the data in order to feed the REST API to get the data from Microsoft Teams.

After reviewing, best practice is to create a script include and then call that from the business rule. I am going to correct my direction to follow best practice.