Introducing "Request sign-off" - an approval flow that requires no set up
We are happy to announce a new feature in SharePoint called "Request sign-off". The goal is to provide you an easy way to send an item for approval to someone else. This feature enables an open approval process that allows you to easily record whether or not a document or list item was approved or not. There is no setup required. Request sign-off makes use of SharePoint's integration with Microsoft Flow. You can use it by selecting a file or list item (but not a folder), and then pulling down the Flow menu in the modern library or list UI, and selecting "Request sign-off". This flow will appear alongside any other custom flow that you or others may have added to the library. Once it is invoked, Request sign-off will create a new text column in your library called "Sign-off status". This column will record the state of your request. It works just like any other text column, you can sort, filter or group by it to organize your library. On invocation, this will tell you that it will send an approval request on your behalf, and ask your consent. Once this is provided, you can pick one or more approvers, and write a message to them for your approval request. If you add more than one approver, any one of them can approve your request: The person you sent the approval to will receive an approval request. This will be an actionable message on clients that support it (meaning you can approve it directly from within Outlook). The approver can also provide some comments along with their decision. There will also be a link included that lets the approver view the item in question: The sign-off status column is then updated with the decision, and the person who sent the approval request will receive an email with the comments: By saving you the trouble of setting up a flow and creating a new column to track status, we hope that this feature will make it easy to add a lightweight approval process to your libraries and lists. We expect this feature to start rolling out to our customers in targeted release (previously called first release) after April 9. Barring any issues we will continue to roll it out to the rest of our customers in two phases late April and early May.Configuring approvals for lists and libraries
We are adding a new menu item under the Flow menu that will let customers configure the type of approvals they would like to use in their lists and libraries (Request sign-off, or Content approval), or turn approvals off altogether. We have added this feature based on the feedback that we received for the rollout of the Request sign-off feature, where some customers preferred to use the Content approval feature which changes the visibility of the current item based on the approval status, and there are fixed approvers for a given list or library, or other customers had other custom flows configured for their list or library, and did not want to have Request sign-off to become a source of confusion for their users. To make changes, as site owner, you will be able click on Flow->Configure flows in the command bar of your list or library: Then in the panel that appears, pick the approval method that you'd like, or turn approvals off altogether: The new configuration panel will become available for our Targeted Release customers in early September, and then go to the rest of our customers. We expect to complete the rollout by September 19. Please continue to keep the feedback for our features coming, and tell us how we can make SharePoint work better for you.
New Trigger Conditions for Flow!
Microsoft Flow triggers now have a built-in condition checker (in the settings). Now in only 1 step, you can set a condition for a specific column, so that the trigger only fires when the condition is met! We wanted newer Flow makers to be able to leverage this new feature too, so here is a video that shows offr the new feature, with the bonus of a few extra tips for newer makers with minimal experience with expressions. Enjoy, Audrie https://www.youtube.com/watch?v=FcTMBQ9KuUAModern SharePoint lists are here—including integration with Microsoft Flow and PowerApps!
Earlier this year, we unveiled a new cloud-first, mobile-first vision and roadmap for SharePoint, which included innovations that empower people, teams and organizations to intelligently discover, share and collaborate on content from anywhere and on any device. Today, we’re pleased to announce the rollout of modern SharePoint lists to SharePoint Online, along with one-click integration of PowerApps and Microsoft Flow. These enhancements will begin rolling out to Office 365 First Release customers the first week in August 2016. Learn more about this from Chris McNulty on the blog.Flow Licensing
A question about the Flow licensing model. The charge is number of flows that have run during the course of a month, pooled across an entire enterprise. So if I have 1,000 users in my tenant, each of them with an E3 O365 license, I should have 2,000,000 Flow runs per month, shared among all of my users. (An E1, E3, or E5 O365 license is considered as Flow for Office 365 in the licensing chart.) All well and good, and this should be plenty. However, I have no methodology or tool to see what the usage is in my enterprise. I don't know if I'm expending 100,000 flow runs a month, or 10, or 1.9 million. I don't know if I need to budget for more Flow runs next quarter, or if I need to put in some governance on my users. Moreover, I don't have any governance tools anyway, other than the giant "Off" button. What if I have a small minority of users creating an irresponsible number of Flows, consuming all of my available Flow runs? I have no way of knowing it's taking place, no way of knowing who is consuming the runs, what business needs these runs are fulfilling, nor any way to limit, encourage, or advertise their use, even if these Flow runs bring a great deal of success and value. In short, to have a per-use license structure with zero ability to monitor or manage usage by the consumer (the enterprise IT department) will not encourage adoption of what is, in my opinion, a fantastic tool. Can we please have an administrative tool for Flow, and a relaxing of license enforcement until we do?Set values for Managed Metadata (aka Taxonomy) columns in PowerApps and Flow! (First Release)
Hi everyone, As of today, you will be able to set the values of your managed metadata columns (sometimes also called taxonomy columns) in PowerApps (for both multi-value and single value) and in Flow (single value for now, but multi-value coming soon...) Here's a sample multi-value taxonomy column that was tied to a termset for languages. We are not fully all the way there: the default values are not yet showing up if they are set, and we don't yet let you disambiguate between different paths while you are typing, but we think this is a great net new add for our customers who love and use the managed metadata columns. Please give it a try, and let us know your feedback. In your First Release tenant, you can create a new app, or custom forms, or go to an existing app and refresh the schema to get the new columns. We expect to start rolling out to Production in the last week of November if we don't hit any blocking issues.Hear from Sogeti & Motion10 how they created a SharePoint solution for ProRail using Flow Buttons!
Does your organization use Office365 and SharePoint online on a large scale? Does your organization invest regularly in creating and maintaining SharePoint sites and contents for team collaboration? Learn how Flow Buttons made it possible for ProRail to facilitate rapid provisioning of team and project sites, thus streamlining processes for ongoing maintenance. Flow buttons can be triggered from the Flow mobile app (get the app) or website. View a short video below to learn more on flow buttons: Learn more about how ProRail created a SharePoint solution using Flow Buttons on the blog.
