Skip to content

Commit 855641e

Browse files
authored
Merge branch 'main' into patch-3
2 parents 185fe3e + 2249a09 commit 855641e

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

47 files changed

+158
-72
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6269,6 +6269,11 @@
62696269
"source_path": "powerapps-docs/sample-apps/return-to-workplace/app-for-employee.md",
62706270
"redirect_url": "/dynamics365/industry/return-to-workplace/app-for-employee",
62716271
"redirect_document_id": "false"
6272+
},
6273+
{
6274+
"source_path": "powerapps-docs/developer/data-platform/developer-resources-page.md",
6275+
"redirect_url": "/powerapps/developer/data-platform/view-download-developer-resources",
6276+
"redirect_document_id": "false"
62726277
}
62736278
]
62746279
}

powerapps-docs/developer/data-platform/developer-resources-page.md

Lines changed: 0 additions & 32 deletions
This file was deleted.

powerapps-docs/developer/data-platform/entity-metadata.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ More information: [Image columns](image-attributes.md), [Sample: Set and retriev
8585
8686
## Types of tables
8787

88-
The capabilities and behavior of tables depends on several table properties. Most of these properties are relatively simple and have descriptive names. Four that require some additional explanation are: *Ownership*, *Activity tables*, *Activityparty table* and *Child tables*.
88+
The capabilities and behavior of tables depends on several table properties. Most of these properties are relatively simple and have descriptive names. Among four properties that require some additional explanation are: *Ownership*, *Activity tables*, *Activityparty table* and *Child tables*.
8989

9090
### Table ownership
9191

powerapps-docs/developer/data-platform/view-download-developer-resources.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,6 @@ search.app:
2222

2323
# View or download developer resources
2424

25-
[!INCLUDE[cc-terminology](includes/cc-terminology.md)]
26-
2725
This article provides resources for developers and information about the specific environment you're working with.
2826

2927
## View the Developer Resources page for your environment
@@ -72,6 +70,8 @@ You can download the WSDL for this service here, but usually you will use the Cr
7270
- [Create early bound table classes with the code generation tool (CrmSvcUtil.exe)](/powerapps/developer/data-platform/org-service/generate-early-bound-classes)
7371
- [Use the Organization Service](/powerapps/developer/data-platform/org-service/overview)
7472

73+
[!INCLUDE[cc-terminology](includes/cc-terminology.md)]
74+
7575
### Instance Reference Information
7676

7777
This information uniquely describes your instance. There is a GUID **ID** and a **Unique Name**.
@@ -92,4 +92,3 @@ More information: [Discover the URL for your organization using the Web API](/po
9292
This is the endpoint address for the SOAP version of the Discovery service to use for your instance. You can also download the service document here.
9393
More information: [Discover the URL for your organization using the Organization service](/powerapps/developer/data-platform/org-service/discovery-service)
9494

95-
[!INCLUDE[footer-include](../../includes/footer-banner.md)]
Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,10 @@
1+
<!--
2+
13
> [!NOTE]
24
> Effective November 2020:
35
> - Common Data Service has been renamed to Microsoft Dataverse. [Learn more](https://aka.ms/PAuAppBlog)
46
> - Some terminology in Microsoft Dataverse has been updated. For example, *entity* is now *table* and *field* is now *column*. [Learn more](https://go.microsoft.com/fwlink/?linkid=2147247)
57
>
68
> This article will be updated soon to reflect the latest terminology.
9+
10+
-->

powerapps-docs/maker/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1393,6 +1393,8 @@
13931393
href: ./portals/use-code-editor.md
13941394
- name: Add Power BI
13951395
href: ./portals/add-powerbi.md
1396+
- name: Add a chatbot (Preview)
1397+
href: ./portals/add-chatbot.md
13961398
- name: Work with templates
13971399
href: ./portals/work-with-templates.md
13981400
- name: Work with themes

powerapps-docs/maker/canvas-apps/functions/function-isblank-isempty.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -101,8 +101,8 @@ The return value for both **IsBlank** and **IsEmpty** is a Boolean **true** or *
101101
| Formula | Description | Result |
102102
| --- | --- | --- |
103103
| **Coalesce(&nbsp;Blank(),&nbsp;1&nbsp;)** |Tests the return value from the **Blank** function, which always returns a *blank* value. Because the first argument is *blank*, evaluation continues with the next argument until a non-*blank* value and non-empty string is found. |**1** |
104-
| **Coalesce( "", 2 )** |Tests the first argument which is an empty string. Because the first argument is an empty string, evaluation continues with the next argument until a non-*blank* value and non-empty string is found. |**2** |
105-
| **Coalesce( Blank(), "", Blank(), "", 3, 4 )** |**Coalesce** starts at the beginning of the argument list and evaluates each argument in turn until a non-*blank* value and non-empty string is found. In this case, the first four arguments all return *blank* or an empty string, so evaluation continues to the fifth argument. The fifth argument is non-*blank* and non-empty string, so evaluation stops here. The value of the fifth argument is returned, and the sixth argument isn't evaluated. |**3** |
104+
| **Coalesce( "", "2" )** |Tests the first argument which is an empty string. Because the first argument is an empty string, evaluation continues with the next argument until a non-*blank* value and non-empty string is found. |**2** |
105+
| **Coalesce( Blank(), "", Blank(), "", "3", "4" )** |**Coalesce** starts at the beginning of the argument list and evaluates each argument in turn until a non-*blank* value and non-empty string is found. In this case, the first four arguments all return *blank* or an empty string, so evaluation continues to the fifth argument. The fifth argument is non-*blank* and non-empty string, so evaluation stops here. The value of the fifth argument is returned, and the sixth argument isn't evaluated. |**3** |
106106
| **Coalesce( "" )** | Tests the first argument which is an empty string. Because the first argument is an empty string, and there are no more arguments, the function returns *blank*. |*blank* |
107107
108108
### IsBlank
@@ -164,4 +164,4 @@ You can also use **IsEmpty** to test whether a calculated table is empty, as the
164164
165165
166166
167-
[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
167+
[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
Lines changed: 121 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,121 @@
1+
---
2+
title: Add chatbot to a page (Preview)
3+
description: Learn about how to add Power Virtual Agents chatbot to Power Apps portals page to answer questions using a bot.
4+
author: neerajnandwana-msft
5+
ms.service: powerapps
6+
ms.topic: conceptual
7+
ms.custom:
8+
ms.date: 05/18/2021
9+
ms.author: nenandw
10+
ms.reviewer: tapanm
11+
contributors:
12+
- neerajnandwana-msft
13+
- tapanm-msft
14+
---
15+
16+
# Add chatbot to a page (Preview)
17+
18+
[This article is pre-release documentation and is subject to change.]
19+
20+
Power Apps portals allows you to add a [Power Virtual Agents chatbot](/power-virtual-agents/fundamentals-what-is-power-virtual-agents) to answer questions posted by a visitor on your portal page. A chatbot (bot) configured with different topics, and trigger phrases, can automatically respond to questions posted by a visitor in a chat conversation.
21+
22+
> [!IMPORTANT]
23+
> - This is a preview feature.
24+
> - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)]
25+
26+
## Prerequisites
27+
28+
Before you add a Power Virtual Agents bot to a Power Apps portals page, you must create a bot first. If you don't have any available bots, you'll have the option in portals to go to Power Virtual Agents to create a bot. To learn about how to create a bot, go to [Create and delete Power Virtual Agents bots](/power-virtual-agents/authoring-first-bot).
29+
30+
> [!IMPORTANT]
31+
> This feature requires the following versions for starter portal package and portal host:
32+
> - Portal host version [9.3.4.x](versions/version-9.3.4.x.md) or later.
33+
> - Starter portal package version [9.2.2103.x](versions/package-version-9.2.2103.md) or later. More information: [additional considerations](#additional-considerations)
34+
35+
## Add chatbot component
36+
37+
To add a chatbot component to portal page:
38+
39+
1. Go to [Power Apps](https://make.powerapps.com).
40+
41+
1. Select **Apps** from the left pane.
42+
43+
1. Select your portal.
44+
45+
1. Select **Edit** to open the portals Studio.
46+
47+
1. Select **Components** from the left pane.
48+
49+
1. Select **Chatbot** component.
50+
51+
![Add chatbot component to a page](media/add-chatbot/add-chatbot.png "Add chatbot component to a page")
52+
53+
1. Select your bot.
54+
55+
![Select your bot](media/add-chatbot/select-your-bot.png "Select your bot")
56+
57+
> [!NOTE]
58+
> If you don't have a bot already created, or want to create a new bot to use in portals, select **Power Virtual Agents**. After you create bot, select **Sync configuration** inside portals Studio to reflect the bot changes.
59+
60+
1. Select whether the bot appears on all pages in your portal, or the selected pages.
61+
62+
1. If you select **Specific pages**, use **Manage bots in pages** to control pages that can use this bot.
63+
64+
You can add more bots from your environment across different pages in a portal. For example, a bot that answers questions related to workplace such as "Back to work" can be added to HR page. Or, a bot that answers to basic queries for payroll, such as "Payroll questions" can be added to Finance page. However, you can't have one page use more than one bot.
65+
66+
## Advanced configuration
67+
68+
Chatbot component is rendered using a web template called **Power Virtual Agents**.
69+
70+
![Chatbot web template](media/add-chatbot/pva-web-template.png "Chatbot web template")
71+
72+
You can change the values for the following parameters inside the "window.PvaEmbeddedWebChat.renderWebChat()" function.
73+
74+
| Parameter | Value |
75+
| - | - |
76+
| width | Uses variable "chatWidth". To change width, update the width in pixel: <br> `let chatWidth = "320px";` |
77+
| height | Uses variable "chatHeight". To change height, update the height in pixel: <br> `let chatHeight = "480px";` |
78+
| headerText | Title of the bot. By default, uses the bot's name. To change, add "headerText" parameter with the bot header value: <br> `"headerText": 'Contoso chatbot';` |
79+
| webChatHeaderStyleOptions | Determines header style for the chatbot component, such as the color of font, and background. To change, update "webChatHeaderStyleOptions" parameter with the values for "fontColor", and "backgroundColor" properties: <br> `"webChatHeaderStyleOptions": {"fontColor":'black',"backgroundColor":'white',}`
80+
81+
After changing the web template, ensure you select **Sync configuration** to update the configuration in open Studio session and reflect the changes.
82+
83+
> [!NOTE]
84+
> Any changes to the Power Virtual Agents web template other than the parameters explained above are not supported.
85+
86+
## Additional considerations
87+
88+
Consider the following when using Power Virtual Agents chatbot inside portals.
89+
90+
### Portal template version
91+
92+
This feature requires starter portal package version [9.2.2103.x](versions/package-version-9.2.2103.md) or later. If your portal template isn't upgraded to add support for chatbot component, you'll see following message when you try to add the component.
93+
94+
"Portal upgrade required" <br>
95+
"An upgrade is required to use this feature on your portal. If you upgrade the portal, ensure you Sync Configuration to refresh your current portals Studio session with new portals package."
96+
97+
When this message appears, upgrade your portal package. More information: [Update portals solution](admin/update-portal-solution.md)
98+
99+
> [!NOTE]
100+
> Upgrading starter portal package will enable any additional portals in your environment with the capability to use chatbot component. More information: [Starter portal package updates](release-updates.md#starter-portal-package-updates)
101+
102+
### Solution deletion
103+
104+
This feature comes with a portal solution called **MicrosoftPortalBot** with display name of **Dynamics 365 Portals - Bot**. Your portal will stop working if you delete this solution, and do not perform the following action.
105+
106+
If you delete **MicrosoftPortalBot** solution, you must restart your portal to ensure the portal works correctly.
107+
108+
To restart your portal:
109+
110+
1. Open [Power Platform admin center](admin/admin-overview.md) for your portal.
111+
1. On the left-pane, select **Portal Actions**.
112+
1. Select **Restart** to restart the portal.
113+
114+
> [!IMPORTANT]
115+
> Restarting the portal will make it unavailable for several minutes and users won’t be able to access the portal URL during this time..
116+
117+
1. Select **Restart** to confirm restarting the portal.
118+
119+
### See also
120+
121+
- [Add the bot to your live website](/power-virtual-agents/publication-connect-bot-to-web-channels)

powerapps-docs/maker/portals/add-powerbi.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: neerajnandwana-msft
55
ms.service: powerapps
66
ms.topic: conceptual
77
ms.custom:
8-
ms.date: 04/21/2021
8+
ms.date: 05/13/2021
99
ms.author: nenandw
1010
ms.reviewer: tapanm
1111
contributors:
@@ -33,8 +33,6 @@ To add a Power BI component to a web page:
3333

3434
1. From Portal components section, select **Power BI**. The Power BI placeholder is added to the canvas:
3535

36-
![Components](media/components-powerbi.png)
37-
3836
1. In the properties pane on the right side of the screen, enter the following information:
3937

4038
1. **Access type**: Select appropriate option from the drop-down as per your requirement.

powerapps-docs/maker/portals/compose-page.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: neerajnandwana-msft
55
ms.service: powerapps
66
ms.topic: conceptual
77
ms.custom:
8-
ms.date: 04/21/2021
8+
ms.date: 05/10/2021
99
ms.author: nenandw
1010
ms.reviewer: tapanm
1111
contributors:
@@ -50,15 +50,14 @@ To use the WYSIWYG editor:
5050

5151
5. Select the component to be added.
5252

53-
> [!div class=mx-imgBorder]
54-
> ![components pane](media/components-pane.png "Components pane")
53+
![components pane](media/components-pane.png "Components pane")
5554

5655
The selected component is added to the canvas inside the editable element.
5756

5857
6. To delete a component, select the component on the canvas and then select **Delete** on the command bar at the top of the page.
5958

6059
> [!div class=mx-imgBorder]
61-
> ![delete component](media/delete-component.png "Delete component")
60+
![delete component](media/delete-component.png "Delete component")
6261

6362
## Next steps
6463

0 commit comments

Comments
 (0)