Skip to content

Commit d5cdb96

Browse files
ymyqweMingyuan Yu
andauthored
update docs to modern app catalog (SharePoint#8898)
Co-authored-by: Mingyuan Yu <[email protected]>
1 parent 6d92b24 commit d5cdb96

File tree

4 files changed

+6
-6
lines changed

4 files changed

+6
-6
lines changed

docs/images/spfx-add-to-all-sites.png

33 KB
Loading

docs/images/spfx-add-to-teams.png

34.3 KB
Loading

docs/spfx/deployment-spfx-teams-solutions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,9 @@ SharePoint Online supports two options for deploying SPFx solutions to the Micro
2020

2121
This capability is ideal when you have a simple implementation to expose automatically in Microsoft Teams.
2222

23-
In this scenario, when an SPFx solution is uploaded to the SharePoint Online tenant app catalog, if the solution contains components for Microsoft Teams, the **Sync to Teams** button in the ribbon is enabled.
23+
In this scenario, when an SPFx solution is uploaded to the SharePoint Online tenant app catalog, if the solution contains components for Microsoft Teams, the **Add to Teams** button in the ribbon is enabled.
2424

25-
:::image type="content" source="../images/sp-teams-sync-to-teams-button.png" alt-text="Sync to Teams":::
25+
:::image type="content" source="../images/spfx-add-to-teams.png" alt-text="Add to Teams":::
2626

2727
This button will start the following process in SharePoint Online:
2828

docs/spfx/tenant-scoped-deployment.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -70,14 +70,14 @@ In following example configuration, `skipFeatureDeployment` is set to `true`, wh
7070

7171
When the solution with the `skipFeatureDeployment` attribute set to `true` is deployed to the tenant app catalog, the administrator is given an option to configure the solution to be deployed centrally across the tenant.
7272

73-
By default, the **Make this solution available to all sites in the organization** check box isn't selected. If the check box is selected by the administrator, components in the solutions are automatically visible and available across the tenant.
73+
By default, the **Enable this app and add it to all sites** check box is selected and components in the solutions are automatically visible and available across the tenant.
7474

75-
![The "Make this solution available to all sites in the organization" setting is visible when solution is deployed to app catalog](../images/tenant-deploy-app-catalog.png)
75+
![The "Enable this app and add it to all sites" setting is visible when solution is deployed to app catalog](../images/spfx-add-to-all-sites.png)
7676

7777
Notice that because the solution and site-specific upgrade actions are only available when you use the feature framework, there's no specific upgrade option for the centrally deployed solutions. These solutions can be updated by updating the solution-specific assets in the CDN and by updating and deploying the package in the app catalog. This automatically updates all existing component instances across the tenant to use the latest component assets, such as JavaScript files and updated CSS files.
7878

7979
> [!WARNING]
80-
> For solution packages containing site extension(s), selecting the **Make this solution available to all sites in the organization** check box is only required to activate the site extension(s) initially. When updating existing solution packages, selecting the check box during deployment may create duplicate entries in the **Tenant Wide Extension** list.
80+
> For solution packages containing site extension(s), selecting the **Enable this app and add it to all sites** check box is only required to activate the site extension(s) initially. When updating existing solution packages, selecting the check box during deployment may create duplicate entries in the **Tenant Wide Extension** list.
8181
8282
## Client-side web part visibility on SharePoint sites
8383

@@ -87,7 +87,7 @@ Web parts included in solutions that have been centrally deployed are immediatel
8787

8888
[SharePoint Framework Extensions](./extensions/overview-extensions.md) are immediately available to be used on SharePoint sites. This means that they can be associated with `ClientSideComponentId` properties in the specific SharePoint elements, such as **fields** and **user custom actions**.
8989

90-
Additionally, if an administrator selects the **Make this solution available to all sites in the organization** checkbox during deployment, automations in the solution package may create entries in the **Tenant Wide Extensions** list on the app catalog. Entries in this list manage tenant-wide activation of site extensions. The automations are described by the **ClientSideInstance.xml** file as referenced in **./config/package-solution.json**.
90+
Additionally, if an administrator selects the **Enable this app and add it to all sites** checkbox during deployment, automations in the solution package may create entries in the **Tenant Wide Extensions** list on the app catalog. Entries in this list manage tenant-wide activation of site extensions. The automations are described by the **ClientSideInstance.xml** file as referenced in **./config/package-solution.json**.
9191

9292
For more information, see [Tenant Wide Deployment of SharePoint Framework Extensions](./extensions/basics/tenant-wide-deployment-extensions.md).
9393

0 commit comments

Comments
 (0)