687474703a2f2f692e696d6775722e636f6d2f6c3031686876452e706e671

Latest changes

Provisioning Engine

The first version of the PnP remote provisioning engine was released with the April 2015 release. For the October release we have continued to add new supported capabilities and made improvements from stability perspective for both Office 365 and on-premises. This list contains the main updates that have been added in the October release:

  • Improved and updated delta handling
  • Overall quality and performance improvements
  • Implementation of 201508 provisioning schema version support – see this documentation for latest supported capabilities.
  • Regional settings for sites
  • Language settings for sites
  • Workflow definitions and associations
  • Publishing settings for sites – Deployment of Design package. Available web templates and page layouts
  • Auditing settings
  • Display/New/Edit-form support for content types
  • Document Set provisioning support
  • Add-in deployment support – Notice that requires tenant permission add-ins to be used to avoid requirement for Trust operation. More documentation for this one coming soon.
  • Significant improvements on the on-premises support

PnP library

  • PnP Core: Lots of re-factoring done to improve code quality and completeness:
    • provisioning engine updates (see above)
    • Bug fixing around term group provisioning
    • Delete navigation nodes from sites
    • External sharing capabilities – see ExternalSharingExtensions.cs for full list
    • Build and test automation improvements
    • Both PnP Core Nuget packages (cloud and on-premises) have been also updated accordingly.
  • New sample Core.ExternalSharing demonstrates how to use external sharing APIs with SharePoint or OneDrive for Business sites in Office 365. With external sharing APIs, you can automate document or site sharing for external users. With site level sharing, you can assign external user with view, edit or owner permissions.
  • New sample Diagnostics.Logging containing a SharePoint provider hosted add-in and an Azure Web Job, which are used to demonstrate the flexibility and rich output of OfficeDevPnP.Core component trace logging functionality. This is good reference sample for diagnostics handling in your provider hosted add-ins.
  • New sample EmployeeRegistration.Forms shows an application that’s leveraging ASP.Net web forms to offer an alternative for an InfoPath form.
  • New sample EmployeeRegistration.KnockOut.SinglePageApp shows an application that’s leveraging JavaScript and HTML to offer an alternative for an InfoPath form. The application is using the knockoutjs library to realize a dynamic JavaScript UI.
  • New sample EmployeeRegistration.MVC shows an application that’s leveraging ASP.Net MVC to offer an alternative for an InfoPath form.
  • Updated component Core.JQuery to include example around jQuery promises. See specific readme around this for addition information.
  • Significant updates to Solution Provisioning.UX.App with cleaning up the code and few other bug fixes for this reference solution.
  • Updated PnP-PowerShell Commands with new CommandLets and with few fixes
    • Overall quality improvements
    • Support for 201508 schema provisioning model
    • Updated documentation
    • Updated contribution guidance
    • New Get-SPOProperty cmdlet
    • Updated Add-SPOWebPartToWebPartPage cmdlet
    • Updated Add-SPOTaxonomyField cmdlet
    • Updated unit tests for cmdlet’s

 

Source: Office Dev Center – Office 365 Developer Patterns and Practices – October 2015 release

Office 365 Developer Patterns and Practices – October 2015 release

Leave a Reply

Your email address will not be published. Required fields are marked *