Overview

Microsoft Teams is one of the most used communication platforms in business as well as personal communication. However, if your requirement is that you want to schedule MS Team meetings via any of your Mendix applications, you will need to customize the code which might take time and effort.

So, we have developed a module to reduce such effort and provide re-usability keeping in mind for such requirement(s) where one needs to create MS Teams meeting link in their Mendix workflow. Anyone can download this module and plug-in into their existing code.

Documentation

Microsoft Teams meeting Scheduler module

Description

Microsoft Teams is one of the most used communication platforms in business as well as personal communication. However, when you want to schedule meetings on Teams channel using via any of the Mendix applications, we need to customize the code and that might take time and effort.

So we have developed a module to reduce the effort when there is a requirement to integrate a MS Teams meeting in the workflow. Anyone can download and plug-in this module into their existing code.

Features and Limitations

• Plan Online MS Teams meetings and generate meeting invite in a web URL link
• Generate QR code for the meeting link that can be scanned and thru which one can join the MS Teams meeting invite
• Add participants for the meeting ; use semi-colon to add multiple participants (this can be further enhanced by integrating with AD or relevant to fetch the list from an existing source)
• Specify the Date and Time of the meetings
• Add message to the Invite body (u can further enhance with RichTextEditor component as per the need)
• This module is specific to Web application only, you might make changes for the Mobile using Nano-flows

Dependencies

Ensure you have also installed the below components (from Mendix market place) before you start using our module:

• Encryption module
• NanoflowCommons module
• Community Commons
• Microsoft Graph Connector
• Barcode and QR code generator

Configuration

• Install the module and all of the dependencies
• Create an App Registration or get access to an existing App Registration in your Azure tenant. Use the Credentials to configure your Authentication and get authorization as a user. Make sure that the App Registration has the correct API permissions (Calendars.ReadWrite, Mail.ReadWrite, OnlineMeetings.ReadWrite)
• To make sure the authorization flow can be completed, the Redirect URIs need to be configured in the Authentication section of your app registration (in Azure portal). You can find (and change) the URI in the PRS_Azure REST service. For local deployment it should most likely be http://localhost:8080/oauth/v2/callback_azure.
• Create a new Authentication object (in Mendix). This will be used for all authorization requests from the admin and other users that are allowed to request authorization. Fill in the Application (client) ID, Directory (tentant) ID and Client Secret from your Azure App Registration. Once these are filled in, the Well-Known Configuration will be retrieved.
• Choose the relevant scopes for you authentication. If you want to add more scopes, you can do so in the Metadata group box in the Supported Scopes section.
• Select your preferred Response Type, Response Mode and Prompt for authorization. Response Type "Code", Response Mode "Query" , Prompt as “Consent” are recommended for most used cases.
• Add the page “Authentication_Overview” to the Navigation tab as a configuration page
• Click “Add Authentication” button and fill-in the required details
• Use the Application ID, Directory ID and Application Secret from your Azure App Registration to get authorization for your user.

(Refer to Screen#1 and Screens#2,3 in the last Screenshots section – fill the ‘scope’ field as you see in the screenshot)

Microflow configuration (after above setup is completed)

• Refer to the “ACT_Demomeeting” microflow available as a reference and create your own microflow and configure accordingly to execute the Teams meeting requirement

refer to screenshots attached as supporting to documentation 

Development Team

Abrar Ahmed, Chayanath P