Book Image

SharePoint Development with the SharePoint Framework

By : Jussi Roine, Olli Jääskeläinen
Book Image

SharePoint Development with the SharePoint Framework

By: Jussi Roine, Olli Jääskeläinen

Overview of this book

SharePoint is one of Microsoft's best known web platforms. A loyal audience of developers, IT Pros and power users use it to build line of business solutions. The SharePoint Framework (SPFx) is a great new option for developing SharePoint solutions. Many developers are creating full-trust based solutions or add-in solutions, while also figuring out where and how SPFx fits in the big picture. This book shows you how design, build, deploy and manage SPFx based solutions for SharePoint Online and SharePoint 2016. The book starts by getting you familiar with the basic capabilities of SPFx. After that, we will walk through the tool-chain on how to best create production-ready solutions that can be easily deployed manually or fully automated throughout your target Office 365 tenants. We describe how to configure and use Visual Studio Code, the de facto development environment for SPFx-based solutions. Next, we provide guidance and a solid approach to packaging and deploying your code. We also present a straightforward approach to troubleshooting and debugging your code an environment where business applications run on the client side instead of the server side.
Table of Contents (14 chapters)

Using Office 365 to build better business process

One aspect of making this web part better is to take care that site (or page) owners are aware of the feedback they are getting.The traditional approach is to create an alert for the owners on the feedback list or have some sort of logic within the web part that executes. Another, even more useful approach is to use SharePoint Workflows. The modern way is to use Microsoft Flow. With Microsoft Flow, we can easily create a flow that will trigger when a new item is added to the feedback list, and then maybe send emails to owners. The email could include the link to the page in question and our feedback list could have additional fields like status and owner's comment. The flow could also send an email back to the original user because we know him as the creator of the feedback list item.

The flow would benefit from additional information about the page the feedback concerns. For example, information which will allow it to open the page...