Merge pull request #4655 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/powerapps-docs (branch main)

Author: tapanm-MSFT

powerapps-docs/maker/model-driven-apps/create-business-rules-recommendations-apply-logic-form.md

@@ -164,6 +164,9 @@ This section describes common issues that may occur when you use business rules.
 ### Full Name column and Address column not supported with Unified Interface apps
 Actions or conditions that use a composite column like the **Full Name** (fullname) column or an **Address** column aren't supported in apps based on Unified Interface.  Alternatively, you can use actions or conditions with the constituent columns. For example, for the **Full Name** column, you can use actions or conditions on the  **First Name** (firstname) and **Last Name** (lastname) columns. 
 
+### Business rules don't execute for some users
+Make sure that users have a security role that includes, at a minimum, user scope read privileges on the Process table. By default, the Basic User security role has this privilege.
+
 ### Business rules don't fire on editable grid on a dashboard
 Entity scoped business rules will not fire on an editable grid when the editable grid is configured on a dashboard page.
 
@@ -204,4 +207,4 @@ Select the lightbulb to expand the view and show the recommendation.
 
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

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

@@ -1,11 +1,11 @@
 ---
-title: Add chatbot to a page (Preview)
-description: Learn about how to add Power Virtual Agents chatbot to Power Apps portals page to answer questions using a bot.
+title: Add a chatbot to a page (Preview)
+description: "Learn how to add a Power Virtual Agents chatbot to a Power Apps portals page to automatically answer questions posted by a visitor in a chat conversation."
 author: neerajnandwana-msft
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: 
-ms.date: 05/18/2021
+ms.date: 06/11/2021
 ms.author: nenandw
 ms.reviewer: tapanm
 contributors:
@@ -17,15 +17,15 @@ contributors:
 
 [This article is pre-release documentation and is subject to change.]
 
-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.
+Power Apps portals allow 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 portals page. A chatbot (bot) configured with different topics and trigger phrases can automatically respond to questions posted by a visitor in a chat conversation.
 
 > [!IMPORTANT]
 > - This is a preview feature.
 > - [!INCLUDE[cc_preview_features_definition](../../includes/cc-preview-features-definition.md)]
 
 ## Prerequisites
 
-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).
+Before you can add a Power Virtual Agents bot to a Power Apps portals page, you must create a bot first. If you don't already have an available bot or one that fits your needs, you'll have the option in portals to go to Power Virtual Agents to create one. To learn how to create a bot, go to [Create and delete Power Virtual Agents bots](/power-virtual-agents/authoring-first-bot).
 
 > [!IMPORTANT]
 > This feature requires the following versions for starter portal package and portal host:
@@ -34,7 +34,7 @@ Before you add a Power Virtual Agents bot to a Power Apps portals page, you must
 
 ## Add chatbot component
 
-To add a chatbot component to portal page:
+Once you have a chatbot created, you can add this component to a portals page with the following steps:
 
 1. Go to [Power Apps Preview](https://make.preview.powerapps.com).
 
@@ -55,64 +55,63 @@ To add a chatbot component to portal page:
     ![Select your bot](media/add-chatbot/select-your-bot.png "Select your bot")
 
     > [!NOTE]
-    > 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.
+    > 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 your bot, select **Sync configuration** inside portals Studio to reflect the bot changes.
 
-1. Select whether the bot appears on all pages in your portal, or the selected pages.
+1. Select whether the bot appears on all pages in your portal, or on specific pages.
 
-1. If you select **Specific pages**, use **Manage bots in pages** to control pages that can use this bot.
+1. If you select **Specific pages**, use **Manage bots in pages** to control the pages that can use this bot.
 
-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.
+You can add more bots from your environment across different pages in a portal. For example, a bot that answers questions related to the workplace can be added to an HR page. Or a bot that answers basic payroll queries can be added to a Finance page. However, you can't have one page use more than one bot.
 
 ## Advanced configuration
 
-Chatbot component is rendered using a web template called **Power Virtual Agents**.
+The chatbot component is rendered using a web template called **Power Virtual Agents**.
 
 ![Chatbot web template](media/add-chatbot/pva-web-template.png "Chatbot web template")
 
 You can change the values for the following parameters inside the "window.PvaEmbeddedWebChat.renderWebChat()" function.
 
 | Parameter | Value |
 | - | - |
-| width | Uses variable "chatWidth". To change width, update the width in pixel: <br> `let chatWidth = "320px";` |
-| height | Uses variable "chatHeight". To change height, update the height in pixel: <br> `let chatHeight =  "480px";` |
-| 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';` | 
-| 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',}`
+| width | Uses variable "chatWidth". To change, update the width in pixels: <br> `let chatWidth = "320px";` |
+| height | Uses variable "chatHeight". To change, update the height in pixels: <br> `let chatHeight =  "480px";` |
+| headerText | Title of the bot. By default, this uses the bot's name. To change, add "headerText" parameter with the bot header value: <br> `"headerText": 'Contoso chatbot';` | 
+| webChatHeaderStyleOptions | Determines header style for the chatbot component, such as color of font and background. To change, update "webChatHeaderStyleOptions" parameter with the values for "fontColor" and "backgroundColor" properties: <br> `"webChatHeaderStyleOptions": {"fontColor":'black',"backgroundColor":'white',}`
 
-After changing the web template, ensure you select **Sync configuration** to update the configuration in open Studio session and reflect the changes.
+After changing the web template, ensure you select **Sync configuration** to update the configuration and reflect the changes.
 
 > [!NOTE]
 > Any changes to the Power Virtual Agents web template other than the parameters explained above are not supported.
 
 ## Additional considerations
 
-Consider the following when using Power Virtual Agents chatbot inside portals.
+Consider the following when using a Power Virtual Agents chatbot inside portals:
 
 ### Portal template version
 
-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.
+This feature requires the 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 the chatbot component, you'll see following message when you try to add the component:
 
-"Portal upgrade required" <br>
-"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."
+"**Portal upgrade required:** _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._"
 
-When this message appears, upgrade your portal package. More information: [Update portals solution](admin/update-portal-solution.md)
+When this message appears, upgrade your portal package. For more information, see [Update portals solution](admin/update-portal-solution.md).
 
 > [!NOTE]
-> 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)
+> Upgrading the 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)
 
 ### Solution deletion
 
-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.
+This feature comes with a portal solution called **MicrosoftPortalBot** with the display name of **Dynamics 365 Portals - Bot**. Your portal will stop working if you delete this solution and don't perform the following action.
 
-If you delete **MicrosoftPortalBot** solution, you must restart your portal to ensure the portal works correctly.
+If you delete the **MicrosoftPortalBot** solution, you must restart your portal to ensure the portal works correctly.
 
 To restart your portal:
 
 1. Open [Power Platform admin center](admin/admin-overview.md) for your portal.
-1. On the left-pane, select **Portal Actions**.
+1. On the left pane, select **Portal Actions**.
 1. Select **Restart** to restart the portal.
 
     > [!IMPORTANT]
-    > Restarting the portal will make it unavailable for several minutes and users won’t be able to access the portal URL during this time..
+    > Restarting the portal will make it unavailable for several minutes and users won’t be able to access the portal URL during this time.
 
 1. Select **Restart** to confirm restarting the portal.
 

powerapps-docs/maker/portals/overview.md

@@ -1,11 +1,11 @@
 ---
-title:  What is Power Apps portals?
-description: Design and build websites using Power Apps that allow external users to interact with the data stored in the Microsoft Dataverse.
+title:  What are Power Apps portals?
+description: "Design and build websites using Power Apps that allow external users to interact with the data stored in the Microsoft Dataverse."
 author: sandhangitmsft
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: intro-internal
-ms.date: 04/21/2021
+ms.date: 06/11/2021
 ms.author: sandhan
 ms.reviewer: tapanm
 searchScope:
@@ -15,36 +15,36 @@ contributors:
     - sandhangitmsft
 ---
 
-# What is Power Apps portals?
+# What are Power Apps portals?
 
 Power Apps makers can now create a powerful new type of experience: external-facing websites that allow users outside their organizations to sign in with a wide variety of identities, create and view data in Microsoft Dataverse, or even browse content anonymously. The full capabilities of Dynamics 365 Portals, previously offered only as an add-on to customer engagement apps (Dynamics 365 Sales, Dynamics 365 Customer Service, Dynamics 365 Field Service, Dynamics 365 Marketing, and Dynamics 365 Project Service Automation), are now available standalone in Power Apps.  
 
 These capabilities feature a revamped end-to-end experience for makers to quickly create a website and customize it with pages, layout, and content. Makers can reuse page designs through templates, add forms and views to display key data from Dataverse, and publish to users.
 
-## Power Apps portals, Dynamics 365 portals and add-on portals
+## Power Apps portals, Dynamics 365 Portals, and add-on portals
 
-After the launch of Power Apps portals on October 1, 2019, Dynamics 365 portals are called as Power Apps portals. In other words, all portals are referred to as **Power Apps portals**.
+After the launch of Power Apps portals on October 1, 2019, all Dynamics 365 Portals are now referred to as **Power Apps portals**.
 
-One of the major changes introduced in portals after October 1, 2019 is the licensing model. Earlier, portals were licensed add-ons to Dynamics 365 apps while certain Dynamics 365 licenses included a default portal add-on. After October 1, 2019, portals are [licensed based on usage](/power-platform/admin/powerapps-flow-licensing-faq#can-you-share-more-details-regarding-the-new-power-apps-portals-licensing). All existing portals will be part of a transition period based on current customer contract after which they'll need to be converted to a new licensing model.
+One of the major changes introduced to portals after October 1, 2019 is the licensing model. Before this, portals were licensed add-ons to Dynamics 365 apps while certain Dynamics 365 licenses included a default portal add-on. As of October 1, 2019, portals are [licensed based on usage](/power-platform/admin/powerapps-flow-licensing-faq#can-you-share-more-details-regarding-the-new-power-apps-portals-licensing), or capacity. All previously existing portals must become part of a transition period based on current customer contract, after which they're required to be converted to a new licensing model.
 
-You can check the type of a portal from the [Power Apps Portals admin center](./admin/admin-overview.md):
+You can check the type of a portal from the [Power Apps portals admin center](./admin/admin-overview.md):
 
 ![Power Apps portals type](./media/power-apps-portals-type.png)
 
-Additional differences between Power Apps portals with capacity-based licenses and add-on based licenses:
+Additional differences between Power Apps portals with capacity-based licenses and add-on licenses include:
 
-- For add-on portals, the portal type has 'add-on' suffix added. For example, a production add-on portal type lists as 'Production (add-on)'.
-- Power Apps portals have a [different caching mechanism](admin/clear-server-side-cache.md) in comparison with add-on based licenses portals.
-- Provisioning method is different for portals with capacity-based licenses from add-on based licenses.
+- For add-on portals, an 'add-on' suffix is included to the portal type. For example, a production add-on portal type is listed as 'Production (add-on)'.
+- Power Apps portals have a [different caching mechanism](admin/clear-server-side-cache.md) in comparison to portals with add-on licenses.
+- The provisioning method is different for portals with capacity-based licenses than add-on licenses.
 
-You can create Power Apps portal with capacity-based license using steps described in following articles:
+You can create a Power Apps portal with a capacity-based license using the steps described in the following articles:
 
 - [Create a Dataverse starter portal](create-portal.md)
 - [Create a portal with Dynamics 365 environment](create-dynamics-portal.md)
 
-To create Power Apps portal with add-on based license, see [provisioning a portal using portal add-on](provision-portal-add-on.md).
+To create a Power Apps portal with an add-on license, see [provisioning a portal using the older portal add-on](provision-portal-add-on.md).
 
-See [Power Apps portals licensing FAQ](/power-platform/admin/powerapps-flow-licensing-faq#what-is-the-difference-between-power-apps-portals-and-dynamics-365-portals-in-terms-of-licensing) for licensing differences between add-on based licenses and capacity-based licenses.
+For more on the differences between add-on licenses and capacity-based licenses, see the [Power Apps portals licensing FAQ](/power-platform/admin/powerapps-flow-licensing-faq#what-is-the-difference-between-power-apps-portals-and-dynamics-365-portals-in-terms-of-licensing).
 
 ## Next steps
 
@@ -61,4 +61,4 @@ See [Power Apps portals licensing FAQ](/power-platform/admin/powerapps-flow-lice
 
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]