This documentation supports the 25.1 version of BMC Helix ITSM: Service Desk.To view an earlier version, select the version from the Product version menu.

Launching ChatOps for collaboration


You can launch a Microsoft Teams chat from an incident screen. When you launch a chat from an incident screen, all the team members associated with the incident are automatically invited to the chat. You can also add team members that are not associated with the incident to the chat.

To hide the Launch ChatOps option, you must change the visibility flag of this option in Developer Studio. For complete information on how to hide the Launch ChatOps option in BMC Helix ITSM, see knowledge article 000403486.

Important

The incident screen does not save the chat discussion in the ticket.

Before you begin

Make sure that the administrator has configured Azure settings so that the service desk agents, specialists, or major incident management team members can launch the Microsoft Teams chat for collaboration from incidents from an incident screen. For more information, see Configuring-settings-to-launch-Microsoft-Teams-chat-from-incidents.

To launch a Microsoft Teams chat from an incident screen 

  1. Open an existing incident.
  2. Click Launch ChatOps.

    chat ops.png

  3. In the popup window, click Launch ChatOps.
    A Microsoft Teams chat is launched from the incident.

When you launch a chat from an incident, the activity feed does not display any Microsoft Teams-related activity, and the chat transcript is not saved on the activity feed.

To add new members to a Microsoft Teams chat

  1. Open an existing incident.
  2. Click Launch ChatOps.
  3. In the popup window, enter values in the Support group and Person fields.

    image2022-6-21_15-21-26.png

  4. Click Add.

Important

If New Microsoft Teams is enabled, you get the following error:

Teams.png

As a workaround, perform the following steps to open the chat in New Microsoft Teams:

  1. Create an overlay for Active link : SHR:MCR:SV_MajorInc_CR_RunProcess.
  2. Enter the updated field mapping value.

    Existing field mapping value

    New field mapping value

    z1d_SV_Char06=(("https://teams.microsoft.com/l/chat/0/0?topicName=" + $SV_SH_SourceRequestID$) + "-") + $SV_CR_SourceReqDesc$

    z1d_SV_Char06=("https://teams.microsoft.com/_#/conversations/" + $INC_ChatID$) + "?ctx=chat"


To add BMC Helix bot to the Microsoft Teams chat

You can manually add the BMC Helix chat bot to the Microsoft Teams chat, or you can configure a CCS parameter to include the bot by default when the chat group is created.

Chatbot.jpg

In Centralized configuration, add a CCS parameter ChatBot-Id and enter the bot ID as shown in the Setting configuration parameters in BMC Helix ITSM topic.
The bot ID is the Microsoft App ID available in Configurations settings under your Bot Channels Registration in Azure portal. Alternatively, Application (client) ID of your registered application name under App registrations in Azure portal can be entered as bot ID. You must have the application administrator permissions in Azure to view the bot ID.

Important

If you do not add the CCS parameter, or if you do not enter a bot ID for the CCS parameter, the bot will not be added to the chat and there will be no error message. But, if you add an incorrect bot ID you will receive a warning message to validate the Microsoft Teams configuration.

Microsoft ID.png

App ID.png

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*