Sample adjustments
This commit is contained in:
Vesa Juvonen
parent
7c272c561c
commit
fb66482027
|
|
@ -1,29 +0,0 @@
|
|||
{
|
||||
// Use IntelliSense to learn about possible Node.js debug attributes.
|
||||
// Hover to view descriptions of existing attributes.
|
||||
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
|
||||
"version": "0.2.0",
|
||||
"configurations": [
|
||||
{
|
||||
"type": "node",
|
||||
"request": "launch",
|
||||
"name": "Launch Program",
|
||||
"program": "${workspaceRoot}/app.js"
|
||||
},
|
||||
{
|
||||
"type": "node",
|
||||
"request": "launch",
|
||||
"name": "Launch Program",
|
||||
"program": "${file}",
|
||||
"outFiles": []
|
||||
},
|
||||
{
|
||||
"type": "node",
|
||||
"request": "attach",
|
||||
"name": "Attach to Process",
|
||||
"address": "localhost",
|
||||
"port": 5858,
|
||||
"outFiles": []
|
||||
}
|
||||
]
|
||||
}
|
||||
|
|
@ -150,4 +150,4 @@ In the PropertyPane, an administrator just needs to specify which Managed Proper
|
|||
|
||||
If desired, the admin can also specify which site templates should be included in the menu, as wall as any additional filters. Additional Filteres can be specified in the format 'ManagedPropertyName=value';
|
||||
|
||||
<img src="https://telemetry.sharepointpnp.com/sp-dev-fx-webparts/samples/readme-template" />
|
||||
<img src="https://telemetry.sharepointpnp.com/sp-dev-fx-webparts/samples/react-property-bag-editor" />
|
||||
|
|
@ -1,133 +0,0 @@
|
|||
## react-property-bag-editor
|
||||
|
||||
This project consists of four webparts that can be used to manage the Property Bags for SharePoint sites and display navigational components from those Properties.
|
||||
|
||||
PropertyBagEditor.
|
||||
|
||||
This webpart allows an administrator to edit selected items in a site's Property Bag. A sample display is shown below:
|
||||
|
||||
|
||||
Selecting a Property and clicking the Edit button will bring up the Edit Panel:
|
||||
|
||||
|
||||
|
||||
Here you can change the value of the property and specify if the property should be included in the search Index.
|
||||
|
||||
The Properties that can be edited are specified in the webpart's Property Pane:
|
||||
|
||||
|
||||
|
||||
The Properties set in the Property Pane of this webpart are crawled properties, and should be mapped to managed properties so that can be used by the other webparts in this project.
|
||||
|
||||
The Site whose properties are to be edited can be passed in via a query parameter. While this webpart can be added to any page, it would be most useful if added to a page in an infrastructure site collection in the tenant, and then linked to from all other sites via a link in the Site Settings page.
|
||||
|
||||
The following script shows how to add such a link to all sites 'Site Settings' page using PNP Powershell. It will add a menu item named 'Edit Site Metadata ' to the Site Settings of each Team Site that links to the PropertBagEdcitor.aspx page on the tenants infrastructure site (this site is named 'cdn' in the example below).
|
||||
|
||||
$adminSiteUrl="https://tenant-admin.sharepoint.com"
|
||||
|
||||
$customActionDescription="CUSTOM_\ ___Navigation__ \__Metadata"
|
||||
|
||||
$pageUrl="https://tenant.sharepoint.com/sites/cdn/SitePages/PropertBagEdcitor.aspx?siteUrl={0}"
|
||||
|
||||
$credentials=get-credential
|
||||
|
||||
Connect-SPOnline -Url $adminSiteUrl -Credentials $credentials
|
||||
|
||||
$ctx = Get-SPOContext
|
||||
|
||||
$sites = Get-SPOTenantSite -Detailed
|
||||
|
||||
foreach($site in $sites){
|
||||
|
||||
if ($site.Template -eq "STS#0") {
|
||||
|
||||
Connect-SPOnline –Url $site.Url –Credentials $credentials
|
||||
|
||||
$existing = Get-SPOCustomAction -Scope "Site" | ? { $\_.Description -eq $customActionDescription }
|
||||
|
||||
if ($existing) {
|
||||
|
||||
$existing.DeleteObject();
|
||||
|
||||
Execute-SPOQuery;
|
||||
|
||||
Write-Host "Deleteting existing action from"$site.Url
|
||||
|
||||
}
|
||||
|
||||
Write-Host "adding action to" $site.Url
|
||||
|
||||
Add-SPOCustomAction -Description $customActionDescription -Location "Microsoft.SharePoint.SiteSettings" -name "Edit Site Metadata"-Title "Edit Site Metadata" -Group "SiteAdministration" -Sequence 10100 -Url ( [string]::Format($pageUrl,$site.Url)) -Scope "Site"
|
||||
|
||||
Execute-SPOQuery
|
||||
|
||||
}
|
||||
|
||||
}
|
||||
|
||||
PropertyBagDisplay
|
||||
|
||||
The propertyBagDisplay webpart can be used by an administrator to view and edit selected properties across sites in the tenant:
|
||||
|
||||
|
||||
|
||||
In the Property Pane, an administrator must specify both the Crawled Property Name and the Managed Property name (separated by a pipe character) of the properties to be included in the webpart:
|
||||
|
||||
|
||||
|
||||
The administrator can also include a list of site templates to narrow down the list of sites to be included in the webpart. When specifying site templates to include you can include just the Site Template Name (STS) and all sites within that template name will be included, or you can specify the Site Template Name and ID, separated by a '#" character (STS#1) to have only sites with that template name and ID included.
|
||||
|
||||
The webpart displays the site template, Title and Url, plus the selected Managed Properties for all sites in the tenant with the selected site template. The Managed Properties are only displayed if they have been set as searchable, and a full crawl has been run. After selecting a Site, a user can click the edit button to edit the Crawled properties (i.e. the raw property bag values) for the selected site:
|
||||
|
||||
|
||||
|
||||
On the edit panel one can specify a new value for each property as well as whether that property is to be included in the search index. Additionally one can specify that a full crawl of the site should be run once the properties are saved.
|
||||
|
||||
PropertyBagFilteredSiteList
|
||||
|
||||
This webpart displays a list of all sites that meet the criteria specified in the property pane by the administrator:
|
||||
|
||||
|
||||
|
||||
Additionally, it lets the user narrow down the list of sites displayed by applying metadata filters that are set up by the administrator in the Property Pane( Businsess Unit and Continent in the example above):
|
||||
|
||||
|
||||
|
||||
In the PropertyPane above, the 'Site Templates to Include' and 'Metadata Filters' are used to filter which site collections are retrieved from search. The 'User Filters' are used to allow the user to easily filter the results returned from search using the command bar on the top of the display.
|
||||
|
||||
|
||||
|
||||
PropertyBagGlobalNav
|
||||
|
||||
This Webpart builds a navigation menu based on the Managed Properties set up in the PropertyPane:
|
||||
|
||||
|
||||
|
||||
In the PropertyPane, an administrator just needs to specify which Managed Properties are to be used to build the Navigation menu:
|
||||
|
||||
|
||||
|
||||
If desired, the admin can also specify which site templates should be included in the menu, as wall as any additional filters. Additional Filteres can be specified in the format 'ManagedPropertyName=value';
|
||||
|
||||
### Building the code
|
||||
|
||||
```bash
|
||||
git clone the repo
|
||||
npm i
|
||||
npm i -g gulp
|
||||
gulp
|
||||
```
|
||||
|
||||
This package produces the following:
|
||||
|
||||
* lib/* commonjs components - this allows this package to be reused from other packages.
|
||||
* dist/* - a single bundle containing the components used for uploading to a cdn pointing a registered Sharepoint webpart library to.
|
||||
* example/* a test page that hosts all components in this package.
|
||||
|
||||
### Build options
|
||||
|
||||
gulp clean - TODO
|
||||
gulp test - TODO
|
||||
gulp watch - TODO
|
||||
gulp build - TODO
|
||||
gulp deploy - TODO
|
||||
|
|
@ -106,5 +106,5 @@ PropertyPaneTaxonomyPicker("Language", {
|
|||
- **SharePoint Framework Web Part (SPFx)**
|
||||
|
||||
|
||||
<img src="https://telemetry.sharepointpnp.com/sp-dev-fx-webparts/samples/spfx-react-taxonomypicker" />
|
||||
<img src="https://telemetry.sharepointpnp.com/sp-dev-fx-webparts/samples/react-taxonomypicker" />
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue