Microsoft Teams Connector

Use the Microsoft Teams Connector node to distribute documents to Teams, an online file sharing and Cloud content management service for businesses. The connector allows you to send documents to Teams via an automated workflow, or you can access Teams directly at the MFP panel.

Note: To use the Microsoft Teams Connector node, you must have a Teams account.

To open the Microsoft Teams Connector node’s configuration window, add a Distribution node for Teams to your workflow and double-click on it.

Adding Your Teams Account

To utilize the Microsoft Teams Connector, the user must first add the Teams Account to Dispatcher Phoenix Web. For more information, see the Dispatcher Phoenix Web Accounts page.

Configuring the Microsoft Teams Connector

• Enabled - To enable this node in the current workflow, ensure the Enabled box is checked. By default, nodes are enabled upon creation. If you disable the node, the workflow will ignore it. While the workflow will still validate, documents will not be output and may be lost. Note that a disabled node does not check for logic or error conditions.

• Node Name - The node name defaults to this field. This name appears in the workflow below the node icon. Use this field to specify a meaningful name for the node that indicates its use in the workflow.

• Node Description - Enter an optional description for this node. A description can help you remember the purpose of the node in the workflow or distinguish nodes from each other. If the description is long, you can hover the mouse over the field to read its entire contents.

Buttons

• Help - To access Dispatcher Phoenix Online Help, click this button.
• Metadata - To access the Metadata Browser window, click this button.
• Cancel - To exit the window without saving any changes, click this button.
• Save - To preserve your node configuration and exit the window, click this button.

Connection Setup

In the Connection area:

• Account - Click the drop-down to see a list of authorized Microsoft Teams accounts. If no accounts appear, be sure the logon user accounts for Dispatcher Phoenix Web and Microsoft Teams must match.
• Connection timeout (in seconds) - Specify the number of seconds you want to elapse before a network connection times out (i.e., for login or logout operations).
• Refresh Data - Selecting this button will send a new request to Microsoft Teams to retrieve any updated teams and channels of the currently selected account.

Connecting to Teams

To connect to Microsoft Teams, do the following:

1. In the Connection area, select a Teams account from the dropdown.

Note: If you have not already set up a Teams account through Dispatcher Phoenix Web, you must do this before it will appear in the dropdown.

To modify the default Connection Timeout (the seconds allotted for the time without communication, after initial connection to the server, before a timeout occurs), enter a value in the Connection Timeout field.

Node Configuration

To begin sending messages, do the following:

1. In the Teams area, select one of the available teams. This will show the available channels within that team. Alternatively, you can enter the Team and Channel into the Path field using the following syntax: TeamName/ChannelName.

Notes:

• The Path field automatically populates with the Team and Channel as you select them.
• The Path, Subject and Message fields support metadata. To add metadata to these fields, click on the Metadata button to open the Metadata Browser window. You can then drag-and-drop metadata variables into the appropriate fields.

2. Select one of the available channels.

3. In the Set Post area, enter the subject of the message in the Subject field.

4. Enter the message contents in the Message field.

5. Select the Save button to save the node configuration and close the node.

Important!

• It is a best practice to organize Teams and Channels with unique names to avoid confusion when using Microsoft Teams and the Microsoft Teams Connector; attempting to send messages and documents to Teams or Channels with identical names can produce unexpected outcomes.
• The Microsoft Teams Connector may experience errors with Team or Channel names longer than 240 characters.
• The Microsoft Teams Connector will upload 1 file per post even if the Input node has the “Process files as a group” option enabled.

Creating the Microsoft Teams Index Form

To set up the Microsoft Teams Connector with an attached Index Form, do the following:

1. Add a node that is capable of attaching an Index Form (e.g. MFP Panel) to your workflow by dragging and dropping it into the Workflow Builder area, and connect it to the Microsoft Teams Connector.

2. Configure the Microsoft Teams Connector node according to the Application Setup section.

3. Open the node associated with the Index Form.

4. Click the checkbox next to Attach Index Form and then the + icon to open the Index Form Builder. Then, select the Blank Index Form option in the pop-up, as in the following illustration:

5. Drag the Microsoft Teams Connector icon to the Index Form Builder working area. Several fields will populate, as in the following illustration:

6. Validate, Save, and close the Index Form Builder.

Accessing Microsoft Teams on MFP

When the Microsoft Teams Connector is configured with an Index Form, the user will be automatically logged into the connected account when accessing the workflow from the MFP. To use the Microsoft Teams Connector at the MFP Panel, do the following:

1. At the MFP, open the workflow containing the Microsoft Teams Connector and the node associated with the Index Form that you have already configured. Select the Team you would like to connect to, as in the following illustration:

2. Select the Channel within that Team you would like to send the document and message to, as in the following illustration:

3. Enter a subject and message to be sent along with your attached file, as in the following illustration: