Live publish

buck1ey · web-flow · commit 4cb8958ba30a · 2021-12-15T11:00:03.000-08:00
diff --git a/powerapps-docs/maker/data-platform/data-platform-restricted-entities.md b/powerapps-docs/maker/data-platform/data-platform-restricted-entities.md
@@ -29,14 +29,15 @@ Tables may be restricted to a Dynamics 365 app license for the following reasons
 If an app or flow only reads information from a table, a Dynamics 365 app license is not required and an appropriate Power Apps or Power Automate license is all that's needed.
 
 ## Restricted tables for create, update, and delete operations
+
 The following table lists the restricted tables and the associated Dynamics 365 license requirements for users who create, update, or delete data stored within these tables. 
 
 |Table  |Logical name  |License required  |
 |---------|---------|---------|
 Actual |msdyn_actual |Dynamics 365 for Field Service <br> **or** Dynamics 365 for Project Service Automation<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
-Agreement Business Process |msdyn_bpf_baa0a411a239410cb8bded8b5fdd88e3 |Dynamics 365 for Field Service<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
+Agreement Business Process |msdyn_bpf_baa0a411a239410cb8bded8b5fdd88e3 |Dynamics 365 for Field Service<br> **or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
 Booking journal | msdyn_bookingjournal|Dynamics 365 for Field Service<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
-Booking Setup Metadata | msdyn_bookingsetupmetadata|Dynamics 365 for Field Service <br> **or** Dynamics 365 for Project Service Automation<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
+Booking Setup Metadata | msdyn_bookingsetupmetadata|Dynamics 365 for Field Service <br> **or** Dynamics 365 for Project Service Automation<br>**or** Dynamics 365 for Customer Service Enterprise edition <br> **or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
 Booking timestamp | msdyn_bookingtimestamp|Dynamics 365 for Field Service<br> **or** Dynamics 365 Customer Engagement plan<br> **or** Dynamics 365 plan
 Case<sup>1</sup> | incident | Dynamics 365 for Customer Service Professional edition <br>**or** Dynamics 365 for Customer Service Enterprise edition <br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
 Case to Work Order Business Process |msdyn_bpf_989e9b1857e24af18787d5143b67523b |Dynamics 365 for Field Service<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
diff --git a/powerapps-docs/maker/data-platform/solutions-overview.md b/powerapps-docs/maker/data-platform/solutions-overview.md
@@ -139,6 +139,9 @@ The following limitations apply to the use of canvas apps, flows, and custom con
 - Flows in solutions don't support delegated authentication. For example, access to a flow is not automatically granted based on having access to the SharePoint list the flow was created from.
 - Custom connectors created outside solutions cannot be added to solutions at this time.
 - Canvas apps shared with 'Everyone' that go through environment backup and environment restore operations aren't shared with 'Everyone' in the restored environment. Notice that, the canvas app can be shared with a security group and the app in the restored environment will be shared with that security group.  
+- Flows using [connectors](/connectors/connector-reference/) that are 'indexed' cannot be added into solutions. Indexing enables the quick retrieval of those flows to display in a menu or list. Indexed connectors include Power Automate instant (button) flows, Power Apps, Teams, SharePoint, Dynamics 365 Customer Voice, Microsoft Forms, legacy Dataverse connector, Dynamics 365, Excel Online, Microsoft Project, Azure IOT Central V2, and Project Online. To work around this behavior choose one of two options: 
+   - Create a new flow in a solution. 
+   - Change the flow to remove the indexed connector usage, add it into a solution, and then change it back.
 
 For details about customizing the individual components in a solution, see the following topics:  
   
diff --git a/powerapps-docs/maker/model-driven-apps/app-designer-overview.md b/powerapps-docs/maker/model-driven-apps/app-designer-overview.md
@@ -69,6 +69,7 @@ From the **Navigation** pane, select **Navigation bar** to set the following opt
 1. **Show Recent**. Enabled by default. When selected, displays the recently viewed pages link. Selecting the link displays all recently viewed pages.
 1. **Show Pinned**. Enabled by default. When selected, displays the pages that have been pinned. App users select the push-pin icon next to a record listed under **Recent** to add it to their pinned rows.
 1. **Enable collapsible groups**. Disabled by default. When selected, subareas displayed under groups in the site map can be expanded or collapsed.
+1. **Enable Areas**. Disabled by default. When selected, new areas can be added to the app. For apps with existing multiple areas, this setting is enabled by default. You can't disable this setting while the app has multiple areas.
 
    :::image type="content" source="media/navigation-pane-options.png" alt-text="Options available for app navigation":::
 
@@ -78,7 +79,6 @@ From the **Navigation** pane, select **Navigation bar** to set the following opt
    - URLs
    - Business process flows
    - Charts
-- You can’t add more than one area to the app’s navigation.
 - You can’t change the app’s icon.
 - You can’t specify the app’s URL.
 
diff --git a/powerapps-docs/maker/model-driven-apps/app-navigation.md b/powerapps-docs/maker/model-driven-apps/app-navigation.md
@@ -32,6 +32,28 @@ In a model-driven app, there are the three main app runtime navigation component
 
 By default, a new model-driven app's navigation includes one area named **Area1**, one group named **Group1**, and one subarea named **Subarea1**. You can change the default area, group, and subarea names to something that is more meaningful to your users or configure a different site map.
 
+## Create an area
+
+By default, the ability to create additional areas is disabled. Areas are enabled by default for apps with existing multiple areas.
+
+### Enable areas
+
+1. On the left navigation pane, select **Navigation**.
+1. Select **Navigation bar**, to display the navigation properties on the right pane.
+1. On the right navigation bar properties pane, select **Enable Areas**.
+
+### Add a new area
+
+1. On the left navigation pane, select **Navigation**.
+1. Select **Add**, and then select **Area**.
+1. Complete the properties pane for the area:
+
+   - **Title**: Enter a title used to describe the area.
+   - **ID**: The system generates an identifier for the area. Accept the system generated ID or enter a new one.
+
+1. To save your app navigation changes select **Save**.
+1. To publish the changes and make them available to other users, select **Publish**.
+
 ## Create a group
 
 To create a new group, complete the following steps:
@@ -43,6 +65,10 @@ To create a new group, complete the following steps:
 
    - **Title**: Enter a title used to describe the group.
    - **ID**: The system generates an identifier for the group. Accept the system generated ID or enter a new one.
+   - **Localized titles**: Add localized titles for the group title. More information: [Translate localizable text for model-driven apps](translate-localizable-text.md)
+
+1. To save your app navigation changes select **Save**.
+1. To publish the changes and make them available to other users, select **Publish**.
 
 ## Create a subarea
 
@@ -51,16 +77,19 @@ To create a new subarea, complete the following steps:
 1. On the left navigation pane, select **Navigation**.
 1. Select **Add**, and then select  **Subarea**.
   
-1. Complete the **New subarea** dialog.
+1. Complete the **New subarea** pane.
   
    - **Content type**: Select either **Table** or **Dashboard**.
    - **Table** or **Dashboard**: Depending on the content type you selected, select a table or dashboard from the list.
    - **Title**: Leave the default title or enter a title used to describe the subarea.
+   - **Icon**: Icons appear to the left of the subarea title. To add an icon, select **No icon** to browse and select an existing web resource or select **New** to create one. More information: [Create or edit model-driven app web resources to extend an app](create-edit-web-resources.md)
+   - **ID**: The system generates an identifier for the subarea. Accept the system generated ID or enter a new one.
+   - **Localized titles**: Add localized titles for the subarea title. More information: [Translate localizable text for model-driven apps](translate-localizable-text.md)
 
 1. To save your app navigation changes select **Save**.
 1. To publish the changes and make them available to other users, select **Publish**.
 
-## Remove a group or subarea
+## Remove a group, subarea, or area
 
 1. On the left navigation pane, select **Navigation**.
 1. Select the group or subarea you want, select the ellipses (**...**) and then select **Remove**.
diff --git a/powerapps-docs/maker/model-driven-apps/create-model-driven-app.md b/powerapps-docs/maker/model-driven-apps/create-model-driven-app.md
@@ -110,8 +110,8 @@ Comments are commonly questions, feedback, or ideas that are important context t
 
 ## Next steps
 
+- [Add areas, groups, and subareas for app navigation](app-navigation.md)
 - [Create, add and remove forms, views or dashboards](create-add-remove-forms-views-dashboards.md)
 - [Create and remove pages](create-remove-pages.md)
-- [Overview of the model-driven app designer](app-designer-overview.md)
 - [Configure app properties (Preview)](app-properties.md)
 - [Configure app properties](manage-app-properties.md)
diff --git a/powerapps-docs/maker/model-driven-apps/media/create-app.png b/powerapps-docs/maker/model-driven-apps/media/create-app.png
diff --git a/powerapps-docs/maker/model-driven-apps/media/navigation-pane-options.png b/powerapps-docs/maker/model-driven-apps/media/navigation-pane-options.png
diff --git a/powerapps-docs/maker/model-driven-apps/monitor-form-checker.md b/powerapps-docs/maker/model-driven-apps/monitor-form-checker.md
@@ -34,14 +34,29 @@ There are many situations where Monitor can help makers understand why a form be
 
 Follow the instructions below to understand the behavior of your model-driven app forms.
 
+### Step 1: Create a Monitor session
+
+There are two ways to open a Monitor session. 
+
+**Option 1:**
+
 1. Sign in to [Power Apps](https://make.powerapps.com/), select **Apps**.
-1. The model-driven app required.
-1. To create a monitoring session, select **...** next to the model-driven app or on the global command bar, and then select **Monitor**.
+1. Select **...** next to the model-driven app or on the global command bar, and then select **Monitor**.
 
    :::image type="content" source="media/create-monitor-session.png" alt-text="Sample model-driven app":::
 
 1. Follow the instructions on your screen to run the app and join the monitoring session.
 
+**Option 2:**
+
+1. Play your model-driven app.
+2. Add `&monitor=true` to the end of the URL in your web browser, and then refresh the page.
+3. Select **Monitor** on the command bar.
+
+    > ![Location of Monitor button in global command bar](https://user-images.githubusercontent.com/69216748/146047014-b9428da5-138a-4ccf-b74c-b45a0a0685b9.png)
+
+### Step 2: Connect your app to the Monitor session
+
 1. Once in the monitor, select **Play model-driven app** from the menu on the command bar. This opens the app and begins the monitoring.
 1. Perform actions within the model-driven app consistent with normal use of the app. For example, open and change data using a table form.
 1. On the browser window running Monitor, select the **Category** column, and then select **Filter by**.
@@ -100,4 +115,4 @@ For more information about how to troubleshoot issues with forms in a model-driv
 
 [Learn about Monitor as a Power Apps tool](../../maker/monitor-overview.md)
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]
diff --git a/powerapps-docs/maker/model-driven-apps/rich-text-editor-control.md b/powerapps-docs/maker/model-driven-apps/rich-text-editor-control.md
@@ -45,7 +45,7 @@ For a full list of default options, see [Use the rich text editor toolbar](#use-
 
 You can create a new text column and configure the control, or replace an existing text column. The rich text editor control can be used with single or multi-line text columns.
 
-1. Sign in to Power Apps. Go to **Solutions**, open the solution that you want, open the table that you want, and then select the **Forms** tab.
+1. Sign in to [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc). On the left navigation pane, select **Solutions**, open the solution that you want, open the table that you want, and then select the **Forms** tab.
 2. Select the form, and then select **Edit form**.
 3. In the form designer on the command bar, select **Switch to classic**.
 4. On the legacy form designer canvas, add or create a text column or select an existing text column, such as the account table **Description** column. On the **Home** tab, select **Change Properties**.
