103 lines
5.2 KiB
Markdown
103 lines
5.2 KiB
Markdown
# Teams Configuration Tab
|
|
|
|
This web part makes a modern SharePoint page into a Teams tab configuration page for use in a Teams application. This allows low-code developers to create Teams applications containing configurable tabs without the need to code a custom configuration page. Using this tool, along with Microsoft Teams App Studio, low-code developers can build Teams applications entirely from modern SharePoint pages.
|
|
|
|
Microsoft Teams applications support _configurable tabs_ that work in Teams channels and group chat conversations. Configurable tabs require a configuation page that is presented to users when they add a tab. This web part implements a simple configuration experience.
|
|
|
|
|
|
|
|
When the user selects one of the tab options, the tab is saved pointing to the corresponding SharePoint page.
|
|
|
|
|
|
|
|
|
|
# Compatibility
|
|
|
|
|
|
|
|
|
|
|
|
-Incompatible-red.svg "SharePoint Server 2016 Feature Pack 2 requires SPFx 1.1")
|
|
|
|
|
|
|
|
## Applies to
|
|
|
|
* [SharePoint Framework Developer](https://docs.microsoft.com/sharepoint/dev/spfx/sharepoint-framework-overview)
|
|
* [Office 365 developer tenant](https://docs.microsoft.com/sharepoint/dev/spfx/set-up-your-developer-tenant)
|
|
|
|
|
|
## Solution
|
|
|
|
Solution|Author(s)
|
|
--------|---------
|
|
Tab Configuration Web Part | Bob German ([@Bob1German](http://www.twitter.com/Bob1German))
|
|
|
|
## Version history
|
|
|
|
Version|Date|Comments
|
|
-------|----|--------
|
|
1.0|January 6, 2020|Initial release
|
|
|
|
|
|
## Disclaimer
|
|
**THIS CODE IS PROVIDED *AS IS* WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.**
|
|
|
|
---
|
|
|
|
## Minimal Path to Awesome
|
|
|
|
#### 1. Build the web part
|
|
|
|
Build and package the web part
|
|
|
|
* npm install
|
|
* gulp bundle --ship
|
|
* gulp package-solution --ship
|
|
|
|
Install into your SharePoint app catalog and add it to a SharePoint site.
|
|
|
|
|
|
#### 2. Create a configuration page
|
|
|
|
Create a new modern SharePoint page that will become the tab configuration page, and add the Configure Tab web part. Edit the web part to set up the tab information.
|
|
|
|
|
|
|
|
Your configuration page will present users with one or more choices for tabs they'd like to show. Enter a line for each choice into the edior panel:
|
|
|
|
(1) Enter a name for each tab, each on its own line
|
|
(2) Enter a unique entity ID for each tab, each on its own line corresponding to the lines in (1)
|
|
(3) Enter the URL for each tab, again each on its own line
|
|
|
|
If you want all tab clicks to be redirected back through this page, select the Redirect checkbox. This allows you to change the URL's for tabs even after they've been configured, however users may notice the page flickering as they are redirected.
|
|
|
|
#### 3. Set up the app manifest
|
|
|
|
Create a new app manifest in [Teams App Studio](https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/app-studio-overview), and add a Team Tab. Paste the URL of your configuration page into the Configuration URL field.
|
|
|
|
|
|
|
|
If you want users to be able to edit the tab and return to the configuration page (and maybe switch to another choice), then check the Can update configuration checkbox. You can also decide if your app is available in Teams, Group Chats, or both.
|
|
|
|
#### 4. Deploy
|
|
|
|
Now check to be sure the valid domains are set up (as above) and install the app into a Teams channel or Group Chat. You will be presentd with the configuration page.
|
|
|
|
|
|
|
|
If you only configured one choice, just click the Save button and save your tab. If you configured multiple choices, pick one and the save button will light up and allow you to save the tab.
|
|
|
|
|
|
|
|
Now your page is visible within the new tab for all to see.
|
|
|
|
#### 5. Maintain
|
|
|
|
If you set the web part up to redirect tab clicks, it saved its own URL and the entity ID into Teams for each tab. The web part will look at the entity ID and redirect to the target page. Thus it is possible to edit the web part and change the URLs, and thus change all the tabs that had previously been created.
|
|
|
|
If you edit the web part and remove the choice (entity ID), it will prompt the user to edit the tab and make another selection.
|
|
|
|
|
|
<img src="https://telemetry.sharepointpnp.com/sp-dev-fx-webparts/samples/react-teams-configure-tab" />
|