Announcing SharePoint page approvals
We are happy to announce that we will be releasing SharePoint page approvals to Targeted Release. We expect to start the rollout of this feature to all Targeted Release tenants by end of July 2018. Rollout status Current rollout status: July 31st, 2018 - Deployed to 10% of Targeted Release tenants August 3rd, 2018 - Deployed to 50% of Targeted Release tenants August 6th, 2018 - Deployed to 100% of Targeted Release tenants January 8th, 2019 - Deployed to all tenants in SharePoint Online Documentation: 1. Configure page approval 2. Page approval flow Known issues If the page is checked-out by another user and you (the author in this case) submit the page for approval, the page will not notify and proceed with the approval. The flow will run and send an email indicating to the author indicating an error occurred in publishing the page. If you have only major versions enabled for the Site Pages library, submit for approval will result in int he following error: Could not complete that action: The type of data at position 0 is different than the one expected. There an issue with the Flow service for the UK region. Any existing UK tenants created before March 2018 will work while it affects only new tenants created after March 2018. We expect to have this resolved by end of September if everything goes according to the plan. See this thread for more information. Good news is that these will be fixed soon are fixed! If you have any feedback, please make sure you discuss here! Configure page approval Site owners can configure page approval to add to the standard publishing process for a site. After adding page approval flow, new and updated pages will be not be published directly. Instead, only the completion of the approval flow will make changes visible to all readers of the site. A site owner can configure page approval flow from the Flow menu of a pages library. Submit page for approval Once the page approval is configured, authors will be able to submit page for approval. The publish button will be replaced by a submit for approval button. The page will be published once the page is approved. Rejecting a page will put that page back to draft status. Approve page Approvers will get an email regarding the page approval request. They can either approve the page directly in the email (in email clients that support actionable messages) or open the page from the email to review and approve the page in SharePoint. Customizing the page approval flow Since page approvals use Microsoft Flow behind the scenes, the page approval flow is available to site owners to modify and add any custom business process items in the flow. After creating the flow, the site owner can click on Flows -> See your flows in the pages library to find the page approval flow. For example, The default approval type is set to ‘anyone can approve’. Site owners can modify the flow and change the approval type to ‘everyone must approve’ if that is the requirement.
Create Approval Flow in Power Automate with Adaptive Card in MS Teams from MS Form response (Part 1)
To eliminate the traditional way of requesting for something to be approved via email or letter writing, here is the best way to handle such situation with just a click and response within with reasons with few seconds of receipt.PowerApps and Flow buttons are graduating out of preview!
PowerApps and Flow are becoming a more integral part of SharePoint Online with the imminent release of Custom Forms with PowerApps and the Flow Launch Panel. Starting in November, these features will no longer be considered as preview features. If you have the Preview Features switch turned off in SharePoint administration center today, you were not seeing the Flow and PowerApps buttons in modern lists and libraries. Once this change goes into effect, the buttons will become available, regardless of the setting: Flow button in modern libraries, and both Flow and PowerApps buttons in modern lists. The change will start with our First Release tenants, and then move forward into the rest of the production in two waves. We hope to complete the change over the month of November. PowerApps and Flow are still working on completing their certification for government and sovereign cloud environments with stricter compliance requirements, and the buttons will continue to remain invisible for these environments, independent of the preview features switch setting.
Combine Multiple MS Forms into one SharePoint List via Flow
Hello, I am trying to create a workflow for new hire requests. The HR Admin will enter a request via a MS Form and those responses will create a list item in SharePoint and also send an email to the hiring manager. The hiring manager will be prompted to enter additional information via a Mgr MS Form. The HM responses will then update the previous list item created by the HR Admin. All responses will then be sent to a distribution list for further action. I have created both forms, the Sharepoint list and have created multiple flows, however, the Manager Form responses are not updating to previously created HR items. It is creating a new item instead. The flow is below. Any suggestions? I am new to Flow and have been You Tubing and Googling to learn!
