Merge branch 'master' of https://github.com/SharePoint/sp-dev-docs into shagra/docs-edit-actions

Author: shagra-ms

docs/declarative-customization/column-formatting.md

@@ -1,7 +1,7 @@
 ---
 title: Use column formatting to customize SharePoint
 description: Customize how fields in SharePoint lists and libraries are displayed by constructing a JSON object that describes the elements that are displayed when a field is included in a list view, and the styles to be applied to those elements.
-ms.date: 10/18/2021
+ms.date: 11/11/2021
 ms.localizationpriority: high
 ---
 
@@ -705,6 +705,7 @@ The following column types support column formatting:
 * Managed Metadata
 * Average Rating
 * Likes
+* Approval Status
 
 The following are currently **not** supported:
 

docs/declarative-customization/formatting-advanced.md

@@ -1,7 +1,7 @@
 ---
 title: Advanced formatting concepts
 description: Advanced formatting concepts
-ms.date: 11/12/2021
+ms.date: 11/16/2021
 ms.localizationpriority: high
 ---
 # Advanced formatting concepts
@@ -14,9 +14,21 @@ The following screenshot shows a list with a Flow button added to the Action col
 
 ![screenshot of the sample](../images/sp-columnformatting-flow.png)
 
-You can use formatting to create buttons that, when selected, run Flows on the corresponding list item.  The Flow Launch Panel will be displayed after choosing the button and the Flow will just run.
+You can use column formatting to create buttons that, when selected, run Flows on the corresponding list item.  For flows that are [solution-aware](/power-automate/overview-solution-flows), the Flow Launch Panel will be displayed after choosing the button and you must select Run Flow to start the flow. For flows that are not solution-aware, The Flow Launch Panel will be displayed after choosing the button and the Flow will just run.
 
-To use the sample below, you must substitute the ID of the Flow you want to run.  This ID is contained within the `customRowAction` attribute inside the `button` element.  To obtain a Flow's ID:
+To use the sample below, you must substitute the ID of the Flow you want to run.  This ID is contained within the `actionParams` property of the `customRowAction` attribute inside the `button` element.
+
+To obtain the ID of a flow that is solution-aware:
+
+1. Choose Flow > See your flows in the SharePoint list where the Flow is configured.
+2. If applicable, [switch to the environment](/power-platform/admin/working-with-environments#switch-the-environment) in which the Flow is hosted.
+3. Choose the Solutions area.
+4. Choose the solution in which the Flow was created.
+5. Filter for Cloud flows and select the Flow you want to run.
+6. Choose Export > Get flow identifier.
+7. Copy the ID. 
+
+To obtain the ID of a flow that is not solution-aware:
 
 1. Choose Flow > See your flows in the SharePoint list where the Flow is configured.
 2. Choose the Flow you want to run.

docs/declarative-customization/formatting-syntax-reference.md

@@ -1,7 +1,7 @@
 ---
 title: Formatting syntax reference
 description: Formatting syntax reference
-ms.date: 11/12/2021
+ms.date: 11/16/2021
 ms.localizationpriority: high
 ---
 
@@ -914,6 +914,35 @@ The following example shows how an image field can be used on a current field.
 }
 ```
 
+**Approval Status fields**
+
+The Approval Status field object has the following property (with example value):
+
+```JSON
+{
+   "displayValue": "Approved",
+}
+```
+`displayValue` is localized string of the approval status.
+
+`@currentField` or `[$__ModerationStatus]` will resolve to the internal code - 
+- 0 : Approved
+- 1 : Denied
+- 2 : Pending
+- 3 : Draft
+- 4 : Scheduled
+
+The following example shows how a approval status field might be used on a current field.
+
+```JSON
+{
+   "elmType": "div",
+   "txtContent": "@currentField.displayValue",
+   "style": {
+      "color": "=if(@currentField == 2, 'red', '')"
+   }
+}
+```
 
 ### "[$FieldName]"
 
@@ -1054,6 +1083,7 @@ The following column types can use displayValue property to get the default rend
 * Number
 * Yes/No
 * Currency
+* Approval Status
 
 ```JSON
  {

docs/general-development/save-download-and-upload-a-sharepoint-site-as-a-template.md

@@ -1,7 +1,7 @@
 ---
 title: Save, download, and upload a SharePoint site as a template
 description: Learn how to design and build robust applications by using SharePoint site templates.
-ms.date: 12/14/2020
+ms.date: 11/16/2021
 ms.prod: sharepoint
 ms.assetid: 2e637172-ddac-4a70-bd77-55a1645a3db1
 ms.localizationpriority: high
@@ -11,7 +11,7 @@ ms.localizationpriority: high
 > [!IMPORTANT]
 > The functionality of saving a site as a template described in this article is **only supported** in SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019 **(classic sites only)**, and SharePoint Online **(classic sites only)**.
 >
-> It is **not supported** in SharePoint Online **(modern sites)** or SharePoint Server 2019 **(modern sites)**.
+> It is **not supported** in SharePoint Online **(modern sites)** or SharePoint Server 2019 **(modern sites)**. SharePoint Online environments should use the [new Site Templates](/sharepoint/dev/declarative-customization/site-design-overview). 
 
 Learn how to design and build robust applications by using SharePoint site templates.
 

docs/spfx/compatibility.md

@@ -34,7 +34,7 @@ The following table lists SharePoint Framework and compatible versions of common
 
 |              SPFx               |         Node.js          |                    NPM                    |   TypeScript   |    React    |
 | ------------------------------- | ------------------------ | ----------------------------------------- | -------------- | ----------- |
-| [1.13.0](release-1.13.md)       | LTS v10,LTS v12, LTS v14 | v5, v6                                    | v3.9           | v16.13.1    |
+| [1.13.0](release-1.13.md)       | LTS v12, LTS v14         | v5, v6                                    | v3.9           | v16.13.1    |
 | [1.12.1](release-1.12.1.md)     | LTS v10,LTS v12, LTS v14 | v5, v6                                    | v3.7           | v16.9.0     |
 | ~~[1.12.0](release-1.12.0.md)~~ | ~~LTS v12, LTS v10~~     | ~~v5, v6~~                                | ~~v3.7~~       | ~~v16.9.0~~ |
 | [1.11.0](release-1.11.0.md)     | LTS v10                  | v5, v6                                    | v3.3           | v16.8.5     |

docs/spfx/debug-modern-pages.md

@@ -1,7 +1,7 @@
 ---
 title: Debug SharePoint Framework solutions on modern SharePoint pages
 description: Guidance on how to debug SharePoint Framework solutions on modern SharePoint pages
-ms.date: 10/21/2020
+ms.date: 11/16/2020
 ms.prod: sharepoint
 ms.localizationpriority: high
 ---
@@ -96,7 +96,7 @@ To debug an Application Customizer, add the following to the URL of your modern
 > Line breaks & indentation have been added to the following snippet for readability. The following text should be on a single line with no whitespace.
 
 ```json
-`?loadSPFX=true
+?loadSPFX=true
 &debugManifestsFile=https://localhost:4321/temp/manifests.js
 &customActions={"<extensionId>":{
     "___location":"<extensionType>",
@@ -131,9 +131,9 @@ The `customActions` parameter has the following tokens that should be replaced:
 
 | Token              | Description                                                                                                                                                                             |
 |--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `<extensionId>`    | Use the GUID of the extension as the key to associate with the custom action. This has to match the ID value of your extension, which is available in the extension manifest.json file. |
+| `<extensionId>`    | Use the GUID of the extension as the key to associate with the custom action. This has to match the ID value of your extension, which is available in the extension **manifest.json** file. |
 | `<extensionType>`  | The type of custom action. Use `ClientSideExtension.ApplicationCustomizer` for the Application Customizer extension.                                                                    |
-| `<propertiesJSON>` | An optional JSON object that contains properties that are available via the this.properties member                                                                                      |
+| `<propertiesJSON>` | An optional JSON object that contains properties that are available via the `this.properties` member.                                                                                      |
 
 With the parameters added to the URL, reload the page in the web browser. The page will show a popup asking you to confirm that you now will be loading debug scripts.
 
@@ -180,7 +180,7 @@ Following are the query string parameters that you need to add:
 |---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 |`loadSPFX=true`      |Ensures that the SharePoint Framework is loaded on the page. For performance reasons, the framework doesn't load unless at least one extension is registered. Because no components are registered, you must explicitly load the framework.                                                                                                                    |
 |`debugManifestsFile` |Specifies that you want to load components that are locally served. The loader only looks for components in the app catalog (for your deployed solution) and the SharePoint manifest server (for the system libraries).                                                                                                                                    |
-|`fieldCustomizers`   |indicates which fields in your list should have their rendering controlled by the Field Customizer. The ID parameter specifies the GUID of the extension that should be used to control the rendering of the field. The properties parameter is an optional text string containing a JSON object that is deserialized into `this.properties` for your extension.|
+|`fieldCustomizers`   |Indicates which fields in your list should have their rendering controlled by the Field Customizer. The ID parameter specifies the GUID of the extension that should be used to control the rendering of the field. The properties parameter is an optional text string containing a JSON object that is deserialized into `this.properties` for your extension.|
 
 The `fieldCustomizers` parameter has the following tokens that should be replaced:
 
@@ -204,7 +204,7 @@ To debug a list view command set, add the following to the URL of your modern pa
 > Line breaks & indentation have been added to the following snippet for readability. The following text should be on a single line with no whitespace.
 
 ```json
-?loadSpfx=true
+?loadSPFX=true
 &debugManifestsFile=https://localhost:4321/temp/manifests.js
 &customActions={"<extensionId>":{
   "___location":"<extensionType>",
@@ -216,7 +216,7 @@ For example:
 
 ```text
 https://contoso.sharepoint.com/sites/team-a/Lists/Orders/AllItems.aspx
-  ?loadSpfx=true
+  ?loadSPFX=true
   &debugManifestsFile=https://localhost:4321/temp/manifests.js
   &customActions={"a8047e2f-30d5-40fc-b880-b2890c7c16d6":{
     "___location":"ClientSideExtension.ListViewCommandSet.CommandBar",
@@ -233,15 +233,15 @@ Following are the query string parameters that you need to add:
 | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `loadSPFX=true`      | Ensures that the SharePoint Framework is loaded on the page. For performance reasons, the framework doesn't load unless at least one extension is registered. Because no components are registered, you must explicitly load the framework. |
 | `debugManifestsFile` | Specifies that you want to load components that are locally served. The loader only looks for components in the app catalog (for your deployed solution) and the SharePoint manifest server (for the system libraries).                 |
-| `customActions`      | simulates a custom action. You can set many properties on this CustomAction object that affect the look, feel, and ___location of your button; we’ll cover them all later.                                                                      |
+| `customActions`      | Simulates a custom action. You can set many properties on this CustomAction object that affect the look, feel, and ___location of your button; we'll cover them all later.                                                                      |
 
 The `customActions` parameter has the following tokens that should be replaced:
 
 | Token              | Description                                                                                                                                                                                                                                                                                                                                                                                                                 |
 |--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `<extensionId>`    | GUID of the extension.                                                                                                                                                                                                                                                                                                                                                                                                      |
 | `<extensionType>`  | Where the commands are displayed. The possible values are:<br/> `ClientSideExtension.ListViewCommandSet.ContextMenu`: The context menu of the item(s),<br/> `ClientSideExtension.ListViewCommandSet.CommandBar`: The top command set menu in a list or library.<br/> `ClientSideExtension.ListViewCommandSet`: Both the context menu and the command bar (corresponds to `SPUserCustomAction.Location="CommandUI.Ribbon"`). |
-| `<propertiesJSON>` | An optional JSON object containing properties that are available via the this.properties member.                                                                                                                                                                                                                                                                                                                            |
+| `<propertiesJSON>` | An optional JSON object containing properties that are available via the `this.properties` member.                                                                                                                                                                                                                                                                                                                            |
 
 With the parameters added to the URL, reload the page in the web browser. The page will show a popup asking you to confirm that you now will be loading debug scripts.
 
@@ -298,7 +298,7 @@ Using the SharePoint workbench, you can only test web parts from your solution.
 
 ## Debug SharePoint Framework web parts - an alternative approach
 
-If you build your web part solution without the **--ship** argument as following
+If you build your web part solution without the **--ship** argument as following:
 
 ```console
 gulp bundle
@@ -307,13 +307,13 @@ gulp package-solution
 
 the packages generated will reference the code from your local computer (https://localhost:4321). You can deploy the solution to the app catalog as you normally would.
 
-You can then start your local server  by running
+You can then start your local server  by running:
 
 ```console
 gulp serve --nobrowser
 ```
 
-Now you can go back to a SharePoint site where the solution has been deployed and add the web parts to any page, modern or classic, and the web part code will be loaded from your local development environment. You can debug your web parts just as you would if you ran 'gulp serve' and added your web part to the workbench.
+Now you can go back to a SharePoint site where the solution has been deployed and add the web parts to any page, modern or classic, and the web part code will be loaded from your local development environment. You can debug your web parts just as you would if you ran **gulp serve** and added your web part to the workbench.
 
 This approach should only be used when you're in development mode. If you deploy an app to the app catalog that points to your local host, it will fail to run if your development environment isn't running.
 

docs/spfx/supported-extensibility-platforms-overview.md

@@ -1,7 +1,7 @@
 ---
 title: Supported extensibility platforms - overview
 description: Learn what platforms support customizations and rely on the SharePoint Framework for their extensibility opportunities available to developers.
-ms.date: 09/08/2021
+ms.date: 11/16/2021
 ms.prod: sharepoint
 ms.localizationpriority: high
 ---
@@ -41,6 +41,6 @@ Learn more about using SPFx for Microsoft Teams: [SPFx support for Microsoft Tea
 
 ## Microsoft Viva Connections
 
-Microsoft Viva Connections, your gateway to modern engagement experiences is designed to keep everyone in your organization engaged and informed. Viva Connections entirely relies on SharePoint for it's customization and extensibility story. This includes both the Viva Connections desktop and mobile experiences. Both of these experiences rely on the SPFx for all customizations.
+Microsoft Viva Connections, your gateway to modern engagement experiences is designed to keep everyone in your organization engaged and informed. Viva Connections entirely relies on SharePoint for its customization and extensibility story. This includes both the Viva Connections desktop and mobile experiences. Both of these experiences rely on the SPFx for all customizations.
 
 Learn more about using SPFx on Viva Connections: [SPFx support for Viva Connections](viva/overview-viva-connections.md).