Skip to content

Commit 524c84f

Browse files
gregli-msftgregli-msft
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/powerapps-docs-pr into gregli-confirmexit
2 parents 8387e9f + 76dee0d commit 524c84f

27 files changed

+214
-3
lines changed

‎pending-deleted-files.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ This file tracks files marked for deletion. Localization requirements mean that
77
These files have been redirected, but the actual .md topic files can't been removed yet.
88

99
powerapps-docs\maker\canvas-apps\working-with-experimental.md
10+
powerapps-docs/maker/common-data-service/entity-relationship-behavior.md
1011

1112
These files have been redirected, and the .md topic files have been deleted. This list hasn't been provided to loc yet.
1213

‎powerapps-docs/developer/common-data-service/use-webhooks.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -88,6 +88,9 @@ The body will contain string that represents the JSON value of an instance of th
8888

8989
The service you create must parse this data to extract the relevant items of information for your service to provide its function. How you choose to parse this data depends on the technology you are using and your preferences.
9090

91+
> [!IMPORTANT]
92+
> Due to certain Service Bus optimizations, it is not recommended that .NET developers deserialize the JSON formatted message request body to a <xref:Microsoft.Xrm.Sdk.RemoteExecutionContext> object. Rather, use [JObject](https://www.newtonsoft.com/json/help/html/T_Newtonsoft_Json_Linq_JObject.htm) to parse the message body.
93+
9194
The following is an example of the serialized JSON data passed for a step registered with the following properties:
9295

9396

‎powerapps-docs/maker/TOC.yml

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -691,8 +691,8 @@
691691
href: ./canvas-apps/share-app-resources.md
692692
- name: Embed an app in Power BI
693693
href: ./canvas-apps/embed-powerapps-powerbi.md
694-
# - name: Embed a Teams app
695-
# href: ./canvas-apps/embed-teams-app.md
694+
- name: Embed a Teams app
695+
href: ./canvas-apps/embed-teams-app.md
696696
- name: Manage an app
697697
items:
698698
- name: Edit an app
@@ -756,7 +756,11 @@
756756
- name: Let customers test drive your apps
757757
href: ./canvas-apps/dev-appsource-test-drive.md
758758
- name: Create a component
759-
href: ./canvas-apps/create-component.md
759+
items:
760+
- name: Overview
761+
href: ./canvas-apps/create-component.md
762+
- name: Behavior formulas
763+
href: ./canvas-apps/component-behavior.md
760764
- name: Embed canvas apps in your applications
761765
href: ./canvas-apps/embedding-sdk.md
762766
- name: Model-driven apps

‎powerapps-docs/maker/canvas-apps/component-behavior.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
title: Behavior formulas for components | Microsoft Docs
3+
description: Trigger an app to perform one or more tasks when a component-based action occurs.
4+
author: yifwang
5+
ms.service: powerapps
6+
ms.topic: article
7+
ms.date: 05/24/2019
8+
ms.author: yifwang
9+
search.audienceType:
10+
- maker
11+
search.app:
12+
- PowerApps
13+
---
14+
15+
# Behavior formulas for components
16+
17+
> [!IMPORTANT]
18+
> This feature is still experimental and disabled by default. For more information, see [Experimental and preview features](working-with-experimental.md).
19+
20+
Specify one or more [behavior formulas](working-with-formulas-in-depth.md) that run when an event triggers a change in component instances. For example, set a component's **OnReset** property to one or more formulas that perform initialization, clear input, and reset values when the **Reset** function runs on the component instances.
21+
22+
## OnReset ##
23+
24+
With a component selected, select **OnReset** in the drop-down list of properties (on the right side of the formula bar), and then enter one or more formulas.
25+
26+
> [!div class="mx-imgBorder"]
27+
> ![OnReset example](./media/component-behavior/example-onreset.png)
28+
29+
To test **OnReset**, configure a control to reset the component. For example, set the **OnSelect** property of a button to this formula: **Reset**(*ComponentName*)
30+
31+
> [!div class="mx-imgBorder"]
32+
> ![Reset button](./media/component-behavior/reset-button.png)

‎powerapps-docs/maker/canvas-apps/embed-teams-app.md

Lines changed: 170 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,170 @@
1+
---
2+
title: Embed a PowerApps app in Teams | Microsoft Docs
3+
description: You can embed an app created in PowerApps in Microsoft Teams to share it.
4+
author: jimholtz
5+
manager: kvivek
6+
ms.service: powerapps
7+
ms.topic: conceptual
8+
ms.custom: canvas
9+
ms.reviewer:
10+
ms.date: 05/29/2019
11+
ms.author: jimholtz
12+
search.audienceType:
13+
- maker
14+
search.app:
15+
- PowerApps
16+
---
17+
# Embed a PowerApps app in Teams
18+
19+
You can share a PowerApps you've created by embedding it directly into Microsoft Teams. When completed, users can select **+** to add your app to any of **your** team channels or conversations in the team you are in. The app appears as a tile under **Tabs for your team**.
20+
21+
An admin can upload the app so it shows up for **all** teams in your tenant under the **All tabs section**. See [Share an app in Microsoft Teams](https://review.docs.microsoft.com/en-us/power-platform/admin/embed-app-teams?branch=JimHoltzWorkBranch).
22+
23+
> [!NOTE]
24+
> Team custom app policies must be set to allow uploading custom apps. If unable to embed your app in Teams, check with your administrator to see if they've setup [custom app settings](https://docs.microsoft.com/MicrosoftTeams/teams-custom-app-policies-and-settings#custom-app-policy-and-settings).
25+
26+
## Prerequisites
27+
28+
- [Have a PowerApps license](https://docs.microsoft.com/power-platform/admin/pricing-billing-skus)
29+
- Created a canvas app
30+
31+
## Locate your PowerApp's GUID
32+
33+
Find and make note of your PowerApp's GUID to use in a later step.
34+
35+
1. Sign in to [https://web.powerapps.com](https://web.powerapps.com), and then select **Apps** in the menu.
36+
37+
> [!div class="mx-imgBorder"]
38+
> ![Show list of apps](./media/embed-teams-app/file-apps2.png "Show list of apps")
39+
40+
2. Select **More Commands** (...) for the app you want to share in Teams, and then select **Details**.
41+
42+
> [!div class="mx-imgBorder"]
43+
> ![App details](./media/embed-teams-app/app-details.png "App details")
44+
45+
3. Record the **App ID** for later use.
46+
47+
> [!div class="mx-imgBorder"]
48+
> ![App details](./media/embed-teams-app/app-details2.png "App details")
49+
50+
## Install App Studio
51+
52+
You can skip these steps if App Studio is already installed.
53+
54+
1. In Teams, select **Apps** in the lower-left of the Teams menu (![Apps icon](./media/embed-teams-app/apps-icon.png "Apps icon")).
55+
56+
2. Search for "App Studio" in the search box and then select it.
57+
58+
> [!div class="mx-imgBorder"]
59+
> ![App Studio](./media/embed-teams-app/store-app-studio.png "App Studio")
60+
61+
3. Select **Install**.
62+
63+
> [!div class="mx-imgBorder"]
64+
> ![Install App Studio](./media/embed-teams-app/install-app-studio.png "Install App Studio")
65+
66+
4. Select **Open** for the App feature.
67+
68+
> [!div class="mx-imgBorder"]
69+
> ![Open App Studio](./media/embed-teams-app/open-app-studio.png "Open App Studio")
70+
71+
## Create a Teams app for your PowerApp
72+
73+
1. In Teams, open App Studio.
74+
75+
> [!div class="mx-imgBorder"]
76+
> ![Open App Studio](./media/embed-teams-app/open-app-studio2.png "Open App Studio")
77+
78+
2. Select the **Manifest editor** tab, and then select **Create a new app** under Welcome.
79+
80+
> [!div class="mx-imgBorder"]
81+
> ![Create new app](./media/embed-teams-app/create-new-app.png "Create new app")
82+
83+
3. Fill in information about your app in the **App Details** page. For the App ID GUID, you should use your PowerApp's App ID GUID you recorded above. This will avoid duplication of Teams apps for a particular PowerApp.
84+
85+
> [!div class="mx-imgBorder"]
86+
> ![Fill in information](./media/embed-teams-app/fill-in-info-about-app.png "Fill in information")
87+
88+
|Fields |Description |
89+
|---------|---------|
90+
|**App names** | |
91+
|Short name | Required. The short display name for the app. 30 character limit. |
92+
|Long name | The full name of the app, used if the full app name exceeds 30 characters. |
93+
|**Identification** | |
94+
|App ID | Required. The unique Microsoft-generated identifier for this app. |
95+
|Package Name | Required. A unique identifier for this app. We recommend using reverse ___domain notation; for example, com.example.<AppName>. |
96+
|Version | Required. The version of the specific app. If you update something in your manifest, the version must be incremented as well. |
97+
|**Descriptions** | |
98+
| Short description | Required. A short description of your app experience, used when space is limited. 80 character limit. |
99+
| Long description | Required. The full description of your app. |
100+
| **Developer information** | |
101+
| Name | Required. The display name for the company or developer. |
102+
| Website | Required. The https:// URL to the website for your app via powerapps.com. When someone installs your app, an “About your app” page will appear. It should link to the web version of your app on powerapps.com. |
103+
| **App URLs** | These links will show up in the **About** page along with the website URL. |
104+
| Privacy statement | Required. The https:// URL to the developer's privacy policy. [Example](https://go.microsoft.com/fwlink/p/?LinkID=698505). |
105+
| Terms of use | Required. The https:// URL to the developer's terms of use. [Example](https://go.microsoft.com/fwlink/p/?LinkID=698507). |
106+
| **Branding** | |
107+
| Full color | A relative file path to a full color 192x192 PNG icon. |
108+
| Transparent outline |A relative file path to a transparent 32x32 PNG outline icon. |
109+
| Accent color | A color to use in conjunction with and as a background for your outline icons. |
110+
111+
For more information, see [Manifest Editor](https://docs.microsoft.com/microsoftteams/platform/get-started/get-started-app-studio#manifest-editor) and [Manifest schema](https://docs.microsoft.com/microsoftteams/platform/resources/schema/manifest-schema).
112+
113+
4. Scroll down to the Branding section and add your logos and the accent color desired for your app. These are the logos that will appear for your app in Teams.
114+
115+
> [!div class="mx-imgBorder"]
116+
> ![Branding and Tabs](./media/embed-teams-app/branding-tabs.png "Branding and Tabs")
117+
118+
5. Under **Capabilities**, select **Tabs**.
119+
120+
6. Under **Team tab** select **Add**.
121+
122+
> [!div class="mx-imgBorder"]
123+
> ![Team tab Add](./media/embed-teams-app/team-tab-add.png "Team tab Add")
124+
125+
7. Add your app's configuration URL in the "Configuration URL" input field, using the following format: `https://web.powerapps.com/webplayer/teamsapptabsettings?appid=<PowerApp ID>`
126+
127+
Replace `<PowerApp ID>` with the App ID GUID you recorded above.
128+
129+
Select the [scope](https://docs.microsoft.com/microsoftteams/platform/concepts/tabs/tabs-overview#tab-scope) for your app to appear in. Ensure **Can update configuration** is checked, and then select **Save**.
130+
131+
> [!div class="mx-imgBorder"]
132+
> ![Configuration URL](./media/embed-teams-app/configuration-url.png "Configuration URL")
133+
134+
8. Under **Finish**, select **Valid domains**. Add **apps.powerapps.com** and **apps.preview.powerapps.com** as valid domains for the Teams application.
135+
136+
> [!div class="mx-imgBorder"]
137+
> ![Add valid domains](./media/embed-teams-app/add-valid-domains.png "Add valid domains")
138+
139+
9. Under **Finish**, select **Test and distribute**. Under **Install**, select **Install**.
140+
141+
> [!div class="mx-imgBorder"]
142+
> ![Select Install](./media/embed-teams-app/test-distribute-app.png "Select Install")
143+
144+
10. Select the team you want the app installed in, and then select **Install**.
145+
146+
> [!div class="mx-imgBorder"]
147+
> ![Add to team Install](./media/embed-teams-app/new-app-add-to-team.png "Add to team Install")
148+
149+
11. If you want to add an instance of that app to a channel right away, select the channel you wish to use the app in and select **Set up**.
150+
151+
> [!div class="mx-imgBorder"]
152+
> ![Select Set up](./media/embed-teams-app/app-now-available.png "Select Set up")
153+
154+
12. Select **Save**.
155+
156+
## Add the app as a tab
157+
158+
To add the app as a tab to any channel or conversation, select **+**, and then under **Tabs for your team** select your app.
159+
160+
> [!div class="mx-imgBorder"]
161+
> ![Add app as tab](./media/embed-teams-app/add-app-as-tab.png "Add app as tab")
162+
163+
The app now appears as a tab.
164+
165+
> [!div class="mx-imgBorder"]
166+
> ![App as tab](./media/embed-teams-app/app-as-tab.png "App as tab")
167+
168+
### See also
169+
[Welcome to Microsoft Teams](https://docs.microsoft.com/MicrosoftTeams/teams-overview)<br />
170+
[For admins: Embed an app in Microsoft Teams](https://docs.microsoft.com/power-platform/admin/share-app-teams)

‎powerapps-docs/maker/canvas-apps/media/component-behavior/example-onreset.png

14.6 KB
Loading

‎powerapps-docs/maker/canvas-apps/media/component-behavior/reset-button.png

56.3 KB
Loading

‎powerapps-docs/maker/canvas-apps/media/embed-teams-app/add-app-as-tab.png

31.6 KB
Loading

‎powerapps-docs/maker/canvas-apps/media/embed-teams-app/add-valid-domains.png

91.1 KB
Loading

‎powerapps-docs/maker/canvas-apps/media/embed-teams-app/app-as-tab.png

6.67 KB
Loading

0 commit comments

Comments
 (0)