Skip to content

Commit 2758acd

Browse files
jansenbejansenbe
committed
Updates
1 parent fba5bdb commit 2758acd

9 files changed

+62
-13
lines changed

‎docs/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1375,6 +1375,8 @@
13751375
href: transform/modernize-userinterface-site-pages-dotnet.md
13761376
- name: Page transformation configuration options
13771377
href: transform/modernize-userinterface-site-pages-configuration.md
1378+
- name: Page transformation security
1379+
href: transform/modernize-userinterface-site-pages-security.md
13781380
- name: Page transformation model
13791381
href: transform/modernize-userinterface-site-pages-model.md
13801382
- name: Page transformation Functions and Selectors

‎docs/transform/modernize-userinterface-site-pages-configuration.md

Lines changed: 17 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Options to control the page transformation process
33
description: Explains how to configure the page transformation process
4-
ms.date: 09/25/2018
4+
ms.date: 01/30/2019
55
ms.prod: sharepoint
66
localization_priority: Normal
77
---
@@ -11,7 +11,7 @@ localization_priority: Normal
1111
When you use the page transformation framework you do have a lot of control on how the page transformation is done. The model to control this is by specifying the correct configuration as part of the `PageTransformationInformation` instance that you use to launch page transformation. In this article you'll learn more about the available options.
1212

1313
> [!IMPORTANT]
14-
> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [PnP Tools GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
14+
> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [sp-dev-modernization GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
1515
1616
## Overwrite option
1717

@@ -125,6 +125,21 @@ PageTransformationInformation pti = new PageTransformationInformation(page)
125125
};
126126
```
127127

128+
## CopyPageMetadata option (as of February 2019 release)
129+
130+
Type | Default value if not specified
131+
-----|----
132+
Bool | false
133+
134+
If you've extended your wiki page library with additional columns to collect page metadata and you want to copy this metadata to the created modern client side page then set this option to true
135+
136+
```Csharp
137+
PageTransformationInformation pti = new PageTransformationInformation(page)
138+
{
139+
CopyPageMetadata = true,
140+
};
141+
```
142+
128143
## HandleWikiImagesAndVideos option
129144

130145
Type | Default value if not specified

‎docs/transform/modernize-userinterface-site-pages-dotnet.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
---
22
title: Transform classic pages to modern client-side pages using .Net
33
description: Explains how to transform classic wiki and web part pages into modern client side pages using the SharePoint .Net
4-
ms.date: 11/19/2018
4+
ms.date: 01/30/2019
55
ms.prod: sharepoint
66
localization_priority: Normal
77
---
88

99
# Transforming to modern site pages using .Net
1010

1111
> [!IMPORTANT]
12-
> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [PnP Tools GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
12+
> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [sp-dev-modernization GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
1313
1414
The page transformation engine is built using .Net and is distributed as a [nuget](https://www.nuget.org/packages/SharePointPnPModernizationOnline) package. Once you've added the nuget package you'll see that 2 additional files are added to your solution:
1515

‎docs/transform/modernize-userinterface-site-pages-model.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Understanding and configuring the page transformation model
33
description: Provides detailed guidance on how to configure and use the page transformation model
4-
ms.date: 05/16/2018
4+
ms.date: 01/30/2019
55
ms.prod: sharepoint
66
localization_priority: Normal
77
---
@@ -11,7 +11,7 @@ localization_priority: Normal
1111
The heart of the page transformation solution is the model that feeds the transformation: the model tells the engine which web part properties are important, allows you to manipulate these properties and dynamically choose a mapping for your web part.The page transformation model is expressed in XMl and comes with a schema that's used to validate the correctness of the model.
1212

1313
> [!IMPORTANT]
14-
> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [PnP Tools GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
14+
> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [sp-dev-modernization GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
1515
1616
## Page transformation high level architecture
1717

‎docs/transform/modernize-userinterface-site-pages-powershell.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
---
22
title: Transform classic pages to modern client-side pages using PowerShell
33
description: Explains how to transform classic wiki and web part pages into modern client side pages using the SharePoint PowerShell
4-
ms.date: 11/19/2018
4+
ms.date: 01/30/2019
55
ms.prod: sharepoint
66
localization_priority: Priority
77
---
88

99
# Transforming to modern site pages using PowerShell
1010

1111
> [!IMPORTANT]
12-
> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [PnP Tools GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
12+
> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [sp-dev-modernization GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
1313
1414
The page transformation engine can also be used from PowerShell. This allows it to be integrated in a site modernization script that besides page transformation also does other things like installing solution, connecting the site to an Office 365 group and applying tenant branding. A good example of an all-up modernization script can be found [in the Office 365 Group connect article](modernize-connect-to-office365-group.md).
1515

@@ -30,6 +30,8 @@ Overwrite | $false | When you add `-Overwrite` then the page transformation fram
3030
AddPageAcceptBanner | $false | Using `-AddPageAcceptBanner` will make the page transformation framework put the configured PageAcceptBanner web part on top of the created modern page. Using this web part the users accessing the page can decide whether they want to keep or discard the created modern page. See the [Page Transformation UI](modernize-userinterface-site-pages-ui.md) article to learn more on how to install and configure the default page banner web part.
3131
ReplaceHomePageWithDefault | $false | The default behavior is to transform your site's home page to a modern page like any other regular page. If you use `-ReplaceHomeWithDefault` then a site's home page will be transformed to a 'default' out-of-the-box modern home page, so the one you would get with a newly created modern team site.
3232
TakeSourcePageName | $false | The default behavior is to give the created modern page a name that starts with the prefix Migrated_ and let the original page keep it's existing name. When `-TakeSourcePageName` is specified the newly created page gets the name of the original page and the original page is renamed with a prefix Previous_. Set this option if you're sure you want to move forward with the modern page as it will ensure that all links pointing the original page now result in the new modern page being loaded.
33+
ClearCache (as of January 2019 release) | $false | To optimize performance certain data (list of available client side web parts, calculated list of fields to copy metadata for) is cached after the first execution. This cache will stay valid during the complete PowerShell session unless you use the `-ClearCache` switch. Restarting your PowerShell session also clears the cache.
34+
CopyPageMetadata (as of February 2019 release) | $false | The default behavior is to not copy page metadata (so additional columns added to the site pages library). When `-CopyPageMetadata` is specified the values of the custom metadata fields of the page to transform are copied to the newly created page
3335

3436
(*) Mandatory command line parameter
3537

‎docs/transform/modernize-userinterface-site-pages-security.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
title: Security requirements for using page transformation
3+
description: Explains the required permission levels for page transformation
4+
ms.date: 01/30/2019
5+
ms.prod: sharepoint
6+
localization_priority: Priority
7+
---
8+
9+
# Security requirements for using page transformation
10+
11+
> [!IMPORTANT]
12+
> The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [sp-dev-modernization GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
13+
14+
Before an existing wiki or web part page can be transformed to a modern client side page you do need to have the needed SharePoint permissions. This short article explains what permissions are required.
15+
16+
## General security requirements
17+
18+
These requirements apply always, regardless whether you're using page transformation from PowerShell, .Net or the [Page Transformation UI](https://aka.ms/sppnp-pagetransformationui) solution.
19+
20+
Page Transformation feature | SharePoint Permission | Included in default permission levels
21+
----------------------------|-----------------------|--------------------------------------
22+
Create a modern version of the wiki or web part page | Edit Items | Contribute, Edit, Full Control
23+
Copy the page metadata | Edit Items | Contribute, Edit, Full Control
24+
Copy the item level permissions (if any) | Manage Permissions | Full Control
25+
26+
Above chart shows that with the default `Edit` or `Contribute` permission level you can use page transformation but if there's item level permissions on the source page these are not copied over. Using the `Full Control` permission level does enable the copy of item level permissions as that one by default includes the `Manage Permissions` permission.
27+
28+
## Page Transformation UI security
29+
30+
The [Page Transformation UI](https://aka.ms/sppnp-pagetransformationui) solution does operate as the logged on user and therefore the logged on user does need to have the permissions as described in the previous chapter. When the user does not have the `Edit Items` permission then the UI entry points (Ribbon buttons) will not accessible.

‎docs/transform/modernize-userinterface-site-pages-ui-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: End user guide for the page transformation UI
33
description: Explains how end users can use the page transformation UI
4-
ms.date: 11/21/2018
4+
ms.date: 01/30/2019
55
ms.prod: sharepoint
66
localization_priority: Normal
77
---

‎docs/transform/modernize-userinterface-site-pages-ui.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
---
22
title: Transform classic pages to modern client-side pages using UI
33
description: Explains how to transform classic wiki and web part pages into modern client side pages using the SharePoint UI
4-
ms.date: 01/24/2019
4+
ms.date: 01/30/2019
55
ms.prod: sharepoint
66
localization_priority: Priority
77
---
88

99
# Transforming to modern site pages from inside the SharePoint UI
1010

1111
> [!IMPORTANT]
12-
> **The SharePoint Page Transformation UI is currently in preview**. The solution is continuously evolving, checkout [the sp-dev-modernization GitHub repository](https://github.com/SharePoint/sp-dev-modernization/tree/dev) to stay up to date on the latest changes. If you encounter problems please file an issue in the [PnP sp-dev-modernization GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
12+
> **The SharePoint Page Transformation UI is currently a beta release**. The solution is continuously evolving, checkout [the sp-dev-modernization GitHub repository](https://github.com/SharePoint/sp-dev-modernization/tree/dev) to stay up to date on the latest changes. If you encounter problems please file an issue in the [sp-dev-modernization GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
1313
1414
If you want to give your end users the option to self-service modernize pages then using the SharePoint Page Transformation UI makes a lot of sense as it offers your end users UI extensions (ribbon buttons) to launch page transformation:
1515

‎docs/transform/modernize-userinterface-site-pages.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Transform classic pages to modern client-side pages
33
description: Explains how to transform classic wiki and web part pages into modern client side pages
4-
ms.date: 03/23/2018
4+
ms.date: 01/30/2019
55
ms.prod: sharepoint
66
localization_priority: Priority
77
---
@@ -14,7 +14,7 @@ The SharePoint PnP Modernization framework ([Nuget](https://www.nuget.org/packag
1414

1515
> [!IMPORTANT]
1616
> - Page transformation today works for wiki and web part pages. Publishing pages is something we're evaluating for a future release.
17-
> - The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [PnP Tools GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
17+
> - The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [sp-dev-modernization GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
1818
1919
To use page transformation for your environment you can use one or more of below described approaches:
2020

0 commit comments

Comments
 (0)